In short: in a mature account what fails isn't a tag: it's that nobody has the map of which signal reaches Google, from where, with what value and who is responsible for it. The audit is 25 points in five blocks, and the priority when fixing is always whatever changes what the algorithm learns. Server-side tagging is the finishing touch, not the first step.
With everything we have covered, a mature account has half a dozen conversion sources, several values and two or three systems talking to each other. What goes wrong in those accounts is not a tag: it is that nobody has the map. This lesson closes the module with the map and the audit.
What is an account's measurement map?
A one-page table that ought to exist in every account:
| Action in Ads | Type | Source | Trigger | Value | Counting | Window | Owner |
|---|---|---|---|---|---|---|---|
| Purchase | Primary | Tag (GTM) | Thank-you page / purchase event | Dynamic, excl. VAT | Every | 30 d | Web |
| Qualified lead | Primary | Offline (CRM sheet) | CRM status "qualified" | €80 | One | 60 d | Sales |
| Sale (lead) | Primary | Offline (CRM sheet) | Status "won" | The amount | One | 90 d | Sales |
| Form | Secondary | Tag (GTM) | form_submit event | The score | One | 30 d | Web |
| Show phone number | Secondary | Imported from GA4 | click_tel event | €5 | One | 7 d | Web |
| Call from ad | Primary | Google (calls) | > 60 s | €60 | One | 30 d | Ads |
If you cannot fill in a row, there is your first finding.
What does a measurement audit check?
Foundations
- Google tag on every page; a single instance.
- Auto-tagging on; the GCLID reaches the landing page after redirects.
- Consent Mode v2 advanced detected; a certified CMP; rejecting as easy as accepting.
- Enhanced conversions (web) on and verified.
Actions
- Primary = only what you would pay for; secondary the rest; no "orphan" action sitting unused.
- Counting set to "one" on leads, "every" on purchases.
- Windows matched to the measured conversion delay.
- The right conversion goal on each campaign (not "all").
- Coherent conversion categories.
Values
- Values on every primary action; excluding VAT; with the right currency.
- L1 < 50% of total value.
- Adjustments for returns/cancellations up and running.
- Fixed values reviewed within the last 6 months.
Offline and CRM
- The GCLID (or email/phone) stored per lead in the CRM.
- Qualified and sale uploads automated; no duplicates (order/lead id).
- Monthly Ads ↔ CRM reconciliation per lead.
- The sales team marking statuses.
GA4 and attribution
- GA4 linked; no primary action duplicated between the tag and GA4.
- GA4 audiences published and in use.
- Data-driven attribution model; windows reviewed with the path report.
Operations
- A monthly end-to-end test (ad → form → CRM → Ads).
- Conversion diagnostics with no warnings; conversion email alerts on.
- Data exclusions created for known broken periods.
- The map above exists, is up to date and somebody owns it.
- A "what is measured where" document for whoever writes the reports.
What is server-side tagging and when do you need it?
With server-side tagging (server-side Tag Manager), tags do not run in the user's browser but on a server of yours, which receives the events and forwards them to Google. Advantages: less loss to blockers and restrictive browsers, more control over what data leaves, better site performance, longer-lived first-party cookies. The cost: a server (or a managed service) and a technical implementation. When: accounts with high spend where every measurement point lost is worth money, or with strict privacy requirements. It is not the first step; it is the last refinement once everything above is done.
Where should you start fixing?
Sort them by impact: first whatever changes what Google learns (wrongly chosen primary actions, values, offline, duplicates); then whatever loses data (consent, enhanced conversions, the tag); and last whatever confuses the reading (GA4, attribution, documentation). And after each fix that changes conversions: a data exclusion for the previous period if one was needed, and a warning that Smart Bidding will go into learning.
💡 Ninja trick: the Ninja Scripts Agent checks several points from this list in every account every day (actions that stop recording, jumps, the weight of L1, conversions with no value) and Lead Rating covers the offline and CRM block out of the box. The full audit is still quarterly and human; watching for what breaks between audits is daily and automatic.
What you should remember
- The problem in mature accounts is the lack of a map: which signal, from where, with what value, and who is responsible.
- A 25-point audit in five blocks: foundations, actions, values, offline/CRM, GA4/attribution, operations.
- Prioritise whatever changes what Google learns.
- Server-side: a final refinement for large accounts, not a first step.
End of Module 8. Module 9 goes back to the money from above: budgets and planning — curves, impression share and how to split your investment.