Tracking that worked six months ago may be failing today: a new form, a site update or a change in the tag manager. A regular audit of tags, duplicate events and ghost conversions prevents months of decisions based on wrong data.
The essentials in a definition
Tracking quality depends on tags that fire only once, events with consistent names and values, and conversions that match real sales. A regular audit of tags and events, supported by the tag manager and GA4 events, detects duplicate events and phantom conversions before they distort optimisation.
The silent problem
When tracking fails, numbers change subtly. Conversions drop or rise without explanation, cost per result looks odd. Often it is only noticed when someone compares with real sales, weeks or months later.
In that time algorithms have learned from wrong data and budget decisions have followed.
What to check
Tags firing on the right pages and only once. Events with consistent names and parameters. Correct conversion values (currency, taxes, shipping). Firing only after the action is completed. Respect for consent. Thank-you pages reachable only after the action.
Also check links between systems: analytics, ad platforms, CRM.
Auditing tracking
- Inventory tags and events
- Walk through the funnel as a real customer
- Compare what is sent with what is received
- Set alerts and an owner
How to audit
Use the tag manager’s preview tools and debugging extensions. Walk through the funnel like a real customer, on different devices, with and without consent. Compare what is sent with what the platform receives.
Keep an inventory: each tag, event, where it fires, who is responsible. Comparing the inventory with reality quarter by quarter catches drift.
Tracking breaks silently; only an audit catches it in time.
Preventing problems
Set rules: any site change that affects forms, checkout or thank-you pages requires a tracking test. Assign an owner. Configure alerts for abnormal drops in conversions.
Keep a reference person. When everyone thinks it is someone else’s job, nobody checks.
Decision table
| Check | How | Error sign |
|---|---|---|
| Duplicate tags | Preview mode and real time | Event fires twice per action |
| Phantom conversions | Compare with the sales system | More conversions than sales |
| Values and currency | Make a test purchase | Zero value or wrong currency |
| Device coverage | Test on mobile and desktop | Events only on one device type |
Common mistakes to avoid
- Auditing only after a problem. Do it quarterly and after major site changes.
- Testing only on desktop. Many failures only appear on mobile.
- Not documenting. Without a tag inventory, nobody knows what exists.
How to measure the result
Keep an inventory of tags and events with a verification date, and track the ratio between recorded conversions and real sales after each audit.
Limits and exceptions
A tracking audit does not find everything: intermittent failures, problems on rarely visited pages or uncommon devices can slip through. Test the most important journeys, on several devices, and combine the audit with continuous alerts that detect sudden drops. For complex sites, consider specialist support and always log site changes that may affect measurement.
Illustrative example
Illustrative example: a shop finds, in an audit, that the purchase event fires on the thank-you page and also on an email confirmation opened in the browser, duplicating conversions in about 15% of cases. It fixes this with a transaction ID and now checks a test purchase after each checkout change.
In practice: checkpoints
Run the audit with a fixed checklist: list every tag and the page where it fires, compare event counts with orders or leads in the database, test the thank-you page by reloading it, and record each fix with its date. Repeat after any site release, because a new theme, plugin or checkout step is the most common cause of duplicate or missing events.
Frequently asked questions
How often should I audit?
Quarterly and whenever the site, checkout or forms change.
What is a ghost conversion?
A conversion recorded with no real sale or lead behind it, because of a tracking error.
Do I need tools?
The tag manager’s preview and debugging extensions are enough.
How often should I audit tracking?
Quarterly, and whenever there are changes to the site, checkout or platforms.
What tool should I use?
The tag manager’s preview mode, GA4’s real-time view and a documented test purchase.
Auditing tags, events and conversions with an inventory, tests on several devices and comparison with the sales system avoids duplicates and phantom conversions.
Sources and recommended reading
- Tag Manager Help: introduction
- Google Ads Help: conversion measurement
- Analytics Help: GA4 recommended events
Last editorial review: October 2026. Informational content; always confirm current conditions in the official sources before deciding.