Server-side tagging means running your tracking tags on a server you control, instead of in your visitor's browser. Your website sends its tracking data to that server, and the server passes it on to analytics and ad platforms like Google Analytics, Google Ads and Meta.
The best-known version is a Google Tag Manager server container, a second copy of Tag Manager that runs on a server (usually Google Cloud, or a hosting company that specializes in it) rather than on your web pages.
Why Server-Side Tagging Exists
Traditional tracking loads a separate script in the browser for every platform: one for Google Analytics, one for Google Ads, one for Meta and so on. Each one slows the page a little, sets its own cookiesA small piece of data stored in a user’s browser that helps websites remember user activity, preferences, or sessions across visits. and talks directly to its own company. Ad blockers and browser privacy settings block many of them.
Server-side tagging changes the route, so the browser sends one stream of data to your own server, usually on a subdomain of your site, and your server decides what to send where. That can mean fewer scripts on the page, more control over what data each platform gets, and fewer blocked requests.
How Server-Side Tagging Works
A typical setup with Google Tag Manager looks like this:
- A server container is created in Tag Manager and hosted on a server you pay for.
- The website's tags are changed to send data to that server instead of straight to Google or Meta.
- Clients in the server container receive the incoming data (the GA4 client is the most common).
- Tags in the server container send it on to each platform, like a Google Ads conversion tag or a Meta Conversions API tag.
It's powerful and works on any kind of website, but it's a second system to host, pay for and maintain, and it takes real comfort with Tag Manager to set up well.
Server-Side Tagging vs. Server-to-Server Tracking
The two are easy to mix up, and the difference is where the conversion starts:
| Server-side tagging | Server-to-server tracking | |
|---|---|---|
| Where the data starts | The visitor's browser | Your website's own server |
| Extra server needed | Yes, a tagging server | No |
| Still needs browser code | Yes, to send data to the tagging server | No, the website already knows about the order or form entry |
| Common tool | Google Tag Manager server container | A Conversions API sent by your site or plugin |
With server-side tagging, the browser still has to send the data out first, it just sends it to your server instead of to each platform. With server-to-server tracking, your website's server already knows a conversion happened (because it just processed the order or saved the form entry) and sends it to the platform directly.
Server-Side Tagging on WordPress Sites
On WordPress you can do either. A Tag Manager server container works with WordPress like any other site. But because WordPress already runs on a server and already handles the orders, forms and signups, many sites don't need the extra container to get conversions to ad platforms from the server.
How Conversion Bridge Helps
Conversion Bridge sends conversions to ad platforms from your WordPress server directly, alongside the browser tags, with no tagging server to host, for Google Ads, Meta Ads, LinkedIn Ads, Pinterest Ads, Reddit Ads, OpenAI Ads, Snapchat Ads, and Awin. Each conversion is sent with a matching ID so the platform counts it once when both copies arrive.
If you already run a Tag Manager server container for other reasons, Conversion Bridge can also work with Google Tag Manager. See what a Conversions API is for more on the direct approach, Google Ads server-side tracking on WordPress for a walkthrough of one platform, and server-side tracking for every platform it covers.
Frequently Asked Questions
Is server-side tagging the same as server-side tracking? People use the words loosely, but server-side tagging usually means a tagging server like a Tag Manager server container. Server-side tracking can mean that, or a website sending conversions straight from its own server.
Does server-side tagging get around ad blockers? Partly, since requests to your own subdomain are blocked less often than requests to known ad domains, but the browser still has to send the data, so some can still be lost.
Do I need server-side tagging to use a Conversions API? No, a Conversions API can be fed by a tagging server, but your website can also send to it directly, which is how Conversion Bridge does it on WordPress.