Your banner looks right. But do the choices work? This checklist helps you check connected tools, saved preferences and records. If you do not edit your website's code, ask your web developer to run it with you.
Set the scope
Record the URL, date, browser, device, active banner settings, and tools you will inspect. List analytics, advertising, chat, video, and other embeds. Check plugins and tag managers for duplicate installations.
Use a test browser state for fresh-visitor checks. Do not erase a real visitor's saved preferences. Keep saved-choice tests separate from new-visit tests.
Follow the visitor's journey
| Test | What to inspect |
|---|---|
| Before a choice | In an opt-in setup, connected optional tools should wait. Watch actual network requests, not just cookie names. |
| Reject all | Optional groups stay off. The website remains usable. |
| Partial choice | Allow one optional group and leave another off. Only the connected allowed tools start. |
| Accept all | The intended optional tools start once, without duplicate page views. |
| Reload | A valid choice remains in the same browser. The notice does not ask again without a reason. |
| Reopen settings | A visible control opens the real preferences dialog. |
| Withdraw | Future collection follows the new choice. Check any vendor shutdown or reload steps. |
| Relevant configuration change | Change categories or services on a test site and check whether a fresh choice is required. Do not assume a color change requires one. |
Inspect Google Analytics carefully
In basic consent mode, Google describes holding its tag until consent. Advanced mode has different behavior. Choose the mode you intend to use before judging the result. See Google's consent-mode overview.
Our ConsentPop.com measurement guide records the behavior we observed on our own site. It does not prove that another website's tag manager or plugins use the same setup.
Check records without overstating them
Find the test choice in your dashboard. Compare its time and category values with your test notes. A timestamp does not by itself prove all scripts respected the choice. Do not describe a consent event as an exact copy of the historical notice unless that notice was actually retained.
Check access and small screens
Use a keyboard to open preferences and change a choice. Test a narrow mobile screen. Check links, button labels, and whether the notice hides essential navigation. If you hide the floating settings button, provide another working way to reopen preferences.
Save the evidence
For each check, save the result, relevant screenshot, and network observation. Label skipped and failed checks. Recheck after a new tool, plugin, or consent configuration change. Background verification has coverage and quota limits; it does not replace every manual check.
Start with the setup guide. Review legal wording and region rules for your business separately from these technical tests.