Cookie consent for Ad Inserter

What Ad Inserter adds to your visitors’ browser

What matters for consent with Ad Inserter

What our tests found on Ad Inserter

• Depends on a setting · Ad InserterAd blocking detection loads Google and ad scripts before the choice

  setting “Use external scripts (ad blocking detection)” · by default: on

  • Off by default; the problem starts when you turn it on.
  • Adds bait tags for Google Analytics, Tag Manager, Quantcast and Media.net.
  • Also loads an image from dummyimage.com and checks Google's AdSense script.
  • Sets the cookies aiADB, aiADB_PV, aiADB_PR and aiBLOCKS.

  What to do: Turn off Use external scripts, or define AI_ADB_NO_GOOGLE_ANALYTICS, AI_ADB_NO_GTM, AI_ADB_NO_QUANT, AI_ADB_NO_MEDIA_NET, AI_ADB_NO_DUMMYIMAGE and AI_ADB_NO_GOOGLESYNDICATION in wp-config.php.

  Read in its code, 16 October 2026, Ad Inserter 2.8.19.

  Full detail

  Ad Inserter's ad blocking detection is off by default. When it is on with Use external scripts (on by default), every page footer gets bait tags before any choice: <object> tags pointing to google-analytics.com/analytics.js, googletagmanager.com/gtag/js, secure.quantserve.com/quant.js and contextual.media.net/dmedianet.js, an <img> from dummyimage.com, and after load a HEAD fetch to pagead2.googlesyndication.com/pagead/js/adsbygoogle.js whose address is base64-encoded in an inline script. Cookies: aiADB (30 days by default) and aiADB_PV (365 days) when a blocker is handled, aiADB_PR for redirection, and aiBLOCKS (365 days) for per-block close and view limits.

• Depends on a setting · Ad InserterAd Inserter can make each ad block wait for a consent cookie

  setting “Cookies list (per block)” · by default: empty

  It has no banner and no consent signals. A block can wait for a cookie from its Cookies list; the check runs in the browser only with Client-side insert or show.

  Read in its code, 16 October 2026, Ad Inserter 2.8.19.

  Full detail

  Ad Inserter shows no banner and does not use WP Consent API or set Consent Mode defaults. Each block can wait for a cookie listed in its Cookies list (whitelist or blacklist, empty by default); JSON cookies are read with the syntax name[key][*]=value after decodeURIComponent and JSON.parse. The check runs in the browser only with Client-side insert or Client-side show; server-side checks are frozen by page caching. Blocks waiting for consent are re-inserted on the page only on IAB TCF signals, on the events of one consent plugin, or when ai_load_blocks() is called; tcf- conditions hide the block if window.__tcfapi is missing after three tries.

• Set before the choice · Ad InserterAd Inserter hides ad code from banners that read the page

  setting “Dynamic blocks” · by default: Client-side insert

  Blocks with a browser-side check or lazy, manual or delayed loading are printed encoded, so a banner reading the page cannot see the ad address. Default blocks are printed in clear.

  What to do: Put the consent condition in each ad block's Cookies list (whitelist) instead of relying on a banner reading the HTML.

  Read in its code, 16 October 2026, Ad Inserter 2.8.19.

  Full detail

  With Dynamic blocks set to Client-side insert (the default), an Ad Inserter block that has a check run in the browser (cookie, URL parameter, referrer or client list, scheduling, a device selection other than all) or uses lazy, manual or delayed loading is printed with its code base64-encoded in a data-code attribute of a div (ai-dynamic, ai-lazy, ai-manual). Ad Inserter's own script decodes it and inserts it, and the inserted scripts run. A consent plugin that reads the page markup cannot see the ad network address. A block with default settings and no list is printed in clear.

Ads

Other plugins of the same kind.

Every plugin and theme we test →