hey squad
shall we settle in?

01 · TRK · 03/03

Server-side tracking.

Not for show. Not to tick the Meta box. For what iOS 18 broke.

You place a server endpoint between your site and Meta/Google. Your events keep flowing when browsers block them. Your ad arbitrage relies on real data, not on what survives ad-blockers.

By Jérôme · Strategy & data

Get my setup quotedSee the Ecostal mission

02 · OPERATION NOTE · OPS SERVER-SIDE TRACKING

Server-side tracking, decoded

The field report

Your ROASwhat your ads return per euro invested collapses while your CPCthe cost you pay per click stays stable. That's often the moment. Adblockad blockers, Consent Mode V2the Google consent framework and iOS 18 chip away 25 to 40 % of browser-side signal on the Belgian market in 2026.

The cost of waiting

Without server-side, you run your ad budgets on truncated data. You over-invest in channels that do not really convert, under-invest in those that do. The opportunity cost is invisible but very real.

In black and white

The conversion signal blocked browser-side. Clean cross-channel attributionlinking each conversion to its source channel. Data that holds up over time, despite the upcoming GDPRthe European personal data regulation, iOS and Chrome tightening.

The manoeuvre

We start by looking at what bleeds, before we touch any code. TAGGRSa server-side container host or GTM Server-Sidethe Google Tag Manager server link container depending on your stack. Deployed alongside your site, never replacing it. Clean handover to your team or existing agency.

The lock that breaks

AI automation and MLmachine learning running on reliable data. Full ownership if you change providers. Budget arbitrages based on real numbers, not estimates.

03 · WHAT WE WON'T WRITE IN AN RFP

Server-side tracking is a marketing decision tool. Not an IT project.

Server-side is only useful if you actually steer your ad arbitrage with it. Otherwise, you pay full price for half the benefit. The right question before signing the quote: who on your team will read the recovered data (via dedicated dashboards or internal tools) and turn it into budget decisions? If the answer is fuzzy, the right order is data governance first, then the server.

  • 01

    Recovered lost signal

    Your conversion events come back even when the browser blocks them. Adblock, Safari ITP, iOS 18, strict Consent Mode V2. The server receives, forwards, stores.

  • 02

    Clean multi-channel attribution

    You finally see which channel actually drives the final conversion. No more Meta + Google double-counting. No more blind arbitrage between Search, Social and Display.

  • 03

    Data ready for AI automation

    Once the server layer is in place, your data is structured and reliable. You can plug in automated budget optimization rules, lead scoring, product personalization.

  • 04

    Full data ownership

    You remove third-party scripts from your site. You regain ownership of the tracking layer. If you change agency tomorrow, the mechanic stays with you, documented.

04 · THE MISSION THAT PROVED IT

We deployed it for these clients.

Ecostal Group team handling a solar panel in their warehouse

Ecostal Group

B2B photovoltaic e-commerce

6-month server-side TAGGRS mission.

Read the Ecostal mission
Brasero estate, corporate retreats and weddings in Liège province

Brasero Group

Hospitality & events

24-month GA4 + dashboards tracking.

Read the Brasero mission
Amecam Van Conversion, mobile workshop fitted out in Wallonia

Amecam Van Conversion

B2B professional vehicle conversion

3-year B2B funnel tracking.

Read the Amecam mission

05 · THE PLAY-BY-PLAY

Four steps. Five weeks on average. Zero production freeze.

  1. STEP 01

    We look at what bleeds.

    Audit of the existing DataLayer + comparison GA4 vs Meta vs ad platforms. We measure the real gap between what fires site-side and what lands ad-side. Tools: TAGGRS (opens in a new window) Diagnostics, GA4 (opens in a new window) BigQuery export, Meta Events Manager Test Events.

  2. STEP 02

    We decide what we touch, what we leave.

    Target tagging plan, scope frozen in writing, client sign-off before any line of code. If some platforms are not worth the server-side move (low conversion volume), we say so. No silent scope creep.

  3. STEP 03

    We deploy the code alongside your site.

    Container TAGGRS (opens in a new window) Cloud Run or GTM Server-Side (opens in a new window) containerised depending on volume. Meta Conversion API + Google Enhanced Conversions wired up. Front-side, just a Custom HTML tag replaces third-party pixels. No production freeze.

  4. STEP 04

    We compare 14 days before vs after.

    A/B measurement on the same events, same attribution window. Looker Studio (opens in a new window) dashboard wired directly to GA4 + BigQuery (opens in a new window). Notion handover to your team or your media agency. Full ownership.

06 · THE FLOW AT A GLANCE

The path each conversion takes between your site and your ad platforms.

BROWSERvisitorEDGE1st-party domainGTM SERVERTAGGRS / sGTMorchestrate + enrichGA4 + BIGQUERYclean analyticsMETA CAPIAds attributionFUNNEL.IOdata lakeLOOKER STUDIOdashboardsadblock · iOS 18 · ITP[signal lost browser-side]

The server receives the event, enriches it, then dispatches it in parallel to the platforms that need the conversion read.

07 · NOT YET FOR YOU IF

Three cases where server-side tracking is not the top priority.

  • You refuse to touch the existing CMP.

    A clean server-side requires a clean Consent Mode V2. If the CMP is untouchable, we lose 60% of the benefit and cannot guarantee compliance.

  • Your annual ad spend is under 50 k€.

    The entry cost of a server-side setup is not paid back below this threshold. At these volumes, the ratio of data recovered to dev effort becomes debatable. We would rather say it than walk you into the dark.

  • You want to tick the Meta box without steering with it.

    No one on your side will read the recovered data to reallocate budgets. The cost of a server-side setup is not paid back by ticking a box.

08 · THE QUESTIONS WE ACTUALLY HEAR

Questions whispered after the second meeting. Honest answers.

On the Belgian market in 2026, estimates converge around 20-40% of conversion signal blocked browser-side. Our x-ray of 579 Liège e-shops adds the local data: 83% of sites show no trace of Consent Mode, so the lost signal is not even modelled there. The gap depends on your sector (B2C more impacted than B2B), your iOS share of traffic, and your Adblock dependency. The real cost is not the lost signal, it is the ad arbitrage made blind on top of it. The broader agency vs freelance vs in-house debate sits here.

Not the same. TAGGRS is a managed setup that includes server, monitoring, and 30+ pre-configured Conversion API templates. Native GTM Server-Side requires provisioning your own Cloud Run, managing costs, writing templates. TAGGRS wins on time-to-market and costs less to run for SME volumes (< 1 M€). Above that, containerised native sGTM becomes relevant.

Not to our knowledge as of late 2026. APD sanctions documented in the last two years mostly hit the lack of a proper Consent Mode and tracking without legal basis, not the server channel itself. Server-side done well with strict Consent Mode V2 remains more GDPR-compliant than broken client-side.

Belgian SME e-commerce 2026 market range: 15-35% recovery on Purchase events, 10-25% on Lead. The real delta depends on browser mix (Safari iOS weighs heavily) and Adblock usage. For your specific case, we quote after a scoping call. The GA4 and BigQuery measurement layer is what makes these numbers readable.

TAGGRS infra side: 200-400 € HTVA per month depending on event volume. Maintenance side: 1-2 dev days per quarter to keep GA4, Meta CAPI, and iOS changes compliant. If we leave, you keep the Notion doc + Cloud Run access + internal agency relay procedure in 1 week.

Yes. We do this on 30% of our missions. The rule: who steers the tagging plan and the post-deploy QA. If your existing agency stays pilot, we frame scope and timeline. If they execute our plan, we accompany. We never step on the other agency without saying.

Field note

Server-side is the cherry on top. Not the priority. It comes on top, when everything else holds. When it is installed cleanly, you gain in tracking, your ad algorithms run on fresher data, and your KPI steering gets sharper. We rarely start there.

Jérôme · Strategy & data
JérômeStrategy & data · HeySquad

Other sub-services TRACKING & MEASUREMENT

We look at your setup. We tell you what your marketing tools no longer see.

Get my server-side setup quotedBack to the Tracking & measurement service