← Back to blog
Tracking

The Missing Manual: Connecting Shopify to TAGGRS Server-Side Tracking

Step-by-step guide to implementing server-side tracking for Shopify via TAGGRS — and why it matters for your GA4 data.

Browser-side tracking is increasingly unreliable. Ad blockers, iOS privacy changes, and aggressive cookie policies mean you’re likely missing 20–40% of your conversion events if you’re still relying purely on client-side GTM. TAGGRS is one of the cleaner server-side tagging solutions for Shopify, and the setup is less painful than it looks.

Why Server-Side for Shopify?

Shopify’s checkout is notoriously difficult to track. Since Shopify Plus allowed custom checkout scripts, things got marginally easier — but for standard Shopify, the purchase event often fires in a sandboxed iframe that client-side GTM can’t reliably touch.

Server-side tagging moves the measurement to a server you control. TAGGRS acts as a proxy: Shopify sends events to TAGGRS, TAGGRS validates and enriches them, then forwards to GA4 and Google Ads with first-party context. The result is more reliable purchase tracking, better match rates for Enhanced Conversions, and data that can’t be blocked by browser extensions.

What You’ll Need

The Setup Flow

1. Configure Your GTM Server Container

TAGGRS provisions a server-side GTM container for you. You’ll get a tagging server URL (something like https://yoursite.taggrs.io). This replaces https://www.googletagmanager.com/gtag as the endpoint your web container sends data to.

In your web GTM container, update your GA4 Configuration tag’s Transport URL to point to your TAGGRS endpoint.

2. Install the Shopify Pixel

TAGGRS provides a Shopify Customer Events pixel. Install it via:

Shopify Admin → Settings → Customer events → Add custom pixel

Paste the TAGGRS pixel code. This captures checkout and purchase events that standard GTM can’t reach.

3. Set Up the Server-Side GA4 Client

In your server GTM container, add the GA4 Client tag. Configure it to receive events from your web container and the Shopify pixel.

The server container then forwards to GA4 using the Measurement Protocol — so the hit comes from your server, not the user’s browser.

4. Enhanced Conversions

With server-side access to checkout data (email, phone, address), you can pass hashed user data to Google Ads for Enhanced Conversions. TAGGRS makes this straightforward — there’s a built-in template for it.

This typically lifts reported conversions by 15–25% for most Shopify stores because it recovers conversions that were previously unattributed.

Verifying It Works

Use GA4 DebugView alongside TAGGRS’s own event log to confirm events are flowing through. Check that purchase events have the correct transaction_id, value, and currency parameters — these are the ones that matter for bidding.

Compare 7-day purchase event counts in GA4 against your Shopify orders dashboard. If they’re within 5% you’re in good shape. More than 10% discrepancy warrants investigation.

If you’re setting this up for the first time and want a second pair of eyes on the configuration, book an hour — server-side setup errors can be subtle and expensive to leave uncorrected.

Found this useful? Book a free 15-minute call to talk through your setup.

🍓 Book Free Call
🍓 Free 15-Minute Call