What is server-side tracking, and does a Shopify store need it?

By the HonestTag team · Published October 24, 2026

Browser tracking vs server tracking

• Browser tracking: a pixel in the shopper's browser sends the event straight to the ad platform. If the browser blocks or loses it, the platform never hears about the sale.
• Server tracking: the event is sent from a server. Google describes its version as "processing data on a server you control, rather than in the user's browser" (Google Tag Manager).

The two work together: the browser notes which ad the shopper came from, because only the landing page sees the ad click, and the server sends the purchase.

What breaks browser tracking

• Ad blockers. Shopify says "Ad blockers can block the web pixel entirely, which prevents its events from being sent to that destination" (Shopify Help Center).
• Shorter cookies. Shopify says intelligent tracking prevention "shortens or limits cookies, which reduces attribution accuracy even though the pixel still runs and sends events" (same page). Safari and iPhone tracking has the details.
• Checkout scripts are gone. Shopify says checkout.liquid and Additional Scripts "were sunset for the Thank you and Order status pages on August 28, 2025" (shopify.dev).

For the first two, the same Shopify page adds: "In both cases, your Shopify reports and order records aren't affected, because Shopify records order and analytics data when the order is processed" (Shopify Help Center). With a blocker, the browser event never reaches the platform. With tracking prevention, the pixel still sends, and the platform's attribution gets less accurate.

What server-side fixes, and what it does not

It helps with:

• Purchases a blocker or a failed page load kept from the platform.
• Purchases on a checkout you can no longer add scripts to.
• Sending details a platform matches on, such as a hashed email, from the order itself (how hashed customer data matches).

It does not:

• Override consent. Shopify says server pixels "are still subject to your store's customer privacy and consent settings" (Shopify Help Center).
• Bring back a lost click. If Safari cleared the cookie or the link lost its click id, the server has nothing to tie the order to that ad, apart from a hashed email the platform may recognize.
• Decide the credit. Each platform still credits its own ads, so their totals can still add up to more than your orders.

Three ways to do it on Shopify

• The platform's own Shopify app. For example, Shopify says that at Enhanced data sharing its Facebook & Instagram app "uses Facebook's Conversions API as well as the Meta pixel," and Maximum uses both as well (Shopify Help Center). One platform at a time.
• A server container you host. Full control over every tag, and the upkeep that comes with it: hosting, tags and fixes are yours. Server-side GTM vs a Shopify app says when that fits.
• An app that sends purchases from the order. No container to run. You depend on the app to keep each platform's connection working.

Whichever you pick, keep one rule: one purchase source per platform, unless both sources send the keys that platform uses to deduplicate, inside any window it states. Duplicate purchase events explains why.

Before you change anything

1. List every tool that sends purchases to each platform today.
2. Write down each platform's purchase count for the last 30 days beside your Shopify order count (why the two rarely match). For GA4, compare its purchase revenue with Shopify's net sales, not total sales (GA4 revenue vs Shopify).
3. Run the new setup beside the old one before you switch anything off. Running two trackers side by side shows how.

What HonestTag does

• Purchases come from Shopify's order webhook, not from a script on the thank-you page, and each one is checked against your real order. Draft orders and register sales stay out of ad platforms by default (draft and manual orders). On a standard Shopify storefront, the pixel that records the ad click is a Shopify app pixel; Shopify custom pixel vs app pixel explains the difference.
• On a paid plan, verified web purchases go from HonestTag's servers to the destinations you connect, within your plan's simultaneous-delivery limit: Google Ads, Meta, Microsoft Advertising, TikTok, Pinterest, Reddit, ChatGPT Ads and Google Analytics 4; Klaviyo when the order carries a HonestTag visitor ID or a Klaviyo click ID. Each delivery leaves an order proof you can open.
• Consent rules apply before anything is sent, and an order they block is dropped, as the server-side delivery docs state.
• By default most platforms get HonestTag's own events, which do not add to their standard purchase count, so they sit beside your current setup instead of doubling it.
• The limits are the same as above. HonestTag's visitor cookie is set by a script, so it follows Safari's limits on script-set cookies: deleted after 7 days with no interaction, and capped at 24 hours when it is created on a landing page whose link ITP detects as decorated with a click ID. An optional tracking domain does not get around Safari or consent.

Frequently asked questions