How server-side tagging works
In a classic client-side setup, the browser loads vendor tags directly and each fires its own request to Google, Meta, and others. Server-side tagging inserts a container that runs on your own server, usually a cloud-hosted Google Tag Manager server container. The browser sends one request to your endpoint, and your server decides what to forward to each platform. Because the outbound requests come from a first-party server on your own domain rather than from third-party scripts in the browser, they are far less likely to be blocked or truncated.
Why it recovers conversion signal
Client-side tracking loses a meaningful share of events. Ad-blockers strip third-party scripts, privacy browsers cap cookie lifetimes to a few days, and network conditions drop requests. Every one of those losses is a conversion the platform never learns about, which starves Smart Bidding of the data it needs. Server-side tagging routes the event through your own infrastructure first, so a blocked browser script no longer means a lost conversion. Paired with Enhanced Conversions and the Conversions API, it is the difference between the platform seeing most of your conversions and seeing all of them.
Server-side vs client-side
Server-side is not simply better at everything, it is a different set of trade-offs. It costs more to run because you are hosting a server, and it takes engineering to deploy and maintain. What it buys is durability, control over exactly what data leaves your domain, and cleaner first-party cookies with longer lifetimes. For a low-volume site the recovered signal may not justify the overhead, but for any account where bidding accuracy drives real budget, the payback in reclaimed conversions is usually quick.
How iClick deploys server-side tagging
iClick deploys server-side tagging as the durable base layer under Enhanced Conversions and the Conversions API, so the conversion signal survives blockers and privacy limits before any bidding optimisation is trusted. The method is to stand up a server-side GTM container on the client's own subdomain, route events through it, and validate that each platform receives clean, deduplicated conversions. The rule is that bidding is only as good as the signal it learns from, so the signal gets fixed first.
