Tracking you can trust: GA4, GTM and server-side
Your analytics will never count every order, because some buyers decline cookies. A GA4 consultant measures that gap, closes what a tracking plan and server-side tracking can close, and explains the rest in a monthly reconciliation that finance can check.
GA4 against the order system, example
GA4 caught 93.4% of October's orders, and consent declines explain 96 of the 128 it missed
Period October 2026
- Order system
- 1,940
- Orders placed on the website.
- GA4
- 1,812
- Purchase events with a transaction ID, 93.4% of orders.
- The gap
- 128
- Orders with no matching purchase in GA4.
| Cause | Orders | Share of the gap |
|---|---|---|
| Consent declined | 96 | 75.0% |
| Blocked (consent granted, no GA4 client ID) | 23 | 18.0% |
| Unexplained | 9 | 7.0% |
| Total | 128 | 100.0% |
What this fixes
Four signs the tracking can't be trusted yet.
A tracking plan, and the setup that follows it
The plan, container and checks your team keeps.
GA4 will never count every order, so the figure worth reporting is how many it misses and why.
Tracking plan extract
| Event | Trigger | Key parameters | Consent |
|---|---|---|---|
view_item | Product page loads | items, value, currency | analytics_storage |
add_to_cart | The basket confirms the item was added | items, value, currency | analytics_storage |
begin_checkout | First view of checkout step one | items, value, currency | analytics_storage |
purchase | Confirmation page, once per order number | transaction_id, value, tax, shipping, currency, items | analytics_storage, plus ad_storage and ad_user_data for ad tags |
Example data
How it runs
From audit to handover, in accounts you own.
- 1
Scoping
An audit of the GTM container and a month of GA4 purchases matched to the order system. That gives the starting gap before anything changes.
- 2
Build
The tracking plan first, signed off by whoever owns each event. Then GTM, consent and, if the audit justifies one, the server container, each tested in preview against the plan, one consent state at a time.
- 3
Handover
Your team gets the plan, admin access on every container and property, and a walkthrough of one new event going from a row in the plan to a published tag.
- 4
Afterwards
The GTM containers and the GA4 property sit in your accounts, with your team as admins. The reconciliation carries on monthly, run by your team from the same query.
Where conversion tracking goes wrong
Three common tracking faults and the guard against each.
The tracking plan is written before any tag changes. A tag with no row in the plan has no owner, so nobody notices when it breaks.
What Consent Mode v2 collects, and what it models
What Google receives when a visitor declines cookies.
Consent Mode passes the visitor's choice to Google's tags through four signals: ad_storage, analytics_storage, ad_user_data and ad_personalization. Version 2 added the last two, which govern whether user data goes to Google for advertising and whether it can be used for personalised ads.
In basic mode, Google's tags don't load until the visitor accepts, so a decline sends Google nothing. In advanced mode, the tags load with consent denied and send cookieless pings. GA4 can then model the behaviour of visitors who declined, but only once the property meets Google's eligibility thresholds. Modelled figures are estimates, and the reconciliation keeps them out of the count.
What server-side tracking changes
What a server container changes, and what it costs.
In a standard setup the browser sends each event straight to Google and to every other vendor. With server-side tagging, the browser sends one stream to a server container on your own subdomain, and the container forwards it to each vendor. You decide what each one receives and can reshape the data before anything leaves.
Consent works exactly as before. A visitor who declined is still declined, and the container has to honour it. Hosting costs money every month, so server-side tracking gets recommended when the audit's blocked share or the number of vendors justifies it.
Conversion tracking by industry
How the tracking plan changes by sector.
The subscription and media and financial services pages show which systems hold those events in each sector.
Tracking usually comes first. Experiments and marketing measurement both read from the events it defines, and data infrastructure takes the reconciled data into a warehouse.
Questions people ask
Answers on GA4, consent, renewals and inherited containers.
Do you set up GA4 for ecommerce?
Yes. The tracking plan uses GA4's recommended ecommerce events, from view_item through to purchase, and every purchase carries the order number as its transaction ID. That ID is what lets GA4 be matched to the shop's orders every month.
Does a subscription business need server-side tracking?
Usually for renewals. A renewal happens in the billing system with no browser open, so it either goes to GA4 server to server through the Measurement Protocol or stays in the billing data and gets joined in the warehouse. Scoping settles which, based on whether marketing needs renewals in GA4 at all.
Can you set up conversion tracking for financial services?
Yes. A quote can take several sessions and end on the phone, so the plan states which system records the sale and how it links back to the web journey. No name, email or policy number goes into any event parameter.
Will Consent Mode v2 bring back the data we lose when people decline?
It can estimate some of it. In advanced mode GA4 models the behaviour of visitors who declined, once your property passes Google's thresholds, and the modelled figures are estimates. The monthly reconciliation counts observed purchases only, so the gap stays visible.
Can you work with the GTM container another agency built?
Yes. The audit starts from the container as it is. Every tag gets mapped to a row in the tracking plan, and a tag nobody can map is paused, then removed once a month of reconciliation shows nothing depended on it.
Book a call about your tracking
Bring last month's order count and GA4's purchase count, and the first call works out what the gap between them is made of.