Linux 软件免费装

Newad Advanced AdTracking

开发者 newad
更新时间 2026年11月17日 06:35
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

tracking analytics gtm pixel csp

下载

1.2.1

详情介绍:

This plugin is an alternative to the subdomain CNAME (custom_collection_domain, configured via aat_console) for clients whose Content-Security-Policy blocks aat.newad.com.br. Instead of depending on the client's own DNS team, the plugin runs inside WordPress itself: it injects the nwd_aat_tag.js tag pointing to the site's own REST routes and proxies collection server-to-server to Newad's real service. Since the visitor's request never leaves the client's domain, no CSP rule applies to it. The plugin does not replace the tag — nwd_aat_tag.js is fetched from the upstream at runtime and served verbatim, cached. Funnel classification stays entirely on Newad's backend; the plugin is a pure byte proxy. REST routes created (namespace newad-aat/v1): All four routes are public and unauthenticated — the same public surface the real upstream endpoints already have (they don't require authentication either, since that's a hard requirement for working as a tracking tag/pixel). Admin screen (Settings → Newad AdTracking):

安装:

  1. Upload the .zip file under Plugins → Add New → Upload Plugin.
  2. Activate the plugin.
  3. Go to Settings → Newad AdTracking and paste the site code from Newad's installation guide.
  4. Use the "Test installation" button after a real visit to the site.

常见问题:

There's already a Newad tag pasted into the theme. Do I need to remove it before installing the plugin?

No. The plugin publishes window.nwdAatConfig as a locked property: the old tag can no longer override the collection endpoint and becomes inert (no duplicate events). Use "Scan this site" to see where it lives and remove it whenever convenient. An old tag living inside a Google Tag Manager container stays in the container and the plugin can't see it.

Does this replace the nwd_aat_tag.js tag?

No. The tag is fetched from the upstream at runtime and served verbatim — the plugin only changes the transport (same-origin instead of cross-origin), never the tag's content or behavior.

Does the plugin decide what counts as consent?

No. Consent decisions are made by the Newad Consent Manager, when it's enabled, or by the site's own CMP — the tag reads Google Consent Mode v2 from dataLayer on its own. The plugin only relays the cookie notice script and the visitor's resulting choice; it never interprets or decides what is or isn't allowed.

Does it work with /v1/imp (publisher impression pixel)?

That's not this plugin's use case — /v1/imp is for the publisher's page (RTB), not for the advertiser's WordPress site.

更新日志:

1.2.1 1.2.0 1.1.0 1.0.0