What is server-side tracking? How server-to-server conversions work
Server-side tracking is a way of measuring what visitors do on your store by sending events such as purchases and sign-ups from a server you control to ad and analytics platforms, instead of relying only on tags that run in the shopper's browser.
How it works
In classic browser-side tracking, every platform loads its own script on your pages, and each script reports events straight from the visitor's browser. With server-side tracking, the event is recorded once, on your side, and your server forwards it to each destination through that platform's server API. Two common patterns are:
- A tagging server. Google describes server-side tagging as processing measurement data in a server container you run: "clients" receive data from the device and turn it into events, and tags forward those events onward.
- Direct server-to-server APIs. Meta's Conversions API, for example, connects marketing data "from an advertiser's server, website platform, mobile app, or CRM" to Meta, and those events are processed like events from the Meta Pixel.
A worked example
Imagine a hypothetical store that completes an order. The order system confirms payment, then sends one purchase event, with the order value and a unique event ID, to its analytics and ad platforms. Because the event comes from the order record rather than a thank-you page script, it still fires if the shopper closes the tab before the confirmation page finishes loading.
Why it matters for an online store
- Less code in the browser. Google notes that fewer measurement tags on a site means less code to run on the client side, which helps page speed.
- Data control. You decide which fields leave your systems, and Google says visitor data is better protected when collected and distributed from a customer-managed server environment.
- Accurate revenue. Conversions can be tied to confirmed orders, so refunds and failed payments are easier to reconcile.
Common mistakes
- Double counting. Many stores run a browser tag and a server feed together. Meta recommends this "redundant setup" but only deduplicates when the browser eventID matches the server event_id and the event names match, within 48 hours of the first event.
- Treating it as a consent workaround. Moving tracking to a server does not change whether you need permission. Consent choices must still be respected and passed on; see Consent Mode.
- Ignoring running costs. A self-hosted tagging server is infrastructure. Google says its default setup is free in most cases, but a production Cloud Run deployment typically costs $30 to $50 per server per month.
On CIQRA, every plan includes server-side conversions to GA4, Meta, TikTok, Google Ads, Pinterest, Snapchat and Microsoft, and server-side Google Tag Manager is supported too.