Server-Side Tracking for Shopify with Stape: A Plain-English Guide

Browser tracking vs server-side tracking

Browser tracking is what most stores start with. A pixel runs in the visitor's browser and sends events straight to Meta, Google or TikTok. Anything that blocks scripts in the browser blocks your data too.

Server-side tracking adds a step in the middle:

Your store → your tracking server (on your own domain) → Meta, Google, GA4, TikTok…

Because the tracking server lives on a subdomain of your site, for example data.yourstore.com, it's treated as part of your website rather than a third-party tracker. And because events can be sent from the server, they don't depend entirely on what the browser allows.

What it fixes (and what it doesn't)

It helps with:

• Missing sales. Purchases reach your ad platforms even when the browser pixel is blocked.
• Duplicates. One controlled feed, with a shared event ID on each event, so each sale counts once.
• Customer matching. You decide which customer details (securely hashed) go with each event, which usually raises Meta's Event Match Quality.
• Control. You choose exactly what each platform receives, including extras like profit per order.

It doesn't:

• Track people who decline tracking in your cookie banner. Consent rules still apply.
• Fix a broken offer or weak creative. It makes sure your ads learn from the right results.

The pieces involved

Setup, step by step (overview)

This is the order we follow. Each step has details that matter, so treat it as a map, not a full tutorial.

1. Audit what's already there. List every pixel, app and Shopify setting that sends data today. Most duplicate problems start here.
2. Create a server container in GTM, then create a matching container in Stape using its config.
3. Add your custom subdomain in Stape and the DNS records it gives you at your domain provider. Wait for it to verify and get its security certificate.
4. Turn on Stape's custom loader, so GTM itself loads from your subdomain instead of Google's.
5. Install Stape's Shopify app for the ecommerce data layer and order data. If GTM is already installed another way, make sure only one method loads it.
6. Build the web container: a Google tag that sends to your server URL, plus browser events for each step of the funnel, each with an event ID.
7. Build the server container: GA4, Meta Conversions API, Google Ads and any other platforms, using the same event IDs so browser and server copies are matched up.
8. Set up consent mode, so tags respect your cookie banner.
9. Turn off the overlap. Disable data sharing in Shopify's Facebook & Instagram app (or any tracking app) for events your new setup now sends, and remove leftover pixels.
10. Test everything with GTM preview and Meta's Test Events, then place real test orders.
11. Publish, then monitor. Compare Shopify orders with each platform daily for the first week or two.

We run this exact setup on our own website, so it's not theory.

What it costs

• Stape has a free plan with a small monthly request limit (fine for testing) and paid plans that scale with traffic. Check Stape's pricing for current numbers.
• Google Tag Manager is free.
• The real cost is setup time. The pieces are well documented. Getting them to work together without duplicates or gaps is where most DIY setups go wrong.

5 mistakes that cause duplicates and gaps

1. Leaving Shopify's Facebook & Instagram app sharing the same events. Meta then gets your purchase from the app and from your server, often without a shared ID.
2. Missing or mismatched event IDs. Without the same ID on the browser and server copy, Meta can't tell they're the same sale.
3. Loading GTM twice, for example through a theme code snippet and an app.
4. Testing on your live setup without a test code. Meta counts test purchases as real unless they're sent with the code from an open Test Events window.
5. Forgetting checkout. Since Shopify's checkout upgrade, GTM can't run on checkout pages. Checkout and purchase events need to come through Shopify's customer events or order data from the Stape app.

see what your store sends today.

Our free store scan checks how your Meta, Google, TikTok and Pinterest tracking behaves from the outside, including whether a server-side setup is in place. It takes about a minute.

Scan my store free →

DIY or done for you?

Do it yourself if you're comfortable in GTM, have time to test properly, and spend modestly on ads.

Get help if you spend $5,000+ a month on ads, run several ad platforms, or your numbers already disagree. At that level, a few weeks of bad data usually costs more than the setup.

FAQ

Is server-side tracking worth it for a small Shopify store? If you spend a few hundred dollars a month on ads, Shopify's built-in connections are usually fine for now. It pays off as ad spend and the number of platforms grow.

Do I still need the Meta pixel? Yes. The best setup sends each event from both the browser and the server with a shared ID, and Meta keeps one copy. If the browser copy is blocked, the server copy still arrives.

Is Stape the only option? No. You can host a GTM server container on Google Cloud or other providers, and some all-in-one tracking apps do server-side tracking their own way. Stape is popular because it's built for exactly this and you don't have to manage servers.

Is it privacy-compliant? It can be, and it gives you more control over what's shared. It still has to respect your visitors' consent choices and your privacy policy.

For how this compares to Shopify's built-in apps, read Shopify's built-in tracking vs GTM server-side tracking.

Feed your pixel. Grow your profit.

Scan my store free →