Introduction
Verify that Reject all, Analytics only, Accept all, and preference changes produce the expected consent and tracking behavior on a live website.
What it means
Test from a clean private browser session so an old consent cookie does not hide the banner or invalidate the result.
Initial visit should begin with non-essential Consent Mode v2 parameters denied before Google tags act on a visitor choice.
Reject all should keep optional trackers blocked across navigation; Analytics only should release analytics but keep marketing denied; Accept all should follow the published configuration.
Evidence should identify the test state separately from a general runtime heartbeat, because a loaded banner alone does not prove visitor interaction behaviour.
Why it matters
Many consent failures appear only after a user clicks a button or navigates. Interaction evidence turns a visual banner review into a behaviour test.
Common mistakes
- Treating a copied snippet as installed without verifying a live runtime heartbeat.
- Placing the consent runtime after GTM, analytics, advertising pixels, or theme-injected scripts.
- Publishing a configuration change without testing a clean browser session and the Reject all path.
- Applying a broad blocking rule without reviewing the detected provider and category first.
Practical checklist
- Confirm domain ownership and open the site-specific Privacy Setup flow.
- Install or update the GDPRChecker runtime before non-essential tracking code.
- Publish the banner configuration and verify its live heartbeat.
- Test initial visit, Reject all, analytics-only, Accept all, and withdrawal in a private window.
- Run a compliance scan and keep the resulting evidence with the release record.
- Enable scheduled scans so later tag, plugin, theme, or campaign changes are detected.
How GDPRChecker helps
GDPRChecker’s Consent Interaction Evidence report shows the expected parameter state for initial visit, Reject all, Analytics only, and Accept all, alongside runtime readiness.
Combine it with a private-window test and a scanner report; automated third-party browser testing is intentionally labelled separately from recorded runtime evidence.