Server-side tracking

What is server-side tracking?

Server-side tracking means conversion and analytics events are sent to platforms like Meta and Google from a server you control, instead of directly from the user’s browser. Rather than a browser pixel reporting a purchase, your server forwards the event server-to-server. The most common implementations are Meta’s Conversions API (CAPI) and Google’s server-side tagging via server-side Google Tag Manager.

Why does server-side tracking matter?

Classic browser pixels are increasingly blocked by ad blockers, Safari’s Intelligent Tracking Prevention (ITP), and stricter cookie rules. That means lost conversions, weaker attribution, and less accurate ad optimization. Because server-side tracking sends data from a first-party server, it is affected less by these limits, and data quality is usually higher and more complete.

Common use cases

• Setting up Meta CAPI so purchases and add-to-cart events are reported even when the browser pixel is blocked.
• Server-side Google Tag Manager that collects and forwards events to GA4 and Google Ads.
• Deduplication, where both browser and server events are sent with the same event ID.
• More robust retargeting and stronger signals for ad algorithms.

Shopify perspective

In Shopify you can send server-side events through the native sales channels — for example, the Facebook & Instagram channel automatically sends conversions through Meta CAPI. With Checkout Extensibility, custom scripts at checkout are restricted, so you rely more on server-side integrations and apps than on manually inserted pixel code. Remember that server-side tracking does not remove the GDPR requirement: you still need valid consent before personal data is processed and forwarded.