Server-side GTM vs a Shopify app: which fits your store?
By the HonestTag team ยท Published October 26, 2026
Server-side tracking is worth having. Babysitting a server is optional.
Server-side Google Tag Manager (GTM) is a tag container that runs on a server you set up, instead of in the shopper's browser. Google says it "runs on a server that you control" (Google Tag Manager), and you get full control over how the data is shaped and "where it is routed from the server." The price of that control is a server to provision and keep updated, which Google says costs money once you upgrade its Cloud Run environment. A Shopify app that sends purchases from your orders does a narrower job with nothing to host. A container fits a team that needs custom transformations or many destinations. An app fits a store that wants purchases sent and checked without running a server.
What server-side GTM is
- Where it runs. Google says server-side tagging allows you to move measurement tag instrumentation "from your website or app to a server-side processing container on Google Cloud Platform (GCP), or any other platform of your choosing" (Google Tag Manager).
- How it works. Google calls its clients "adapters between the software running on a user's device and your server container," and server containers "come with 2 clients included: Google Analytics and Measurement Protocol" (Google Tag Manager). Google says tags, triggers and variables in a server container "work exactly like they do in other kinds of containers."
- What you get. "You have full control over how that data is shaped, and where it is routed from the server" (same page).
Stop guessing which ads bring new customers, and give Meta and Google a new-customer signal you can bid on. HonestTag sends verified purchases to Meta, Google and 7 more, each buyer marked new or returning. Start free beside your current tracking.
What Google says it takes to run
- Accounts. For the Cloud Run setup, Google lists a GCP account and "a GCP billing account" (Cloud Run setup guide).
- Servers. The default automatic deployment "is recommended for testing limited traffic volumes only." For live traffic, Google recommends "a minimum of 3 instances per container for redundancy" (overview); its Cloud Run guide recommends "a minimum of 2 instances to reduce the risk of data loss in case of a server outage."
- Cost. "The default deployment of a GCP project with a single server is free in most cases." Google adds: "Once you upgrade your Cloud Run environment, you can expect to spend $30-$50 per server per month. Large amounts of network traffic may increase this cost" (overview). Its Cloud Run guide says: "To avoid unexpected costs, set up a billing alert" (Cloud Run setup guide).
- Same domain as your store. Google says the default endpoint "runs in a third-party context," and: "To unlock the benefits of a first-party context, such as more durable cookies, your tagging server and your website have to run on the same domain" (custom domain guide).
- Upkeep. "Keep your tagging server version updated after provisioning the server" (Cloud Run setup guide). If you provision the servers yourself, Google's manual guide says to restart them "periodically" for the latest code, or risk "incompatible functionality for new SST features" (manual setup guide).
Third-party services offer help with the setup. For example, Stape's Shopify app says it "makes it easy for stores to set up Google Tag Manager with server-side tracking" and can "Send purchase and refund webhooks to the server-side GTM container" (Shopify App Store).
What is different on Shopify
- Scripts are gone from the Thank you and Order status pages. Shopify says "checkout.liquid and additional scripts were sunset for the Thank you and Order status pages on August 28, 2025" (shopify.dev).
- Web GTM runs in a pixel sandbox. You can run Google Tag Manager as a custom pixel, but "pixels that Google Tag Manager loads still run within the Shopify sandbox, so the same tracking capabilities and limitations apply" (Shopify Help Center). Shopify custom pixel vs app pixel lists those limits.
- A custom pixel is yours to maintain. Shopify says "Compliance with applicable laws, consents, code security, troubleshooting, and updates are your responsibility," and "Adding and using custom pixels is unsupported by Shopify. If you need help adding or using a custom pixel, then you can hire a Shopify Partner" (Shopify Help Center).
When a container you host is the right choice
Pick server-side GTM when:
- You need custom transformations. Google's transformations "include, exclude or modify event parameters output from your client before they are exposed to tags" (Google Tag Manager).
- You send to many destinations, or from more than a Shopify store. Google says that because the server container does not run on the device, "the same container can handle analytics instrumentation for all three device platforms," and you control "where it is routed from the server" (Google Tag Manager).
- You have someone to run it. Google calls its own server-side course "suitable for tech-savvy marketers and developers" (Google Tag Manager).
Get server-side tracking with no server to babysit. HonestTag runs its own tracking and its own sending, so there is no server or container for you to host or keep alive.
When an app fits
- You want purchases sent server-side without a server, a billing alert or a version to keep current.
- You sell on Shopify only, and your destinations are the main ad platforms.
- You would rather depend on the app to keep each platform connection working than build and fix the tags yourself.
Before you choose
- Name who maintains it. A container needs an owner for its servers and its tags. An app needs an owner for its settings.
- List your destinations and any change you need to make to the data on the way.
- Keep one purchase source per platform. A container and an app sending the same purchase to one pixel or conversion action can count it twice. Duplicate purchase events explains why.
- Test side by side before you switch anything off. Running two trackers side by side shows how.
What HonestTag does
- No container to host. HonestTag runs its own tracking and sending, so there is no server for you to set up. Its tracking runs on Cloudflare's network, and each store gets its own tracking address. On paid plans, one optional DNS record (CNAME) moves that address to a subdomain of your store's domain (tracking domain docs). Hosting a container is something HonestTag will not do.
- Purchases from the order. Shopify sends HonestTag the order webhook, HonestTag joins it to the visitor record, and applies the recorded consent before anything is sent (server-side delivery docs).
- Sent to the platforms you connect, on a paid plan, up to your plan's number of destinations at once, with a proof for each delivery you can open.
- What it is not. HonestTag is not a Google Tag Manager replacement. It builds its own purchase events, so there is no event schema to write, and no place for your own transformations or tags. If you need those, a container fits. HonestTag vs Stape sets out both side by side.
- Runs beside a container. Start free and compare HonestTag with your server-side GTM setup before you change anything.
Frequently asked questions
Is server-side GTM free?
The default setup can be. Google says the default deployment of a GCP project with a single server is free in most cases, and recommends it for testing limited traffic volumes only. Once you upgrade your Cloud Run environment, Google says to expect $30-$50 per server per month, and that large amounts of network traffic may increase this cost. For live traffic, its overview recommends at least 3 instances per container; its Cloud Run guide recommends at least 2.
Where should a server-side GTM container run?
On your store's own domain, for the first-party benefits. Google says the default endpoint runs in a third-party context, and that to unlock the benefits of a first-party context, such as more durable cookies, your tagging server and your website have to run on the same domain.
Do I need a developer for server-side GTM?
Usually someone technical. Google calls its server-side course suitable for tech-savvy marketers and developers, and if you run web GTM as a Shopify custom pixel, Shopify calls custom pixels an advanced feature that requires JavaScript knowledge.
Can I run server-side GTM and HonestTag together?
Yes. Keep one purchase source for each pixel and conversion action, so the same order is not counted twice. The free Mirror plan sends no purchases, so it cannot add a second one.
Get server-side tracking with no server to babysit
HonestTag runs its own tracking and its own sending, so there is no server or container for you to host or keep alive.
- Feed your ads a clean signal. The platforms you send to get each verified purchase, new customers marked as new.
- Catch the sales your pixels miss. Purchases are sent from your Shopify orders, server to server.
- Know what to scale. A weekly scale, hold or cut call when the data supports one, and proof behind every attributed order.
- Start free. Keep your current tracking while you look.
Related reading: server-side tracking, Shopify custom pixel vs app pixel, and HonestTag vs Stape.