Tracking & Consent · Conversion Guard

Your tracking is silently broken — and it's costing you conversions and compliance.

Consent Mode v2 is where Google’s ad-data quality and GDPR become the same technical problem. Conversion Guard scans your live site the way a real visitor’s browser does, and shows you exactly where the signal is leaking — in money terms and the fix.

Run a free scanSee what we check
  • No code to install
  • 60-second scan
  • GDPR + Consent Mode v2
your-affiliate-site.comRED
58score
CriticalTag fires before consent
HighConsent Mode v2 not wired (gcs)
MediumGA4 conversions under-reported

Illustrative scan result

The stakes

Broken tracking is lost revenue and a compliance gap — at the same time

“You’re bidding, reporting, and optimizing on numbers that are quietly wrong — and the same misfire is a GDPR exposure. One scan, two problems.”

20–40%
of conversions can go under-reported when Consent Mode v2 isn’t sending signals correctly — shrinking the data Google optimizes on.
Illustrative range; varies by traffic mix and CMP setup.
€20M / 4%
of global turnover is the GDPR ceiling for consent failures — the same misconfiguration that costs you conversions.
GDPR Art. 83 maximum; not a prediction of your exposure.
Every deploy
a CMP tweak, a new tag, or a theme change can silently break tracking between the audits you actually run.

What we monitor

Every check is a versioned rule — deterministic, with evidence

Conversion Guard loads your public pages in a real browser across the reject and accept paths, then scores what actually fires against a versioned rule-pack.

Consent-gated tracking

Whether trackers respect consent — before and after the banner.

  • Trackers firing before consent is granted
  • No tag/cookie leakage on the reject path
  • Reject-path parity (dark-pattern detection)

Consent Mode v2 wiring

Whether Google is actually receiving the consent signals it needs.

  • Consent signal (gcs) granted/denied across reject and accept
  • ad_storage / analytics_storage / ad_user_data / ad_personalization
  • Default vs. update consent calls in the right order

Conversion-event integrity

Whether the conversions you optimize on are actually being measured.

  • GA4 / Google Ads / Meta Pixel presence and configuration
  • Conversion events firing once — not missing, duplicated, or dead
  • Key purchase / signup events reaching their endpoints

Change detection

What broke since last time — so regressions surface the day they happen.

  • Diff vs. the previous scan
  • New or removed third-party scripts
  • Score regressions flagged automatically

How it works

One scan, four outputs

  1. 01

    Scan

    We load your pages in a real browser across reject and accept, capturing every tag, signal, and network call.

  2. 02

    Findings

    A deterministic rule-pack scores what fired — each finding carries severity, plain money/compliance impact, and the fix.

  3. 03

    Evidence

    Every finding is backed by timestamped artifacts: DOM snapshot, HAR, screenshot, and a proof hash.

  4. 04

    Report

    An exportable tracking-integrity report — plus change detection that alerts you when a deploy breaks something.

Sample finding

This is what a finding looks like

CG-014Critical

Consent Mode v2 sends no signal after the visitor accepts

Impact

Google isn’t receiving consent signals, so conversions are under-reported and your remarketing audiences are shrinking. You’re optimizing bids on numbers that understate reality — and the gap is also a GDPR consent-wiring defect.

Fix

Fire the gtag consent `update` (ad_storage, analytics_storage, ad_user_data, ad_personalization) on accept, before the conversion tags, then re-scan to confirm the reject path stays clean.

DOM snapshotHAR network logScreenshotproof_hash

What’s in the report

  • Every finding with severity, plain money/compliance impact, and the exact fix
  • Timestamped evidence artifacts (DOM, HAR, screenshot) per finding
  • Deterministic score and status (GREEN / YELLOW / RED) with the penalty breakdown
  • Consent Mode v2 signal matrix across the reject and accept paths
  • Change-since-last-scan diff and an exportable PDF

Find your gaps in 60 seconds

Run a free scan and see exactly what’s broken — the lost conversions and the compliance gaps, with the fix for each. No install, no card.

Run a free scanStart free trial

Free scan needs no card · Continuous monitoring on the trial · Cancel anytime

FAQ

Questions, answered

Do I need to install anything?

No. Conversion Guard scans your public pages from the outside, the way a visitor’s browser does — nothing to add to your site to get your first results.

What exactly is Consent Mode v2 and why does it matter?

It’s how your site tells Google whether a visitor consented to ads and analytics storage. Wired wrong, Google stops receiving conversions and your audiences shrink — and the same misconfiguration is a GDPR consent defect. It’s the one place where ad-data quality and compliance are the same technical problem.

Does it fix my tracking, or just find the problems?

It finds and proves them, with the exact fix for each finding and timestamped evidence. Your team (or ours, on higher tiers) applies the fix; a re-scan confirms it’s resolved and the reject path stayed clean.

How is the score calculated?

Deterministically. Each failed rule deducts a fixed penalty by severity, so the same site always produces the same score — no black box, no ML guesswork.

How often does it scan?

Continuously, on a schedule, with change detection — so a CMP tweak or a new tag that breaks tracking is caught the day it happens, not at your next manual audit.

Also protecting this site