Skip to content

Consent and caching

Track Them All doesn’t ask visitors for consent. It follows the consent plugin you already use, through the WP Consent API.

Respect the WP Consent API, under Settings › Track Them All › Events & privacy, is on by default. Without a consent plugin that supports it, every visitor is tracked. With one that supports it (Complianz, CookieYes and others), each platform waits until the visitor accepts the right category of cookies, for browser tags and server-side events alike:

  • Google Analytics needs statistics consent.
  • Google Ads conversions and the other ad platforms need marketing consent.

A visitor who refuses isn’t tracked in the browser or from your server.

Consent is checked in each visitor’s browser, not baked into the page. With a consent plugin, tags are printed inert, and the tracking script runs each one only once the visitor’s consent allows it. Every visitor gets their own event IDs. So a cached page never carries one visitor’s choice, or their events, to the next. With Google Consent Mode on, Google’s tag loads at once, with consent denied until the visitor accepts.

Turn on Google Consent Mode v2 to start Google tags with consent denied, as Google requires in the EEA, and update them with each visitor’s answer from the WP Consent API. Site Health warns if Consent Mode is on without a consent plugin.

When a payment gateway confirms an order minutes later by webhook, or you mark an order paid yourself, the purchase is sent with the consent and ad-click details of the shopper who placed it, not those of whoever triggered the confirmation.

Don’t track these roles leaves out logged-in users with those roles, including test orders they place. Administrators are left out by default.

That depends on your jurisdiction, not on this plugin. Track Them All exists to send data to ad platforms, so in most places that require consent for marketing cookies you’ll need a consent plugin.

Checked against Track Them All 1.0.5 on main, 19 October 2026.