ModeConsentRun a Free SentinelScan
Cookie Banner Audit

Cookie banner audit for sites that need proof, not assumptions

A browser-based cookie banner audit that checks whether consent choices actually control cookies, pixels, scripts, GTM tags, Consent Mode signals, and vendor requests.

Implementation context

Start from observable behavior, then repair the consent contract.

A cookie banner audit should answer the question buyers actually care about: does the live site behave the way the banner, policy, and CMP settings imply?

ModeConsent audits the browser path behind the banner. First load, reject, accept, category opt-in, revisit, withdrawal, regional rules, and high-value conversion paths are tested against cookies, scripts, requests, and consent state.

The result is a focused evidence package that shows what is working, what is leaking, and what needs repair before legal, marketing, analytics, or engineering can trust the implementation.

What breaks

The failure pattern usually starts before the dashboard can see it.

01

The banner loads after tracking

Visitors can be tracked in the first seconds even when the banner appears polished.

02

The CMP and GTM have separate logic

Preference categories must control triggers, templates, custom HTML, and hard-coded scripts.

03

Reject is not tested like accept

Teams often validate the happy path while missing reject-all, withdrawal, and granular category behavior.

04

Evidence is not stakeholder-ready

Screenshots of settings rarely show whether cookies, requests, or scripts honored a visitor choice.

How ModeConsent fixes it

Repair the consent system where visitors and tags actually interact.

  1. 01

    Record browser behavior

    Capture storage, network calls, tag timing, CMP state, and visible banner state under each user choice.

  2. 02

    Map banner choices to execution

    Connect categories to GTM triggers, Consent Mode updates, vendor loaders, and blocking rules.

  3. 03

    Prioritize repairs by consequence

    Separate legal exposure, Google signal issues, analytics quality, and governance cleanup.

  4. 04

    Retest and package proof

    Validate the repair and deliver evidence legal, marketing, analytics, and engineering can use.

Why this is urgent

Platform and regulator requirements now point at implementation evidence.

Google Ads Consent Mode updates

Google states that EEA advertisers must collect consent and share consent signals with Google to keep using applicable tags for measurement, ad personalization, and remarketing.

SourceGoogle EU User Consent Policy help

Google says advertisers with EEA traffic need to pass end-user consent choices to Google, and that adopting a CMP does not automatically guarantee compliance because implementation matters.

SourceICO cookie compliance enforcement

The ICO continues to test cookie compliance, including whether advertising cookies are stored before choice, whether reject is as easy as accept, and whether cookies are placed without consent.

Source
Related work

Adjacent pages in the consent stack.

Resources

Cookie Banner Failures

The common technical failures that make cookie compliance look correct in a CMP dashboard while scripts still collect data in the browser.

View pageServices

/services/cmp-implementation-audit/

A CMP implementation audit for teams that need to prove their banner, categories, blocking rules, GTM logic, and browser storage behavior work together.

View pageCompliance

Browser-Level Audits

Evidence-led audits that show what fires, what stores data, what changes by region, and whether consent choices are honored in production.

View page

/free-scan/

View page
Request audit

Need evidence for the live consent stack?
Start with browser behavior.

Request Compliance Audit