Troubleshoot analytics consent that does not match visitor choices

Define the expected behaviour first

A consent banner can display the right buttons while sending the wrong instructions to analytics tags. Symptoms include unchanged collection after rejection, inconsistent behaviour between pages or missing updates after acceptance. Begin with an approved description of what each visitor choice should do.

Have the privacy owner confirm applicable requirements and any relevant exceptions. Technical consent mode is not a legal determination. ICO guidance covers storage and access technologies beyond traditional cookies, so a cookie-only inventory may miss scripts, pixels or other mechanisms requiring review.

Test fresh and returning visitor states

Use a clean browser profile for each initial-choice test. Inspect the state before interaction, after acceptance, after rejection and after a later change of preference. Repeat across relevant regional configurations and on pages reached without first visiting the homepage.

Google's Tag Assistant guidance describes checks for default consent, updates and tag behaviour. Check timing as well as the final state: a correct update cannot retrospectively explain a tag that fired under an unintended default. Keep evidence of the sequence, not just a screenshot of the banner.

Record a consent-state worksheet

For each test, capture the page, region configuration, previous preference, selected action, expected state and observed tag behaviour. Inspect browser storage and network requests where appropriate. The absence of an Analytics event alone does not establish that no other technology accessed the device.

Include navigation immediately after a choice. Google's implementation guidance discusses updates around page transitions, which can be relevant when a banner disappears before its instructions reach the tagging system.

• Default state appears before relevant tags execute.
• Accept and reject produce their approved, distinct outcomes.
• Changed preferences persist and remain changeable.
• Regional and deep-link journeys match the documented policy.

Repair dependencies rather than hiding the discrepancy

Assign the fault to the correct layer: banner interface, consent platform, tag container or site code. Avoid adding duplicate consent scripts as a quick fix. Retest the full sequence after publication because preview behaviour may differ from the live page.

Annotate reporting interruptions and explain that lawful collection boundaries can affect measured traffic. Do not weaken visitor choices to restore a dashboard trend. Close the issue only when the privacy owner and technical owner agree that observed behaviour matches the approved specification.