Skip to content
Guide

How to switch to server-side tracking

Your Google, Meta and LinkedIn campaigns report fewer sales than your back office. The cause often lies in the source of the collection: your visitors' browsers. This guide explains what server-side tracking is, how to tell whether it applies to you and how to set it up, whether you do it yourself or hand it over.

20-40%
of conversions that browser pixels never see
7 days
lifetime of a JavaScript cookie on Safari
8 steps
from mapping conversions to going live

Server-side tracking in 2 minutes

Today, when a visitor converts on your site (a transaction, a subscription, a form), their browser is what tells Google Ads, Meta, LinkedIn, Google Analytics and every other platform. Each platform drops its own piece of code, reads its own cookies and sends the conversion notification from the visitor's browser. That is client-side tracking: everything starts in the client, meaning the browser.

Server-side tracking changes the route. Your site sends the conversion to a server that belongs to you, hosted on a subdomain of your own domain (sst.mysite.com, for example). That server receives the data, applies the visitor's consent choice, then forwards the conversion to each platform through its server-to-server interface: the Meta Conversions API, the Google Ads API, TikTok, LinkedIn, GA4.

Visitors see no difference. Analytics solutions and ad platforms receive data that was blocked by neither ad blockers nor the third-party cookie restrictions that apply on the client side.

1. Your site

The browser packages the data

The Google Tag Manager container captures the purchase, quote request or booking together with its details: amount, currency, order number, items.

2. Your server

sst.mysite.com

A subdomain of your site receives that data. Browsers recognise it as first-party: the cookies it sets last, the information survives. The server reads the consent choice before it forwards anything.

3. Your platforms

Each one receives the conversion through its API

Meta, Google Ads, GA4, TikTok, LinkedIn, Pinterest and Snapchat are served from the server, with the same data.

The vocabulary you will come across

Web container and server container
2 types of Google Tag Manager container. The first lives in the browser on the client side, the second runs on your server. The first one forwards to the second.
First-party
Anything that comes from your own domain. Safari, Firefox and Brave treat a first-party cookie far more generously than one set by a third-party domain.
Data layer
Your site's data layer: a structured list of the useful information (product, price, transaction ID, visitor data, funnel step) that tracking reads.
Conversions API
The server-to-server channel of ad platforms. Meta calls it CAPI, Google speaks of enhanced conversions and the Google Ads API.
Consent Mode v2
The Google mechanism that passes the visitor's choice (advertising accepted or refused) to every tag, in the browser and on the server.
Deduplication
The event identifier shared between the browser hit and the server hit, which lets a platform recognise one single conversion.

Does it apply to you?

Server-side tracking repairs a data loss. That loss still has to cost you something. Here is how to check in an hour, before spending a single euro.

6 signals of a leaking setup

  • Your ad platforms report fewer sales than your back office. Compare last month's total conversions with your real orders. A gap of 15% or more is worth the exercise.
  • A large share of your traffic comes from iPhone. Look at the browser breakdown in GA4. Above 30% Safari, the 7-day cap on JavaScript cookies weighs heavily.
  • Your customers take more than a week to decide. Decisions that take time, between the ad click and the purchase: the conversion can end up credited to another channel such as direct.
  • Meta shows a low event match quality. In Events Manager, a score below 6 out of 10 means conversions of poor quality for optimising your campaigns.
  • Your ad budget is above 1,500 € per month. That is the order of magnitude where 20% of invisible conversions cost more over a year than the migration itself.
  • Safari shortens the cookie lifetime further, from 7 days to 24 hours. The purchase is poorly attributed to the campaign that generated it.

When it is better to wait

The main gain of server-side tracking concerns paid advertising. Without an ad budget, what remains is measurement comfort that does not always justify the investment, especially for a small business.

  • Your traffic comes mostly from organic search
  • You have very little incoming traffic
  • Your site is moving to another platform in the coming months

In those 3 cases, start with clean browser tracking. Server-side sits on top of it later, with nothing thrown away. See the tracking expertise

What to gather before you start

A server-side migration rarely stalls on technique. It stalls on a missing access or a DNS zone nobody knows how to edit. Gather this list up front and the project is measured in days.

If one item is missing, it gets clarified when you get in touch and sorted out during the migration.

Access to your DNS zone

At your host or registrar, to create the technical subdomain

Administrator rights

Google Tag Manager, GA4 and every ad account to reconnect

A GTM container on the site

Or the ability to add one, through your CMS or your developer

A certified consent banner

Cookiebot, Usercentrics, Axeptio, UniConsent: it has to handle Consent Mode v2

A hosting budget

From 25 € per month depending on volume, on top of the setup

The list of your conversions

What you want to maximise, ordered by how much it matters to revenue

A baseline reading

Conversions, CPA and ROAS of the last month, platform by platform. This is your point of comparison

Server-side tracking: yourself, with an agency or with a freelancer?

3 options, each with its advantages and its drawbacks.

Do it yourself

A technical profile in-house, the Google documentation and a server container host.

Time from your team
High the first time: learning, configuration, testing
Direct cost
Container hosting, from 25 € per month
Quality of the result
Varies, it depends on the tests you run

What you gain

  • No service budget
  • The skill stays inside the company
  • You move at whatever pace suits you

What it really costs

  • One consent or deduplication mistake skews your numbers for months
  • A slow build and a slow learning curve, taken away from your marketing or your IT department
  • Open questions that can stay open

For whom: a team that already knows GTM and has time ahead of it.

Go through an agency

A structure that often runs your campaigns too, with a contract and a team behind it.

Calendar time
4 to 10 weeks, scoping included
Direct cost
The highest of the 3 routes, often with a retainer
Quality of the result
High when it truly masters server-side tracking

What you gain

  • Continuity if your contact leaves
  • Several trades under one roof: media, development, analysis
  • A contractual frame that suits large groups

What it really costs

  • The person who sells the project is rarely the one who configures it
  • The price includes the structure: offices, project managers, internal meetings, reviews
  • It also includes the agency's own costs: advertising, SEO, sales staff, lost pitches
  • Server-side configuration is sometimes subcontracted to a specialist, with a margin on top
  • When the same agency runs your campaigns and measures their results, the agency is judge and jury

For whom: a group, several markets or several sites to handle in parallel.

My job

Hand it to a specialised freelancer

The person who answers you is the one who configures the container and tests every conversion.

Calendar time
1 to 2 weeks, access and DNS included
Direct cost
1,500 to 3,500 € for an SME
Quality of the result
Very high, focused on the objectives you set

What you gain

  • One contact, from scoping to production
  • A fixed price known before the work starts
  • The accounts and the infrastructure stay your property

What it really costs

  • One person: their availability drives the schedule
  • Campaign management stays with you or with your agency
  • Possibly fewer edge cases already met than in an agency

For whom: an SME that wants the result live this month.

The 8 steps of a migration

The sequence is the same whether you do the work or delegate it. Use it as a reading grid for any quote you receive.

  1. Map the conversions

    List the domains, subdomains and actions to measure: purchase, add to cart, form, call, booking. For each one, note what triggers it and the data that comes with it. This document becomes the specification for everything that follows.

  2. Choose where the server container runs

    2 routes: Google Cloud directly, more flexible and more technical, or a specialised host such as Taggrs, Stape or Addingwell, which handles updates and infrastructure for a few dozen euros a month. For an SME, the second route costs less and needs less upkeep.

  3. Create the server container and its subdomain

    The server container is created in Google Tag Manager, then tied to a subdomain of your site through a DNS record. This point decides everything: a subdomain of your domain makes the collection first-party. A domain provided by the vendor takes you back to square one.

  4. Add or complete the data layer

    The server forwards what it is given. Without an amount, a currency and an order ID, platforms receive an empty conversion. On Shopify, WooCommerce or Prestashop, an extension provides the basics. On a custom site, this step needs a developer or advanced technical knowledge.

  5. Point the web container at the server

    In the site's GTM container, the GA4 tag receives the address of your server container. From then on, data travels through your subdomain before reaching Google. That is the switch itself, reversible with a single publication.

  6. Reconnect each platform to its API

    Meta CAPI, Google Ads, TikTok, LinkedIn, Pinterest, Snapchat: each platform gets its tag in the server container, with its access token. Email and phone are hashed in SHA-256 before sending. An event ID shared by both hits prevents the same sale from being counted 2 times. Be careful not to send personal data to your analytics solutions.

  7. Wire up consent

    Consent Mode v2 carries the visitor's choice all the way to the server container, which blocks advertising hits when there is no agreement. Your banner has to be Google-certified and fire its signals at the right moment, before tags load.

  8. Test, publish, compare

    Every conversion is tested end to end, with and without consent, in the preview mode of both containers and then inside each platform. After publishing, let it run 14 to 28 days and compare with the baseline: conversions reported, CPA, ROAS, Meta match quality.

The mistakes that cost the most

These 6 mistakes pass technical acceptance without a sound. They are paid for in budget decisions taken on false numbers.

A subdomain that is not yours

Hosting the container on the vendor's domain cancels the point of the whole exercise: browsers see a third party and apply the same restrictions as before. Check that the server address ends with your domain.

Conversions counted 2 times

When the browser pixel stays active alongside the server hit without a shared event ID, Meta and Google record 2 sales for 1. ROAS climbs on screen while revenue stays the same.

Consent forgotten on the server

A server that forwards everything, including visitors who refused advertising, puts you in breach of the GDPR. Consent Mode v2 is wired all the way to the server container and tested refusal by refusal.

Personal data sent in clear text

An email sent without hashing, an order reference containing a name, an address sitting in the URL of a confirmation page: server-side makes it easier to send user data, and therefore easier to leak it. See how to handle personal data in URLs

Migrating without a baseline

Without the conversions, CPA and ROAS of the last month, the gain stays an impression. The reading takes 20 minutes, do it before you switch.

The checkout left aside

Many sites hand payment over to another domain. If the mapping ignores it, the purchase is lost at the exact point where it matters most. This case is handled at step 1.

Checking that it works

5 checks you can run yourself, even when somebody else did the migration.

  • The server address carries your domain

    In your browser's network tab, filter on "collect". Requests should leave towards your technical subdomain.

  • Cookies last beyond 7 days on Safari

    In the developer tools, under Application, check the expiry date of the measurement cookie. That is the sign it is set on the server side.

  • Meta recognises the deduplication

    In Events Manager, each conversion should appear once, with deduplicated hits noted and a rising match quality.

  • A consent refusal does block advertising hits

    Refuse advertising on the banner, run a test conversion and confirm that no ad platform receives it.

  • The gap with the back office narrows

    14 to 28 days after going live, compare the conversions your platforms report with your real orders. That is the only measure that counts.

A dashboard that reconciles platform conversions, GA4 and your back office makes that check permanent. It is the natural extension of a successful migration. See my dashboards expertise

Frequently asked questions about server-side tracking

Client-side means the visitor's browser talks straight to Google, Meta and the other platforms. Server-side means it talks to a server hosted on a subdomain of your site, which relays the information to the platforms. The second route escapes ad blockers and the limits placed on third-party cookies.

No. A visitor who refuses advertising on your banner has to stay out of advertising hits, and the server applies that choice exactly as the browser would. What server-side recovers are the conversions of visitors who accepted and whose data was lost for technical reasons: a blocker, a cookie restriction, an expired cookie.

Yes when consent is applied all the way to the server, IP addresses are masked before transmission and your privacy policy describes the processing. Server-side even improves control: you see what leaves your site and you can decide what stays with you. Have the privacy policy paragraph reviewed by your legal adviser.

On Shopify, WooCommerce, Prestashop or Lightspeed, an extension provides the data layer and the migration happens without touching the code. On a custom site or a single-page application, plan a few days of development to expose the order data. The DNS change itself takes 5 minutes at your host.

Conversions come back from day one. The effect on performance takes longer: bidding algorithms relearn on the new data for 2 to 4 weeks. Vendors of server-side solutions report an average ROAS improvement of 15%, a market average that moves with the share of blocked traffic and your consent rate.

The web container stays in place: it is what captures the action on the page and sends it to the server. What changes is the destination. Some advertising tags are worth keeping active on both sides, as long as they share an event ID so the platform recognises a single conversion.

Server-side makes pages lighter: advertising scripts that used to run in the browser move to the server and the weight loaded by the visitor drops. The gains show up mostly on mobile, where every third-party script weighs on display time.

The budget reads in 3 lines: hosting the server container, from 25 € per month with a specialised host, the setup itself, and a few days of development if your site does not expose its order data yet. In-house, the setup costs time rather than money. My SME package runs from 1,500 to 3,500 € excluding VAT depending on complexity. An agency invoices more for the same container: its price carries its structure and what it spends to find you.

Yes. The switch lives in one setting of the web container: publishing the previous version brings collection back into the browser within minutes. That is also why every published version deserves an explicit name in Google Tag Manager.

Ready to take action?

Tell me about your site and your Ads platforms: you get a clear answer within 48 hours.

Get a quote