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.

Last reviewed

GA4 against the order system, example

GA4 caught 93.4% of October's orders, and consent declines explain 96 of the 128 it missed

Example data

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.
Order numbers matched to GA4 transaction_id, 1 to 31 October, UK time.
The gap, by cause
CauseOrdersShare of the gap
Consent declined9675.0%
Blocked (consent granted, no GA4 client ID)2318.0%
Unexplained97.0%
Total128100.0%
Consent state saved to each order at checkout. Granted orders with no GA4 client ID count as blocked.
Example data: an invented shop's October. Each order missing from GA4 is put in one cause by the consent state and GA4 client ID saved on the order, and the 9 left over are the ones to investigate.

What this fixes

Four signs the tracking can't be trusted yet.

Two order countsThe shop's order count and GA4's purchase count disagree, and nobody can say which orders are missing or why.
A container nobody ownsGTM holds years of tags from several agencies, and nobody knows which ones the reports depend on.
The banner went liveGA4 numbers dropped the week the consent banner changed, and nobody can tell declines from a broken setup.
More conversions than ordersYour ad platform reports more purchases than the shop took. The first suspect is a confirmation page that fires the purchase tag again on reload.

A tracking plan, and the setup that follows it

The plan, container and checks your team keeps.

The tracking planA sheet with one row per event, giving its trigger, parameters, consent requirement and owner. Every tag in GTM maps to a row.
The GTM containerTags, triggers and variables named to match the plan, each published version noted with what changed.
Consent Mode v2Consent defaults set before any tag fires, the consent signals wired to your banner, and a test record of what fires in each consent state.
Server-side tagging, where it paysA server container on a subdomain you own, hosted in your own cloud account, with the running cost estimated before it's built.
The monthly reconciliationGA4 purchases matched to orders by transaction ID, with the gap split by cause, as in the exhibit. Each line of it carries its formula, as every figure does in our KPI library.

GA4 will never count every order, so the figure worth reporting is how many it misses and why.

Tracking plan extract

Tracking plan extract
EventTriggerKey parametersConsent
view_itemProduct page loadsitems, value, currencyanalytics_storage
add_to_cartThe basket confirms the item was addeditems, value, currencyanalytics_storage
begin_checkoutFirst view of checkout step oneitems, value, currencyanalytics_storage
purchaseConfirmation page, once per order numbertransaction_id, value, tax, shipping, currency, itemsanalytics_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. 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. 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. 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. 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.

A tagging change read as a sales changeConsent Mode goes live, GA4 purchases fall, and the fall gets reported as fewer sales. The guard is a dated change log of every tracking release, with the reconciliation showing the gap before and after it.
The purchase that counts twiceThe confirmation page fires the purchase tag again on a refresh or a revisit. The guard is a trigger that fires once per order number, plus a monthly check for duplicate transaction IDs in GA4.
A server container that ignores consentData reaches every vendor whatever the visitor chose, and the problem is now harder to see because it happens on a server. The guard is the consent state travelling with each event into the server container, where every vendor tag checks it before sending, and a test record for each state.

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 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.

EcommerceEvery purchase carries an order number, which makes the monthly match between GA4 and the shop exact.
Subscription and mediaA subscription starts in the browser and renews in the billing system, so the plan says which system records each event.
Financial servicesA quote can span several sessions and end on the phone, so the plan says where a sale gets recorded and how it links back to the visit.

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.

Book a call