In this guide
- Server-side tracking means the browser sends one request to your own server, and that server forwards events to Meta, Google Ads, GA4 and others.
- Because the request goes to your own domain, ad blockers and Safari treat it as first-party and let more through.
- It fixes losses, not bad data. You still need consent, a clean data layer and a correct set-up.
Most websites track visitors by loading a dozen vendor scripts in the browser. Each script phones its own company: Meta, Google, TikTok. This is called client-side tracking, and it has been losing ground for years as browsers and blockers cut the connections. Server-side tracking changes one thing: the browser sends its events to a server you control, and that server sends them on. This guide explains how it works, what you gain, what stays hard and how to start.
How much is your tracking missing?
Put in your own numbers. This is an estimate, not a promise.
Most stores do not know this number. Start with 20% and compare it with the orders in your store.
That is the signal Meta and Google are missing when they decide who to show your ads to. Server-side tracking sends it back.
Check your tracking in one pass
This is an example. Run the check on your own site to see where yours stands.
How it works, step by step
The page collects the event
A purchase, a lead or a page view is pushed to the data layer, as before.
The browser sends it to your domain
Instead of many vendor domains, the request goes to something like track.yourstore.com.
Your server checks and shapes it
The server can drop fields you do not want to share, hash e-mail addresses and add data from your own systems.
Your server sends it on
It calls the Meta Conversions API, the Google Ads and GA4 endpoints and any other destination, each with the fields it expects.
The server is usually a Google Tag Manager server container, hosted on Google Cloud or on a host built for it. The container parts are explained in clients, tags, triggers and variables. Open Tracked is such a host: it runs the container, the domain and the Google Cloud side for you.
What you gain
More events survive
Ad blockers and privacy browsers block known vendor domains. Your own subdomain is not on those lists.
Longer cookies
Cookies set by your server in an HTTP response can live longer than cookies set by JavaScript. See Safari ITP.
Faster pages
Fewer scripts load in the browser, so the page has less to do. See page speed and server-side tagging.
Control over your data
You choose what leaves your system, which helps with privacy rules such as GDPR.
Better matching
The server can add hashed e-mail, phone and location to events, which raises match quality at Meta, TikTok and Google. See Meta event match quality.
Server-only events
Orders, refunds and CRM stages can be sent from your backend or CRM, where the browser never sees them. See offline conversions.
3 things to remember
Scroll and the points stack up.
Server-side tracking means the browser sends one request to your own server, and that server forwards events to Meta, Google Ads,
Because the request goes to your own domain, ad blockers and Safari treat it as first-party and let more through.
It fixes losses, not bad data. You still need consent, a clean data layer and a correct set-up.
Browser, server, or both?
Most stores send the same event from the browser pixel and from the server, with a shared event ID. The platform sees both and counts the event once (this is called deduplication, see event deduplication). The server copy catches what the browser lost. The browser copy gives the platform fast, rich signals. Dropping the browser copy completely is rare.
What it does not do
- It does not remove the need for consent. Rules still apply to the data you send. See Consent Mode v2.
- It does not fix a broken data layer. Wrong or missing events stay wrong or missing.
- It does not make blocked requests reach your server if the blocker also blocks your own subdomain. This is rare but possible with aggressive filter lists.
- It is not free. You pay for the server, though the cost can be small. See how much a server GTM costs.
What it costs
A server container needs a server. On Google Cloud you pay for the instances yourself, which usually lands around $45 per instance per month, and you need at least two or three for stability. Managed hosts charge a plan fee instead and take care of the Google Cloud side. Open Tracked hosting plans are sized by monthly requests, from 15,000 on the free plan up to 20 million; see the pricing page. A request is one call to your tagging server. A store with 20,000 visits a month and about 15 events per visit sends roughly 300,000 requests.
When it is worth doing
If you spend on ads and your ad platform numbers are lower than your store numbers, you probably lose events in the browser. Stores that run Meta or TikTok ads, sell to many Safari or iPhone users, or have a visitor base with many ad blockers see the biggest gain. A site with no paid traffic and a handful of visits a day does not need it.
How to start
- Write down the events that matter: purchase, lead, add to cart. See GA4 event tracking.
- Choose a host and create a tagging subdomain on your own domain. See DNS for a custom domain.
- Import the web and server container files, or use a wizard that does it for you.
- Send a test purchase and check it in Preview and in the platform's test tool.
- Add the Conversions API next to the pixel, with a shared event ID.
- Wait a week and compare platform counts to your store.
Terms you will see
- Server container
- The Google Tag Manager container that runs on a server and receives events.
- Tagging server
- The machine or service that runs the server container.
- Custom domain
- A subdomain of your website, such as
track.yourstore.com, that points to the tagging server. - Conversions API
- The server-to-server endpoint of an ad platform, for example Meta's.
- Event ID
- A value sent with the browser event and the server event so the platform can count them once.
- First-party cookie
- A cookie your own domain sets. Server-set first-party cookies can last longer than script-set ones.
Checklist before you go live
Orders from your store, back to the ad that earned them
Your store sends the order once. Open Tracked passes it on to each ad platform, cleaned and deduplicated.
Frequently asked questions
Is server-side tracking the same as server-side tagging?
In practice yes. "Tagging" is the Google Tag Manager term, "tracking" is the wider name. Both mean events are sent from a server.
Does server-side tracking replace the Meta Pixel?
Not usually. Most set-ups send the same event from the browser pixel and from the server, and use an event ID so the platform counts it once.
Is server-side tracking GDPR compliant?
It can be, but it is not compliant by itself. You still need a lawful basis and, where required, consent before sending personal data. See server-side tracking and GDPR.
Do I need a developer?
For a standard store, no. A good host gives you a ready container and a wizard. Custom events or unusual platforms may need a developer.
How much more data will I get?
It depends on your audience. Sites with many Safari and ad-blocker users see more than sites with mostly desktop Chrome. Measure your own before and after by comparing platform counts to store orders.
Do I need spreadsheets to read my results?
No. Once tracking is live, the Open Tracked analytics shows spend, revenue, ROAS and profit, and you can ask Ari, the built-in AI assistant, questions about your own numbers in plain words. Ari's allowance depends on your analytics plan.
Is Open Tracked different from Open Track or Open Space Track?
No. Open Tracked is the official name of our server-side tracking platform, and the website is opentracked.io. Many people search for it as Open Track, OpenTrack or Open Space Track. All of them lead to the same product: server-side Google Tag Manager hosting, first-party analytics and a CRM pipeline.
Fix your tracking at the source
Open Tracked hosts your server-side Tag Manager, keeps first-party cookies alive and shows what each ad is really worth.
The Open Tracked team
We build Open Tracked: server-side tracking hosting, analytics and the tools around them, for stores that spend on ads. Questions about this guide, or an idea for the next one?
Comments
Loading comments...
Blog · 5 min read
