Foundation · build guide
Measurement Repair
Fix conversion tracking across GA4, Google Ads, and Meta before automation touches spend
What it does
Measurement Repair is a full audit and rebuild of your conversion tracking across GA4, Google Ads, and Meta. You inventory every conversion event, reconcile counts across platforms, trace the events that disagree, fix deduplication, validate attribution settings, and document everything in an event dictionary that anyone touching the account can check.
It sits in the Foundation category because every automation downstream optimizes toward whatever your conversion data says. If events double-count or silently drop, Smart Bidding and every rule you add will confidently scale the wrong thing. Repair measurement once and each new automation inherits data it can trust; skip it and each new automation amplifies the error.
You run the whole repair with platform exports, tag-manager preview tools, and one spreadsheet. It suits a marketer with admin access and a couple of hours a day for two weeks — no engineering help needed beyond publishing tag changes.
The same audit runs as a standing loop: read-scoped API connections feed an agent that reconciles counts daily, traces discrepancies, and stages fixes for your approval. It suits teams whose site changes often enough that tracking breaks between manual audits — and who want the repair to stay repaired.
Before you start
Prerequisites.
Path A
Build it with manual data extracts.
You run the whole repair with platform exports, tag-manager preview tools, and one spreadsheet. It suits a marketer with admin access and a couple of hours a day for two weeks — no engineering help needed beyond publishing tag changes.
Build the event inventory
Open GA4's key events list, the Google Ads conversion actions page, and Meta Events Manager, and list every conversion event in one spreadsheet tab. For each event, record where it fires from (GTM tag, hardcoded, imported), its counting method, and the value it carries. This tab becomes your event dictionary — the deliverable everything else feeds.
Export and reconcile counts
Export the last 30 days of daily conversion counts and values from each platform into separate tabs, then build a reconciliation tab that lines the same event up across sources. Flag any event where platforms disagree by more than a margin you choose, plus anything reporting zero or roughly double what you'd expect.
Trace every flagged event
Use GTM preview mode and Tag Assistant to fire a test conversion and watch which tags fire, how many times, and with what values; on the Meta side, use the test events tool in Events Manager. Record the failure mode for each flagged event: duplicate fires, missing dedupe keys like transaction ID or event ID, wrong values, or tags installed both hardcoded and in GTM.
Fix one change at a time
Make each fix in a fresh GTM workspace: add transaction IDs to dedupe purchases, remove double-installed tags, correct counting settings, repair value parameters. Publish one change per version and log it in a change-log tab with the date, what changed, and why — that's what makes any fix reversible.
Validate attribution and primary conversions
In Google Ads, confirm which conversion actions are primary (used for bidding) versus secondary (observation only), and that Smart Bidding optimizes toward one deduplicated revenue event rather than a mix of overlapping ones. Check GA4-imported versus native-tag conversions so the same purchase isn't counted twice.
Re-reconcile and publish the dictionary
After a week of clean data, re-run the exports and confirm the platforms now agree within your margin. Finish the event dictionary and put it where anyone building a rule or report will find it. From here, nothing gets automated on an event that isn't in the dictionary.
Cadence: The initial repair takes about two weeks; after that, re-run the export-and-reconcile pass monthly and after any site release or tag change — roughly an hour per cycle.
Path B
Integrate it with MCP connections.
The same audit runs as a standing loop: read-scoped API connections feed an agent that reconciles counts daily, traces discrepancies, and stages fixes for your approval. It suits teams whose site changes often enough that tracking breaks between manual audits — and who want the repair to stay repaired.
Grant read access; keep publishing locked
Connect GA4, the Google Ads API, and the Meta marketing API through MCP servers or direct API credentials, all read-only to start. Add Google Tag Manager API access with permission to create workspace versions but not to publish. Credentials live in your automation platform — n8n, Make, or Claude with MCP servers — never in the spreadsheet.
Let the agent build the live event map
The agent enumerates every GTM tag and trigger, every Google Ads conversion action, and every GA4 and Meta event, then writes the combined inventory to an event dictionary in Google Sheets or BigQuery. Unlike a manual inventory, this one regenerates on schedule, so the dictionary can't quietly go stale.
Schedule the reconciliation loop
A daily job pulls conversion counts and values from all three platforms, compares matching events, and flags divergence beyond a threshold you set. Each flag ships as a short discrepancy report with the suspected cause — duplicate tag, missing event ID, value mismatch — and a link to the evidence.
Stage fixes behind an approval gate
For each confirmed issue, the agent drafts the exact fix as an unpublished GTM workspace version and posts the diff for review. You approve, the agent publishes, and the change log records before and after. Conversion settings inside Google Ads and Meta — counting methods, primary versus secondary, attribution — stay human-only: the agent recommends, you click.
Keep watching for drift
Once counts agree, the loop keeps running and alerts you the day a release breaks tracking, instead of you finding out from a bad month of Smart Bidding. Alerting is the default action; auto-applied fixes stay off unless you deliberately allow a narrow class of change, and even those remain reversible through GTM version history.
Tools & guardrails
Run it safely.
- One change per GTM workspace version, published only after human review — every fix reversible in one click via version history
- Conversion settings in Google Ads and Meta (counting method, primary/secondary, attribution) are human-only; the agent proposes, never edits
- Every discrepancy report, staged fix, and publish lands in the change log with before/after values and who approved it
- The agent never deletes events or tags — deprecated items are paused and documented so history stays intact
Want new build guides as they ship?
Optional — every guide on this site is free either way. Leave your details and we'll email you when new automations join the library, nothing else.
Prefer it built for you?
We stand this automation up as a governed sprint on the stack you already run — scoped, built, and handed over with the guardrails configured. No new platform, no migration.