Traditional ad tracking works in the user’s browser: a JavaScript pixel fires and sends event data to an ad platform like Meta or Google. Server-side tracking changes where the event is sent from. Instead of the browser, the event is sent from your server, after the purchase has been confirmed. This simple architectural change has significant implications for tracking accuracy, particularly in the era of ad blockers and iOS privacy restrictions.
How Traditional (Client-Side) Tracking Works
When a customer completes a purchase on your Shopify store, the thank-you page loads in their browser. The Meta Pixel JavaScript fires, reads the order data from the page, and sends a Purchase event to Meta’s servers. This all happens in the customer’s browser.
Problems with browser-based tracking:
- Ad blockers: blockers like uBlock Origin or Privacy Badger intercept requests to Meta and Google domains and prevent the pixel from sending data
- iOS Intelligent Tracking Prevention (ITP): Safari on iOS aggressively limits cookie lifespans and blocks third-party tracking requests
- Slow page loads: if the user navigates away before the pixel fires, the event is lost
- Browser extensions: any extension that modifies page behaviour can interfere with pixel execution
For a typical Shopify store, 15–30% of purchase events may be lost due to these browser-side limitations, depending on the audience’s technology behaviour.
How Server-Side Tracking Works
With server-side tracking, when an order is confirmed in Shopify, a signal is sent from your server (not the browser) to the ad platform. The path:
- Customer completes purchase on Shopify
- Shopify triggers a webhook or your server receives the order data
- Your server sends an API request directly to Meta’s Conversions API (CAPI), Google’s Measurement Protocol, TikTok’s Events API, etc.
- The ad platform records the Purchase event
Because the event is sent from server to server, it is completely invisible to ad blockers, iOS restrictions, or any browser-side interference. The event delivery rate is close to 100% regardless of what browser or device the customer used.
What Data Is Sent in Server-Side Events
Server-side events typically include:
- Event type: Purchase
- Order value and currency
- Customer identifiers for matching (hashed email, hashed phone number)
- Click IDs (fbclid for Meta, gclid for Google, ttclid for TikTok) captured from the URL when the customer first arrived
- Timestamp
The customer identifiers are hashed (SHA256) before sending, so the raw personal data is never transmitted to ad platforms. The hashes allow ad platforms to match the purchase event to a specific user in their system — improving attribution while maintaining privacy compliance.
Server-Side Tracking Does Not Replace Browser Pixels
Running both browser-side pixels and server-side APIs simultaneously (with deduplication) is the recommended approach. The browser pixel captures real-time behavioural data (page views, add-to-cart, checkout initiation) that is harder to send server-side. The server-side API captures the purchase event reliably even when the browser pixel fails.
Meta, Google, and TikTok all support deduplication: you send the same unique event_id from both the browser pixel and the CAPI. The platform deduplicates and counts each event once, combining the reliability of server-side delivery with the rich behavioural data of browser-side tracking.
Who Needs Server-Side Tracking?
Server-side tracking is most valuable for:
- Stores with audiences that use ad blockers heavily (tech-savvy demographics, US users generally)
- Stores where a significant portion of traffic is from iOS Safari
- Stores spending $10k+ per month on Meta or Google where the 15–30% event loss translates to meaningful bidding errors
- Stores trying to use Meta CAPI or Google Enhanced Conversions properly
For very small ad budgets or simple tracking setups, the complexity of server-side tracking may not be justified. For serious ecommerce stores running meaningful ad spend, it is increasingly the baseline expectation, not an advanced option.
Get Your Server-Side Tracking Set Up
Setting up server-side tracking correctly requires understanding both the technical implementation and the deduplication configuration. Done incorrectly, it can double-count conversions or send events with poor match quality that do not help platform attribution.
Book your free Shopify tracking audit here and we will assess whether server-side tracking is the right next step for your store and what the implementation would involve.