Shopify Server-Side Tracking with TAGGRS: 2026 Guide

Updated for Shopify Customer Events and checkout extensibility. This guide explains how to connect Shopify to TAGGRS server-side tracking without relying on legacy checkout scripts.

The confusing part is not creating the Google Tag Manager server container. It is getting reliable ecommerce events from Shopify’s storefront and sandboxed checkout into that container without duplicating purchases.

Shopify now manages marketing and analytics pixels through Settings → Customer events. Since 28 August 2025, scripts can no longer be added directly to the Thank you and Order status pages. A current setup therefore needs a supported app pixel or custom pixel rather than old code in checkout.liquid or Additional scripts.

What you need before starting

• A Shopify store with permission to install apps and manage Customer events
• A Google Tag Manager web container
• A Google Tag Manager server container hosted through TAGGRS
• A GA4 property and the relevant advertising-platform accounts
• A consent-management setup suitable for the countries where you operate

Server-side tagging can improve control and data quality, but it does not remove your consent or privacy obligations. Only send data that you have a lawful reason to collect and that each destination permits.

Step 1: Install and configure the TAGGRS Shopify app

1. Install the TAGGRS Data Layer app from the Shopify App Store.
2. Open the TAGGRS app inside Shopify.
3. Enter your web GTM container ID. This is the ID beginning GTM-, not the server-container URL.
4. Add your TAGGRS custom tracking subdomain if you have configured one.
5. Select the ecommerce events you need, such as product views, add to cart, begin checkout and purchase.
6. Save the app settings.

A custom tracking subdomain is recommended because it places the tagging endpoint on your own domain. Check its DNS status inside TAGGRS before troubleshooting anything in Shopify.

Step 2: Activate data collection in Customer events

In Shopify, go to Settings → Customer events. Follow the current instructions displayed by the TAGGRS app. Depending on the app version, you may see an app-pixel toggle, a generated custom-pixel script, or both.

Where TAGGRS provides custom-pixel code:

1. Copy the script generated by the TAGGRS app.
2. Select Add custom pixel in Shopify Customer events.
3. Give it a clear name such as TAGGRS Server-Side.
4. Paste the code exactly as provided.
5. Review the customer-privacy settings.
6. Select Save, then Connect.

Saving a custom pixel is not the same as connecting it. A pixel left in the disconnected section will not collect customer events.

Step 3: Configure the web and server containers

The Shopify app supplies ecommerce events to your GTM web container. The web container then sends the relevant requests to the TAGGRS-hosted server endpoint, where server-side clients and tags process them.

• Use the TAGGRS templates and container instructions for GA4, Google Ads and other destinations.
• Make sure the transport or server-container URL uses the correct custom subdomain.
• Map Shopify event names and parameters consistently.
• Send a stable transaction ID with purchases so platforms can deduplicate repeat events.
• Avoid running an old theme script, another ecommerce data-layer app and the new Customer Events pixel simultaneously unless you have intentionally designed the deduplication.

Step 4: Test the full purchase journey

Do not stop when the home page produces a page view. A usable ecommerce implementation needs to work from landing page to confirmed order.

1. Open GTM Preview for the storefront.
2. View a product, add it to the basket and begin checkout.
3. Use TAGGRS server-side preview to confirm requests reach the server container.
4. Complete a test order using an appropriate test-payment method.
5. Confirm that one purchase event arrives with the correct transaction ID, value, currency and products.
6. Check GA4 DebugView or Realtime, then verify the destination-platform diagnostics after processing.

Shopify’s custom pixels run in a sandbox. Because of that isolation, normal web-container preview can be limited during checkout. Server-container preview and destination diagnostics become particularly important.

Common Shopify and TAGGRS problems

Product events work but purchases do not

Check that the Customer Events pixel is connected, that purchase is enabled in the TAGGRS app and that you are testing an actual completed order rather than abandoning checkout.

Purchases appear twice

Look for legacy scripts in the theme, checkout settings, Google & YouTube app, another data-layer app or a second custom pixel. Keep a record of every route by which each destination can receive a purchase.

The server preview is empty

Verify the web-container ID, server endpoint, TAGGRS subdomain and DNS status. Then check whether consent settings or browser controls are correctly preventing the request in your test session.

Revenue does not match Shopify

Compare gross versus net revenue, taxes, shipping, discounts, refunds and currency handling. Tracking platforms and Shopify reports may use different definitions, time zones and attribution windows.

When to get implementation help

The app installation is only one part of the job. The valuable work is validating event quality, consent behaviour, deduplication and platform reporting. I provide GA4 and tracking implementation for Shopify businesses using GTM and server-side tagging.

Official documentation

• Shopify: Pixels and customer events
• Shopify: Manage custom pixels
• TAGGRS: Shopify Data Layer app

Ben

Ben Luong is a technical marketing consultant who operates where AI falls short. In a world flooded with cheap, mediocre code and automated strategies, he provides the expert integration, verification, and strategic accountability required to make modern marketing stacks profitable. He specialises in architecting Google Ads, SEO, and GA4 into a single, high-performance system that is accountable to the bottom line.