Services / Server side tracking
Server side tracking that
counts every consented sale.
Server side tracking and tagging for businesses losing conversions to browsers, blockers and broken pixels. We set up server-side GTM on your own subdomain, send purchases and leads to Meta and Google Ads properly, and keep consent mode v2 in charge of what is collected.
Builds from £2,500
Server-side GTM, First-party data, Meta CAPI, Enhanced conversions, Consent mode v2, Hosting
Sound familiar?
The platforms see
fewer sales than you made.
Browsers, ad blockers and short cookie lifetimes all chip away at what a browser pixel can see.
01
Missing conversions.
Meta and Google Ads report fewer purchases than Shopify or your CRM.
02
Cookies that expire.
Some browsers cut cookie lifetimes, so returning buyers look like new ones.
03
A crowded site.
Every tag loads its own script in the browser, and the pages pay for it.
04
Consent you cannot prove.
Tags fire before consent, or not at all, and nobody is sure which.
What you get
Tracking that runs on
your own server.
The browser sends one stream of events to your server container. Your server decides what goes where.
01 · sGTM
Server-side GTM.
A server container on your own subdomain, receiving events from the site and forwarding them to each platform.
02 · First-party
First-party collection.
Data collected on your domain, with cookies set by your server, so measurement lasts longer in browsers that limit scripts.
03 · Meta
Meta Conversions API.
Purchases and leads sent to Meta from the server, deduplicated against the pixel so each sale counts once.
04 · Google Ads
Enhanced conversions.
Google Ads conversions with hashed, consented customer data, for better matching of sales to clicks.
05 · Consent
Consent mode v2.
Your consent banner stays in charge. Nothing is sent server-side that a visitor has declined.
06 · Hosting
Hosting, costed up front.
Google Cloud or a managed host, sized to your traffic, with the monthly running cost agreed before we build.
What it fixes
What it fixes,
and what it doesn't.
Server side tracking is worth doing for many businesses. It is not a fix for everything.
01 · Fixes
Lost ad conversions.
Purchases and leads reach the ad platforms even when the browser pixel is blocked or cut short.
02 · Fixes
Short cookie lifetimes.
Cookies set by your own server last longer, so returning customers keep their source.
03 · Doesn't fix
Missing consent.
If a visitor declines, they are not tracked. Server-side is not a way around consent, and we will not set it up as one.
04 · Doesn't fix
A broken set-up.
Duplicate events and wrong values still need fixing first. A server container forwards whatever the site sends it.
How it works
Fix the basics,
then move server-side.
We fix the browser set-up first, because a server container only forwards what it is given.
01
Audit
Your tags, consent and conversions checked against real orders or leads.
02
Fix the basics
Duplicate events, wrong values and consent problems fixed in the web container.
03
Build server-side
A server container hosted on your subdomain, with Meta CAPI and enhanced conversions set up.
04
Test and monitor
Every consent state tested end to end, then match quality and running costs watched after launch.
Case study
Consent and server-side · UK humanitarian charity
239
Consented, server-side tracking for a UK charity
Analytics caught about 83% of one-off gifts and none of the recurring renewals. We designed one dataLayer, consent and source specification, then built consent mode v2, ad conversions with enhanced conversions, and pixel plus server-side events, tested in every consent state.
- 16 defects found in the existing set-up
- Consent mode v2 tested in every consent state
- Ad conversions with enhanced conversions
- Pixel plus server-side events
- 239 payments found that never reached the CRM
Client anonymised. Delivered with Kinsman & Co.
Read the case study →552
Uncounted purchases found for an online learning company
69%
Attribution over-count found for a Shopify Plus brand
5.3%
Revenue with no source, down from 51.9%
Price
Find out first
if it is worth it.
The audit tells you how much the browser is losing. The fee is credited against any build that follows.
- Tracking auditTags, consent and conversions checked against real orders, with a clear view on whether server-side is worth it.£1,950
- Server-side buildServer-side GTM, Meta CAPI, enhanced conversions and consent mode v2, tested and documented.from £2,500
- HostingServer running costs depend on traffic. You get the monthly figure in writing before we build.Quoted after audit
- PartnerMonitoring and fixes when sites, checkouts or platforms change.from £1,500 a month
Questions
Questions about
server-side tracking.
Click a question to open it.
Instead of every tag running in the visitor's browser, the site sends events to a server container you control, usually on your own subdomain. That server then forwards the data to GA4, Meta, Google Ads and the other platforms.
Near enough. Server side tagging usually means the server container in Google Tag Manager. Server side tracking is the wider set-up around it, including first-party collection and the conversion APIs.
Not always. If you spend meaningfully on ads, or many visitors use blockers or browsers that limit cookies, it usually recovers conversions the browser loses. If it is not worth it for you, we will say so.
It depends on traffic. Smaller sites can run on low-cost managed hosting, and busier ones need more capacity on Google Cloud. You get the monthly running cost in writing before we build.
No. Consent mode v2 stays in charge, and anything a visitor declines is not sent. Server-side improves the quality of consented data. It does not replace consent.
Yes. Purchases and leads go to Meta through the Conversions API, deduplicated against the pixel, and Google Ads gets enhanced conversions, so each sale is counted once.
Other services
Container clean-ups, consent mode v2 and server-side GTM.
GA4 audits and revenue that matches the bank.
The full stack, from consent to CRM revenue.
How many sales
are the platforms missing?
Send us your site and ad accounts. We'll tell you how much the browser is losing, and whether server-side is worth it for you.