| 开发者 | newad |
|---|---|
| 更新时间 | 2026年11月17日 06:35 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
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):
GET /wp-json/newad-aat/v1/collect — relays d/debug to /v1/collect upstream.GET /wp-json/newad-aat/v1/tag.js — serves nwd_aat_tag.js, cached (1-hour transient plus a
persistent "last good" fallback).GET /wp-json/newad-aat/v1/banner.js — serves the Newad Consent Manager cookie notice,
cached, only when enabled in the plugin's settings.GET /wp-json/newad-aat/v1/proof — relays the visitor's consent choice upstream, only when
the Newad Consent Manager is enabled.collect_all toggle (mirrors window.nwdAatConfig.collect_all)..zip file under Plugins → Add New → Upload 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.
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.
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.
/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.
wp_enqueue_script()
instead of an inline <script> block.Object.defineProperty): an old manual snippet,
before or after the plugin, no longer overrides the collection endpoint./v1/collect and
nwd_aat_tag.js, installation diagnostics and a suggested selector catalog.