This guide covers server-side tracking for ecommerce: why client-side tracking is losing data, how server-side tracking works, choosing your setup method, server-side GTM configuration, connecting ad platforms, Shopify-specific considerations, and measuring the impact.
1. Why Client-Side Tracking Is Losing Data
Here is the problem in simple terms. Every tracking tag on your store (GA4, Google Ads, Meta Pixel) runs in the visitor's browser. And browsers have been getting increasingly aggressive about blocking those tags.
Safari's Intelligent Tracking Prevention (ITP) limits first-party cookies to 7 days for JavaScript-set cookies. So a visitor who clicks your ad on Monday and buys on the following Tuesday might not be attributed to that ad. On Safari, that conversion just vanishes from your data.
Ad blockers make it worse. Roughly 30-40% of desktop users run some form of ad blocking. These tools do not just block ads. They block tracking scripts too. Every blocked script is a conversion your ad platform never sees.
Then there is Firefox's Enhanced Tracking Protection, Brave's built-in blocking, and Chrome's ongoing changes to third-party cookies. The trend is clear: client-side tracking gets less reliable every year. For ecommerce stores spending serious money on ads, this data loss directly affects bidding algorithms and attribution.
2. How Server-Side Tracking Works
Server-side tracking adds a middleman between the browser and the ad platforms. Instead of the browser sending data directly to Google, Meta, and others, it sends data to YOUR server first. Your server then forwards it to each platform.
Why does this help? Because ad blockers work by blocking requests to known tracking domains (like google-analytics.com or connect.facebook.net). When the request goes to your own domain first (like tracking.yourstore.com), most ad blockers do not block it. It looks like a regular first-party request.
The server can also set proper first-party cookies with longer expiration times, getting around ITP's 7-day limit. And because the server controls what data goes where, you can enrich events with data the browser does not have access to (like customer lifetime value from your database).
This is not about circumventing privacy. Users who opt out of tracking should still be excluded. But for users who consent to tracking, server-side makes sure their data actually reaches your analytics and ad platforms instead of getting silently dropped.
3. Choosing Your Setup Method
There are three main approaches to server-side tracking, and they vary in complexity and cost:
Option 1: Server-Side GTM on Google Cloud. This is the most flexible option. You run a Google Tag Manager server container on Google Cloud Platform (or any cloud provider). It costs $30-100/month in hosting for a typical ecommerce store. Setup is more involved, but you get full control over data routing and transformation.
Option 2: Managed platforms. Services like Stape, Addingwell, or Taggstar host and manage the server container for you. Pricing starts around $20/month. They handle the infrastructure, and you just configure the tags. This is the fastest path for most stores.
Option 3: Platform-native server-side. Some platforms have built-in server-side options. Meta's Conversions API (CAPI) and Google's enhanced conversions are examples. These are simpler to set up but only cover their specific platform. For a full solution, you probably still need a server container.
For most ecommerce stores, we suggest starting with a managed platform plus Meta CAPI and Google enhanced conversions. That covers the two biggest ad platforms with minimal infrastructure overhead.
4. Server-Side GTM Configuration
If you go with Server-Side GTM, here is the setup at a high level. The details would fill a book, but this gives you the framework.
Step 1: Create the server container. In GTM, create a new container and choose "Server" as the target platform. Google will give you provisioning options for Cloud Run or App Engine.
Step 2: Set up your custom domain. Map a subdomain like tracking.yourstore.com to your server container. This is what makes the requests look first-party. Without it, you lose most of the benefit.
Step 3: Update your client-side GTM. Change your GA4 tag's transport URL to point to your server container domain instead of Google's servers. The client-side tag still fires in the browser, but now it sends data to your server first.
Step 4: Add server-side tags. In your server container, add tags for each platform you want to send data to: GA4, Google Ads, Meta CAPI, etc. These tags receive the data from the client-side request and forward it to each platform's API.
Step 5: Configure event mapping. Make sure the server-side tags correctly map your ecommerce events. A purchase event coming from the client side needs to be transformed into the right format for each destination platform.
5. Connecting Ad Platforms Server-Side
Google Ads. Server-side GTM can fire Google Ads conversion tags from the server. You will also want to enable enhanced conversions, which sends hashed customer data (email, phone, address) alongside the conversion. This helps Google match conversions to ad clicks even when cookies are missing. The match rate improvement is typically 10-20%.
Meta (Facebook). The Conversions API (CAPI) is Meta's server-side tracking solution. You can fire it from your server container or set it up directly through Shopify. CAPI sends events alongside the pixel, and Meta deduplicates them. For Shopify stores, this is probably the single biggest tracking improvement you can make. We have a full guide on Facebook CAPI setup for Shopify.
GA4. The GA4 server-side tag in GTM forwards measurement protocol hits. One nice benefit: you can enrich GA4 events with server-side data before they reach GA4. Things like customer cohort, lifetime value, or CRM data that the browser does not have access to.
TikTok, Pinterest, others. Most major ad platforms now support server-side event APIs. If you are spending meaningful budget on these platforms, add server-side tags for them too. The setup is similar to Meta CAPI: you send events from your server using the platform's events API.
6. Shopify-Specific Considerations
Shopify adds some wrinkles to server-side tracking. The checkout is hosted by Shopify, and you have limited control over what scripts run there (unless you are on Shopify Plus).
For non-Plus stores, your options are:
- Shopify Web Pixel API: Shopify's official way to capture checkout events. It runs in a sandboxed environment and can send data to your server container. The limitation is that it cannot set cookies or access the DOM.
- Third-party apps: Elevar, Littledata, and Analyzify handle the Shopify-to-server pipeline. They capture checkout events and forward them to your server-side GTM or directly to ad platform APIs. These cost $100-300/month but save significant development time.
- Shopify's native CAPI integration: Shopify has built-in Meta CAPI support through its Facebook channel app. It is basic but functional for Meta specifically.
For Plus stores, you can use checkout extensibility to run custom server-side scripts during checkout. This gives you the most control but requires development resources.
One thing to watch out for: if you use both Shopify's native integrations and a third-party server-side tool, test for duplicate events. Meta's deduplication handles it well if you pass a consistent event_id, but Google Ads is less forgiving with duplicates.
7. Measuring the Impact
After setting up server-side tracking, you need to measure whether it is actually recovering lost data. Here is how:
Before vs after conversion counts. Compare your weekly conversion count in Google Ads and Meta for the two weeks before and after server-side was enabled. Most stores see a 15-25% increase in reported conversions. The conversions were always there. You just were not capturing them before.
Match rate in Meta Events Manager. Check your Meta Events Manager for the "Event Match Quality" score. It should improve after CAPI is active. Scores above 6.0 are considered good. Below 4.0 means your server-side setup needs work.
GA4 session count vs Shopify visits. Compare GA4's session count with Shopify's analytics sessions. If GA4 was previously showing 30% fewer sessions than Shopify, server-side tracking should close that gap to 10-15%.
Ad platform ROAS changes. Watch your ROAS in Google Ads and Meta over the first 2-4 weeks after implementing server-side tracking. ROAS should improve because the platforms now see more conversions attributed to your ads. This does not mean your actual performance improved. It means the reporting is more accurate.
A word of caution: if your ROAS jumps dramatically (like 50%+), double check for duplicate conversion counting. Server-side tracking should recover lost data, not manufacture it. If the numbers look too good, something is probably being counted twice. Review your analytics tracking setup carefully.
Frequently Asked Questions
A basic server-side GTM setup on Google Cloud costs $30-100/month in hosting for most ecommerce stores. Managed solutions like Stape charge $20-100/month depending on request volume. The bigger cost is the initial setup, which typically runs $2,000-5,000 if you hire a specialist.
No. Server-side tracking works alongside client-side tracking, not instead of it. The client-side tag still fires in the browser and sends data to your server container, which then forwards it to GA4, Google Ads, Meta, etc. The server acts as a relay that is harder for ad blockers to intercept.
Partially. Server-side tracking helps with Safari's ITP cookie restrictions by setting first-party cookies from your domain. But it does not bypass Apple's ATT framework. Users who opt out of tracking on iOS still will not be tracked. Server-side helps with the cookie side, not the consent side.
Yes, but with limitations. Non-Plus stores cannot inject scripts into checkout, so you will need to use Shopify's Web Pixel API or a third-party app like Elevar to capture checkout events and forward them server-side. It adds a layer of complexity but it works.
Is Your Tracking Missing Conversions?
COREPPC's free audit checks your Google Ads and Meta tracking setup in 60 seconds. See where data gaps are costing you.
Start Free Audit
