Verify Consent Mode in Tag Assistant for WordPress

Start with a clean, repeatable test session

Google's troubleshooting guide says Tag Assistant can be used to check whether a site sets the correct default consent state, updates that state after visitor interaction, and shows which tags check which consent types. Treat that as a technical audit, not a screenshot exercise.

Open a fresh browser profile or private session, clear the existing site consent cookie, and start a new Tag Assistant session for the public URL you want to test. For the clearest results, Google recommends Chrome with the Tag Assistant Companion extension. If your WordPress setup has page caching, test a normal cached page and any template where tags are injected differently.

Confirm the default state appears before tags use it

Consent Mode depends on order. In a typical EEA opt-in workflow, optional storage should not start granted before the visitor chooses. In Tag Assistant, select the earliest consent event and inspect the API call or the Consent tab. Google's current debugging documentation calls out ad_storage, analytics_storage, ad_user_data, and ad_personalization as parameters to check for website verification.

If you use Google Tag Manager, also check when the consent tag runs. Google documents the Consent Initialization trigger as the trigger intended to make consent settings available before other triggers fire. That does not remove the need to configure your banner correctly, but it gives you a concrete timing point to inspect.

Test accept, reject, and custom updates

A single accept-all test is not enough. After interacting with the banner, select the latest consent event in Tag Assistant and confirm the update reflects the visitor's actual choice. Analytics consent should follow the analytics category. Advertising storage, advertising user data, and ad personalization should follow the marketing or ads category your site has defined.

Repeat the same check after rejecting optional categories and after saving a custom mix. Then reload the page and verify the stored choice is applied consistently. A common WordPress failure mode is that the first page view works, but a cached page, theme-injected script, or plugin optimization path changes the sequence on the next load.

Keep WordPress script timing part of the test

WordPress itself uses cookies for logged-in users, commenters, and language behavior, but most Consent Mode problems come from optional analytics and advertising scripts. Check where your theme, plugins, page builder, or GTM container loads Google tags. A tag that fires before the default consent call can undermine an otherwise good banner.

ACookies sets denied Google consent defaults and sends updates after visitor choice in its Consent Mode workflow. It also supports WP Consent API registration in the WordPress plugin. Those product claims are grounded in the repository implementation and marketing product data, but your final site still needs Tag Assistant, cookie, and network checks after configuration.

• Clear existing consent and start a new Tag Assistant session.
• Inspect the earliest consent event before interacting with the banner.
• Check accept, reject, and custom category updates.
• Reload the same page and retest a different WordPress template.
• Compare Tag Assistant output with browser cookies and network requests.

Frequently asked questions