Server-side tracking explained: why client-side alone is no longer enough

What is client-side tracking?

Traditional pixel tracking works client-side: a JavaScript snippet loads in the visitor browser. When someone views a product, adds to cart, or purchases, the pixel sends an event to the ad platform. This worked well until a few years ago. But the world has changed.

Why client-side tracking is failing

Three main causes:

• Ad blockers — About 30-40% of desktop users have an ad blocker installed. Tools like uBlock Origin block not just ads but also tracking pixels from Meta, Google and TikTok.
• iOS 14.5 and later — Apple introduced App Tracking Transparency. Most users decline. This has largely broken the Meta Pixel on iOS devices.
• Third-party cookie deprecation — Chrome is phasing out third-party cookies. Safari and Firefox have done this for years. Without cookies, the pixel struggles to identify visitors and match events to ad clicks.

What is server-side tracking?

Server-side tracking, also known as Conversions API (CAPI), works differently. Instead of the browser sending the event, your server sends it directly to the ad platform. The flow: visitor purchases on your Shopify store, Shopify registers the order on your server, your server sends the purchase event to Meta CAPI, Google Enhanced Conversions, and TikTok Events API — regardless of ad blockers, iOS restrictions, or cookie settings.

Dual-dispatch: the best of both worlds

The most effective approach is dual-dispatch: sending events both client-side (via the pixel) and server-side (via CAPI). Ad platforms have built-in deduplication on event_id — if both sources send the same event with the same ID, it only counts once. Layer Insights implements dual-dispatch automatically. lf.js runs in the browser for speed and browser signals. The CAPI gateway runs server-side for reliability and advanced matching.

What is the difference in results?

In practice, Shopify stores switching from client-only to dual-dispatch tracking see 15-40% more measured conversions, an average EMQ improvement of +2.8 points, better algorithm optimization, and lower CPMs from more efficient targeting.

Is server-side tracking GDPR-compliant?

Yes, if implemented correctly. Server-side tracking via CAPI still requires user consent for processing personal data. Layer Insights implements consent-aware dispatch: if a user does not consent, we send a stripped payload without PII. Google Consent Mode v2 is automatically implemented in lf.js.