What is server-side tracking?
Server-side tracking sends conversion and event data, such as purchases, sign-ups, and add-to-carts, from a business's own server directly to ad platforms. Traditional tracking relies on a pixel, a small piece of code that runs in the visitor's browser and reports what they do.
The difference is where the data is sent from. A browser pixel depends on the browser letting it run and keep cookies. A server-to-server connection doesn't, so far fewer events go missing.
How does server-side tracking work?
- Capture the event. A purchase, sign-up, or other action is recorded on the business's own systems.
- Process it. The event is prepared with the details each platform needs, in line with the business's consent settings.
- Send it. The server sends the event to each ad platform through that platform's server-side API, such as a Conversions API.
- Use it. Platforms use the events for measurement, attribution, audiences, and campaign optimization.
What is an example of server-side tracking?
A purchase the pixel missed
A shopper uses a browser that blocks third-party scripts, so the store's pixel never fires when they buy. To the ad platform, the sale didn't happen, and the campaign that drove it looks less effective than it was.
With server-side tracking, the store's server reports the purchase directly to the platform, so the conversion is counted and the campaign is optimized on more complete data.
Server-side tracking vs. browser pixel tracking
| Browser pixel | Server-side tracking | |
|---|---|---|
| Where data is sent from | The visitor's browser | The business's own server |
| Affected by ad blockers | Often | Generally not |
| Affected by browser privacy limits and short-lived cookies | Yes | Largely not |
| Control over what is shared | Limited | Set by the business |
| Setup | Add a tag to the site | Needs a server-side connection, often managed |
It's rarely either-or. Teams usually keep the pixel and add server-side events, then match them so the same conversion isn't counted twice.
Why does server-side tracking matter now?
Browser restrictions, operating system changes, ad blockers, and privacy regulation have made pixel data less complete every year. Missing conversions mean ad platforms optimize on partial information, and reports undercount what marketing delivered.
- More complete measurement. Fewer conversions go missing between the site and the ad platform.
- Better optimization. Platforms bid and target using stronger signals.
- More control. The business decides what data is sent, from its own infrastructure.
- Privacy still applies. Server-side tracking works alongside consent management and legal review, not instead of them.
How does Alli do this?
Alli by PMG's Audience Gateway is managed server-side tracking. It captures first-party events once, such as purchases, sign-ups, and add-to-carts, processes them, and sends them server-to-server to the ad platforms' conversion APIs, in each platform's format. It runs in a dedicated Alli and client server environment or on a subdomain of the client's own infrastructure.
API changes are managed for you, and the same events feed measurement in Alli, so conversion data stays consistent across platforms and reporting.
Explore Alli Audience GatewayServer-side tracking FAQ
Is server-side tracking better than pixel tracking?
It's more complete, because it isn't blocked by most browser restrictions or ad blockers. In practice, the two usually run together, with events matched so they aren't double counted.
Does server-side tracking replace cookies?
It reduces reliance on browser cookies for sending conversion data, because events are sent from the business's own server. It doesn't remove the need for consent management.
Is server-side tracking privacy compliant?
It can be, when it's set up to respect user consent and applicable law. Server-side tracking changes where data is sent from, not whether consent and legal review are needed.
What is the difference between server-side tracking and a Conversions API?
Server-side tracking is the overall approach of sending events from your own server. A Conversions API is a specific ad platform's endpoint for receiving those events.
Last updated ‹ Back to the glossary