Waterloo Track

Managed server-side tracking for Shopify & ecommerce brands

Waterloo Track is Waterloo Digital’s done-for-you server-side tracking service for Shopify and ecommerce brands that run paid media. We build server-side Google Tag Manager, hosted on Stape, on a tagging subdomain of your own site. Then we send purchase events to GA4, Google Ads and Meta’s Conversions API, and keep that pipeline running every month.

Talk to us

What is Waterloo Track?

The short version.

Track moves the processing of your tracking data to a server you control, then sends that data on to your ad platforms from there. It’s a monthly service, not a one-time install, because it’s a live pipeline that has to keep running.

A browser pixel is third-party JavaScript running in someone else’s browser, and that browser increasingly blocks or limits it. So your ad platforms are bidding on an incomplete record of your business.

What it isn’t: a data-sharing toggle switched on in Shopify settings and never checked again. Track puts the first-party collection point under your control, with one tag container that routes to every destination.

Who is Waterloo Track for?

Ecommerce brands, Shopify first, that run paid media and need attribution they can trust. It also fits nonprofits and B2B companies (though this page is written for stores).

Subscription brands get one extra reason to look. An automatic renewal has no browser session, so a browser pixel can’t report it, and only a webhook-fed server path can. That path gives you conversion volume and customer-level matching, not click attribution, because a webhook carries no cookie data.

What do you get with Waterloo Track?

A tracking plan, a build, and a pipeline someone watches. Specifically:

  • A server-side Google Tag Manager container on Stape, on a tagging subdomain of your own domain.
  • Purchase events sent to Meta through the Conversions API, with click and browser IDs where they were captured.
  • GA4 and Google Ads (with Enhanced Conversions), routed from the same server container.
  • Deduplication, so the same purchase is counted once across the browser and server paths, using a shared event_id.
  • Stape’s Cookie Keeper feature, enabled on the container.
  • For Klaviyo users, Klaviyo profiles enriched with first- and last-touch attribution on purchase events.
  • For subscription stores, renewals reported through Shopify Flow, a webhook and the server container. A webhook carries no cookie data, so renewals give you conversion volume and customer-level matching (hashed email or phone), not click attribution.
  • Control over which events and fields go to each platform, with fields stripped on your own server before anything leaves.
  • Ongoing monitoring, maintenance and support.

The pitch is recovered data, not recovered purchases: browse, cart and retargetable-visitor events, not only the order count. You’re not missing a report. You’re missing the people.

What does the $2,500–$5,000 setup cover?

The setup pays for the build and for proof that it works before it goes live. Setup includes:

  • A tracking plan (an event contract) listing your goals, events, destinations, required fields and how each will be proved, approved by your marketing owner before anything is built.
  • A web Google Tag Manager container and a server container on Stape.
  • Event_id deduplication, so a purchase is counted once across the browser and server paths.
  • The loader snippet deployed on your website.
  • Testing across four hops (dataLayer, web container, server container, destination), each with its own evidence, including the destination’s own proof such as Meta Test Events or GA4 DebugView.
  • A Stape preview check before anything is published to the live server container.

Where it applies, the build also wires Klaviyo profile enrichment and Shopify renewal reporting (see the list above). After setup, the $198 a month covers monitoring, maintenance and support.

How does a Waterloo Track setup work?

Audit, plan, build, prove.

We audit what you have, agree the tracking plan, build, then run parallel tracking to validate and cut over once the data is clean. We never publish a change to the server container without checking it in Stape’s preview mode first, and we monitor after launch.

We also measure click-ID coverage, the share of paid orders that arrived carrying a click ID. It’s our own diagnostic (not a published Meta or Stape metric).

How much does Waterloo Track cost?

$198/mo plus a one-time setup, typically $2,500–$5,000 depending on complexity.

The setup is a separate cost from the monthly fee, and it varies with how complex your store and stack are. The monthly fee covers monitoring, maintenance and support.

How does Waterloo Track compare on price?

Track costs more up front than a self-serve app. On the pages we read on October 28, 2026, Littledata’s Scale plan starts at $159 per month paying annually ($199 paying monthly), with 1,500 orders included. Elevar’s Core plan is $225/mo for up to 2k orders, and its Expert installation is a $1,000 one-time fee.

The higher setup fee buys the work around the tool: a tracking plan approved before the build and evidence at every hop before launch. The $198 a month then pays for monitoring, maintenance and support. If your team can do that work itself, you don’t need to pay us for it. Compare the full field in Stape alternatives, compared.

Who uses Waterloo Track?

Waterloo Track clients include Apolis, Leadership Now Project, Duarte, Hope International and System Catalyst.

  • Duarte. We implemented Waterloo Track within Duarte AI for privacy-first analytics and attribution.
  • Hope International (a nonprofit). Track clarifies attribution across web traffic, donor acquisition and campaign engagement.
  • System Catalyst. First-party analytics for reliable attribution across web, email and campaign channels.

What won’t Waterloo Track do?

Said up front.

Cross-device attribution works only for people who are logged in, with an email provided, on each device. And no setup makes the record complete. Track reduces what goes missing (it doesn’t bring the gap to zero).

When don’t you need Waterloo Track?

If you only advertise on Google and want cheaper ad-blocker resistance, Google Tag Gateway may be enough. It changes the hostname the tag is served from, and it covers GA4 and Google Ads only.

If someone on your team will own a GTM container after launch, a self-serve host such as Stape may be all you need. And if you’d rather not run GTM at all, Littledata says its Shopify app runs server-side tracking “with no GTM and no code.”

Frequently asked questions

Is Waterloo Track built on Stape?

Yes. Waterloo Track is built on server-side Google Tag Manager, hosted on Stape, on a tagging subdomain of your own site. Stape provides the hosting. We build the container, connect your destinations, enable features such as Stape's Cookie Keeper, and maintain the setup every month.

What does the Waterloo Track setup fee cover?

Setup includes a tracking plan approved before anything is built, web and server Google Tag Manager containers, event_id deduplication, the loader snippet deployed on your site, testing across four hops from the dataLayer to each destination, and a Stape preview check before anything is published.

How much does Waterloo Track cost?

Waterloo Track is $198/mo plus a one-time setup, typically $2,500–$5,000 depending on complexity. The setup is priced separately from the monthly fee, and the monthly fee covers monitoring, maintenance and support.

What happens during a Waterloo Track setup?

We audit what you have, agree a tracking plan, build the server-side infrastructure, and run it in parallel with your existing tags to validate the data. We cut over once the data is clean, and we monitor after launch. Nothing is published until it has passed Stape's preview mode.

Doesn't Shopify's Meta integration already send server-side events?

Shopify's Enhanced and Maximum data-sharing settings turn on Meta's Conversions API alongside the pixel. That is a setting, and it says nothing about what flows through it. Shopify's documented setup has no step for capturing click IDs on the first hit, persisting them across domains, or preserving them through redirects.

Can Waterloo Track report Shopify subscription renewals?

Yes, through Shopify Flow, a webhook and the server container. An automatic renewal has no browser session, so a pixel can't report it. A webhook carries no cookie data either, so renewals give you conversion volume and customer-level matching, not click attribution.

Related guides

If you want someone to tell you plainly what’s broken in your tracking and what it would take to fix it, book a short call with us.

Talk to us