Ad tag data paths

Outside services used by WordPress ad plugins

Some ad plugins display banners hosted on your WordPress site. Other setups load ad code from an outside service. When that code loads, the visitor's browser contacts the service. This table describes the setups below; your settings can change where requests go.

Based on plugin documentation, not tests of your site. Your settings can change what loads. This is not legal advice or a compliance rating.

Scan your site for third-party requests

How we group ad plugins

We compare the ad-manager setups named below. A plugin that stores local banners on your WordPress site is different from a plugin that loads an ad tag from an outside ad service. Header-bidding stacks and consent strings are different setups. We have not tested consent timing or how long vendor logs are kept.

Ad manager plugins

No paid placement. Banners stored on your site first, then outside ad tags, then plugins not yet reviewed. Names are alphabetical within each group.

PluginDocumented behaviorDocumented script hostsHow long data is keptBefore consentLinksSource
AdRotate Banner Manager

This row covers AdRotate Banner Manager when banners are stored on your WordPress site. The plugin writes rows to the adrotate table. Pasted AdSense or other network tags are a different setup and are not this row. Consent timing is not tested here.

Banners stored on your siteNo outside ad script host documented for this setup. Other page requests are not covered.Not assessedNot tested
  • None
Ad Inserter

This row covers Ad Inserter when it inserts a publisher-provided tag that loads ads from an outside service. The plugin does not document a single default ad host. Local image banners without a network tag are a different setup and are not this row. Consent timing is not tested here.

Outside ad tagReceiving domains not verifiedNot assessedNot tested
  • None
Advanced Ads

This row covers Advanced Ads when an AdSense ad is on the page. The plugin loads a script from pagead2.googlesyndication.com. Header-bidding stacks and consent strings are a different setup and are not this row. Consent timing is not tested here.

Outside ad tagpagead2.googlesyndication.comNot assessedNot tested
Easy Google AdSense

This row covers Easy Google AdSense when a publisher ID is set. The plugin loads a script from pagead2.googlesyndication.com. Consent timing is not tested here.

Outside ad tagpagead2.googlesyndication.comNot assessedNot tested
Quads Ads Manager for Google AdSense

This row covers Quads Ads Manager when an AdSense ad is on the page. The plugin loads a script from pagead2.googlesyndication.com. Other ad networks configured in the plugin are a different setup and are not this row. Consent timing is not tested here.

Outside ad tagpagead2.googlesyndication.comNot assessedNot tested
AdSanity

We have not reviewed this plugin's ad-tag data path yet.

Not reviewedDocumentation not reviewed yet.Not assessedNot tested
  • None

What this table does and does not prove

This table describes the named ad-manager setups. It does not show what loads on your site. Where no outside ad script host is documented, that applies only to the setup described. Other page requests are not covered. An ad tag is a request from the visitor browser. Header-bidding stacks and consent strings are different setups. Plugins marked Not reviewed have not been assessed. We have not tested consent timing, and we have not assessed how long vendor logs are kept. The site scan linked below checks for third-party requests; it does not access your WordPress database.

Documentation snapshot: Oct 2, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-ads-plugin-privacy