Check if your Google Ads tracking is broken

Ads can still run while Google optimizes on incomplete or missing conversion data.

No signup. Scan runs as a new visitor.

See what a full diagnostic report looks like →

Need to implement Consent Mode? Get snippet →

What we see across real sites →

Want ongoing checks? Monitor your site →

This scan checks technical behavior, not Google Ads reporting delays or attribution windows.

The problem

Many websites with consent banners have tracking issues that break Google Ads conversion measurement. Tracking scripts fire before users accept consent, Google Consent Mode v2 isn't configured, or conversion events get blocked entirely.

When this happens, Google Ads receives incomplete data. Your campaigns optimize on partial information, conversion tracking reports incorrectly, and retargeting audiences fail to build properly.

Read the full breakdown of why Google Ads tracking fails →

What this checks

  • Cookies set before consent - detects non-essential cookies (GA, _gcl_au, _fbp) created before user consent
  • Tracking scripts before consent - identifies Google Analytics, Meta Pixel, and other tracking scripts firing too early
  • Google Consent Mode v2 - verifies proper Consent Mode v2 implementation with default denied states
  • Conversion tracking behavior - checks if conversion events fire before consent and after user accepts
  • Consent banner validity - validates structural parity between accept and reject options
  • IAB TCF consent signals - reads declared consent via TCF API and compares it to actual tracking behavior to detect mismatches

Why this matters

When tracking is broken, Google Ads cannot measure conversions accurately. This has direct business impact:

  • Ads optimize on incomplete data - Google's machine learning works with partial signals, reducing campaign performance
  • Retargeting audiences may not populate - visitor lists stay empty or incomplete, breaking remarketing campaigns
  • Conversion reporting may be inaccurate - you see fewer conversions than actually occur, making optimization decisions unreliable
  • Consent Mode modeling may be suppressed - Google cannot use modeling to fill gaps when Consent Mode isn't properly configured

What this is NOT

  • Not legal advice - this tool checks technical implementation, not legal compliance
  • Not a compliance platform - it diagnoses issues, but doesn't manage ongoing compliance

Who this is for

ConsentCheck is for people who need to know whether consent and conversion tracking are technically working in the browser - not as a legal opinion, but as a fast diagnostic.

  • Performance marketers and PPC teams checking if Google Ads is measuring correctly
  • Analytics / tracking specialists debugging tags, Consent Mode v2, and CMP behavior
  • Developers wiring consent banners and GTM who want to validate browser behavior
  • Agencies that need before/after proof of fixes for many client sites

For a more detailed breakdown, see who this is for →

Common issues found

  • Consent Mode v2 missing - the most common issue, causing Google Ads to suppress conversion data entirely
  • GA4 fires before consent - Google Analytics loads and tracks users before they accept, invalidating consent
  • Conversion events not firing - conversion tracking code exists but may not fire because consent is never properly granted
  • Reject doesn't block tracking - clicking "reject" has no effect, tracking continues regardless

Catch breaks before they hurt

A one-time scan tells you how things look right now. Site or CMP updates can re-break consent and conversion tracking later. With monitoring, we scan your URLs on a schedule (daily, weekly, or monthly) and email you when something changes.