How to test what your cookie banner actually does
A banner can look polished and still have little influence over the scripts running on a page. A technical consent review compares what the interface says will happen with the requests and storage you observe in the browser.
Make an inventory before changing settings
List analytics tags, advertising pixels, embedded maps or video, chat tools and other third-party components. For each, note where it loads, what purpose it serves and which consent setting is meant to control it. Some tools can be loaded by your theme, your tag manager and a plugin at the same time. Check all paths before assuming one switch controls them.
Run four separate browser sessions
- Open the site in a fresh session and inspect what happens before you select an option.
- Reject optional categories. Follow a link to an interior page and check that the choice carries over.
- Accept one optional category. Confirm that the expected tools change behaviour and that unrelated categories follow their own settings.
- Change or withdraw the choice from the site controls. Recheck behaviour on a later page visit.
Record the URLs, the choice, the browser and the requests or storage you observed. If you use Google Consent Mode, check both the configured default settings and the updates after a choice. Google’s Consent Mode documentation explains the difference between basic and advanced setups.
Turn findings into a release check
Keep the test sheet alongside your tag inventory. Run it again when you add a tracker, an embed or a new language. Use the EDPB cookie banner taskforce report and your privacy adviser to confirm what notices and choices your site needs. If you need help with implementation and testing, see our cookie consent setup service.