What is server-side tagging¶
Server-side tagging is the Google Tag Manager mode in which tags run on a server instead of in the visitor's browser. The site keeps collecting events, but the processing — firing Google Analytics, Google Ads, third-party pixels, conversions — happens on a server you control.
The problem with tags in the browser¶
In the traditional (client-side) model, every tag is a script the browser has to download and run. Three things happen:
- Ad blockers prevent scripts associated with advertising and tracking from loading. The event simply never happens.
- Browser restrictions (ITP, intelligent tracking prevention) limit third-party cookies, which lowers the attribution rate.
- Every script adds weight to the page, which affects load speed and, as a consequence, experience and SEO.
The result is an incomplete data funnel: what the server records does not match what the browser managed to send.
What changes in the server-side model¶
| Situation | Tags in the browser (client-side) | Tags on the server (server-side) |
|---|---|---|
| Ad blocker active | Script blocked; event lost | Event reaches the server normally |
| Third-party cookies | Restricted by the browser | Processed as first-party cookies |
| Page weight | One script per tag | Fewer scripts loaded on the client |
| Who runs the tag | The visitor's browser | The container server |
| Data control | Spread across the client | Concentrated in one point you govern |
Server-side does not neutralize ad blockers
The technique does not "turn off" the visitor's ad blocker. It removes the dependency on third-party scripts in the browser, which is the most common reason an event gets dropped. Part of the traffic may still not arrive by user choice — and respecting that choice remains mandatory, including under LGPD and GDPR.
How GTM fits in¶
Google Tag Manager already supports server-type containers. The practical difference is that the container gains its own URL, served by a tag server, instead of only a container ID loaded from googletagmanager.com.
That is where AdPulse comes in: instead of you provisioning and maintaining that server infrastructure, you paste your container configuration in the dashboard and we provision the container for you.
What AdPulse delivers¶
- Managed provisioning — you paste the configuration string and the server is created automatically.
- SA East (Brazil) location — processing happens in the region where most of the Brazilian audience is.
- Global CDN (Cloudflare) — file delivery goes through the Cloudflare edge, closer to the visitor. The CDN is standard and cannot be disabled.
- Per-request metering — the requests the container receives are counted and billed according to your plan.
- WordPress integration — a plugin forwards requests from your own domain to the tag server. See How to install and configure the WordPress plugin.
Shared usage and custom domain
By default your container is served by the platform's shared hostname, which sits behind the CDN. You can connect a custom domain to the container from the dashboard; when you do, traffic goes through your own DNS provider's network.