Find What's Breaking Your Google Ads Tracking
If your conversions dropped or don't match GA4, something is likely broken — but it's not always obvious what.
This scanner checks credible HTML-level signals (Consent Mode, GTM, GCLID hints, and tracking configs) and gives you a fast diagnosis before you waste spend on bad data.
What you'll get:
- Problem summary sentence (what looks broken)
- Confidence layer (HTML-level only)
- Fast signal checks: Consent Mode, GTM, GCLID hints, tracking configs
Want the exact issue + fix steps?
Get a full diagnostic report that detects what's blocking your conversions (consent timing, missing signals, attribution gaps).
Also validate firing: test conversion tracking.
Why Google Ads tracking breaks
Tracking breaks most often because consent state is wrong (or updates never fire), click IDs are lost (GCLID stripped by redirects), or tags fire before consent / never fire on the conversion path.
Google Ads not tracking conversions — common causes
- Consent Mode defaults are missing or run too late
- Consent update never fires on accept/reject
- GCLID is missing after redirects / cross-domain
- GTM/gtag triggers don't run on the real conversion path
- Duplicate tags or attribution settings create mismatches
How to fix Google Ads tracking issues
- Verify Consent Mode v2 defaults and update behavior
- Confirm your conversion fires after consent (accept/reject paths)
- Check GCLID retention and attribution signals
- Re-test after deploying fixes
Start with the money page: check your Consent Mode v2 setup.
FAQ
Why is Google Ads not tracking conversions?
Most commonly: consent state is wrong (or never updates), tags fire before consent, click IDs are lost, or the conversion never fires on the real user path.
How do I know if tracking is broken?
Use this scanner for fast signals, then confirm behavior using the conversion tracking test guide.
What should I do if the scanner says “unclear”?
Run the full Consent Mode v2 check to detect consent timing and missing signals more reliably.