NOTE-015 · FIELD NOTE FILED 08 NOV 2026 · REVISED 13 NOV 2026 F-401 F-102 F-201
Stape alternatives for server-side GTM hosting compared (2026): TAGGRS, Addingwell, Cloud Run, Tracklution.
ABSTRACT — TAGGRS, Addingwell and Google Cloud Run run the same server-side GTM container Stape does. Tracklution replaces the container instead. Who keeps each running, what logs you see, where the servers are, how to move.
Baris Asa, tracking consultant, London · Last checked: November 2026
The direct Stape alternatives are TAGGRS and Addingwell, which host the same server-side GTM container, and Google Cloud Run, where it runs in your own Google Cloud project. Tracklution is not a like-for-like swap: it replaces the container with its own connectors.The short verdict. Nobody on your side runs servers and you want to keep GTM: Stape, TAGGRS or Addingwell. Someone already runs your Google Cloud, or data and billing must stay in your own account: Cloud Run. Nobody to maintain a container at all: Tracklution.
If your numbers are wrong now, moving host rarely fixes it. The host keeps a server answering. Missing or doubled purchases usually come from what is inside the container (tags, triggers, dedup keys), not from the host. Start with Server-side GTM errors before you pay for a move.
I have no partnership, affiliate or commission arrangement with any tool on this page, and I don’t resell hosting.
Check what you have first
A server container is the set of tracking rules that runs on a server instead of in the shopper’s browser. Before comparing hosts, get four answers from your agency or developer:
- Which host, and which plan? The bill tells you.
- How many days of server logs can you see? Zero is a common answer.
- Whose account is it billed to? It should be the brand’s.
- Who has admin on the GTM server container and on the DNS record that points your tracking subdomain at the host?
Not sure you need server-side tracking at all? You don’t need server-side tracking (yet). On Shopify, the native apps and paid tools are compared in Elevar vs Stape vs Littledata vs native.
What to compare
Five things decide it. Every vendor below bills on volume, so compare price last, with your own monthly request or event count from their pricing pages.
- Container or no container. A GTM server container gives you control over every tag and costs someone’s time. A managed product does the reverse.
- Who keeps the server running. Updates, capacity on your busiest day.
- Logs. When Meta shows fewer purchases than your shop, can you see what the server received and sent on? For how many days?
- Where the servers are. Whether you can choose UK or EU, and whether the vendor publishes it.
- A way out. Whether moving later is documented.
The options at a glance
| Option | Keeps it running | Logs you can see | Where |
|---|---|---|---|
| Stape | Stape | Paid plans: 3 or 10 days | Published zones, incl. England |
| TAGGRS | TAGGRS | Request dashboard | Chosen at set-up, list not published |
| Addingwell | Addingwell | Errors; raw logs on request | Not published |
| Cloud Run | You | Every request, in your project | You choose, incl. London |
| Tracklution | Tracklution (no container) | Its own dashboard | EU (AWS Stockholm) |
Read from each vendor’s own documentation on 8 November 2026. Sources are at the end.
Each option, briefly
Stape
Stape hosts your server container. You create it in Tag Manager and paste its Container Config, the string that links it to a server, into Stape.
- Best for: brands that want server-side GTM with nobody running cloud servers. Its Shopify app (“Stape Conversion Tracking”) adds data layer events and sends purchase and refund webhooks to the server container.
- Not for: a team that needs request logs without paying for a plan.
- One minus, logs: Stape keeps 3 days of logs on Pro and 10 days on Business and above. Three days is gone by the time a weekend sale is questioned on Wednesday.
- One more step for logs: outgoing logs (what the server sent to Meta or GA4) need a toggle that switches on Monitoring, a Business-plan feature.
Stape’s zone list (updated 6 April 2026) includes “EU North (England)” under Stape Global, and Poland, France, the Netherlands and Italy under Stape Europe. Its custom loader serves the GTM and GA4 scripts in a way it says reduces ad-blocker losses.
TAGGRS
TAGGRS, based in the Netherlands, also hosts your server container. Its home page describes “European independent infrastructure with UpCloud”; elsewhere it describes its servers as “strategically distributed around the world”.
- Best for: brands that want a host outside Google Cloud, with a dashboard of incoming requests and of server-side against browser counts. Its Shopify app builds a GTM data layer for server-side tracking.
- Not for: anyone who needs a named UK region in writing before signing. You pick a server location at set-up, but I found no published list.
- One minus: its pricing page says each account is intended for one website. An agency with many clients plans for that from the start.
Addingwell
Addingwell, now “Addingwell by Didomi”, hosts your server container and links to it with the configuration token from Tag Manager.
- Best for: teams that want alerts without building them. It emails on DNS errors, an invalid token, data drops, gaps, duplicated events and failed tags. Its Shopify app installs the GTM web snippet and uses a Custom Pixel for checkout events.
- Not for: anyone who wants every request visible by default.
- The standard logs give a high-level view and the errors platforms send back.
- Raw logs go to BigQuery on request, for 30 days per activation, and not backwards.
- One minus: it does not publish where its servers are. Its pricing page sells a multi-region add-on for response times, which is not the same as choosing where data sits. Ask in writing.
Google Cloud Run
Cloud Run runs the server container in your own Google Cloud project.
- Best for: a business with someone who already looks after Google Cloud, or a policy that data and billing stay in your account. Google lists
europe-west2(London) as a Cloud Run region. Tag Manager can provision Cloud Run for you, but Google’s guide sets the region only in the manual route, so for London provision it manually and chooseeurope-west2. - Not for: a team with no one to own updates and capacity. Google’s guide says to deploy a new revision for each major release and recommends at least two instances.
- One minus: the cost is your Google Cloud bill, not a plan, and Google warns that request logging alone can bring significant charges on a busy site. Set a billing alert.
Who does each job on Cloud Run against a managed host is set out in Server-side GTM hosting: who maintains what.
Tracklution
Tracklution (Tracklution Oy, Helsinki) is the odd one out. Its comparison page says there is “no need for server-side GTM container”. It runs the server side as a service, with built-in connectors for GA4, Google Ads, Meta, TikTok, LinkedIn and others, and says it keeps those connectors updated itself.
- Best for: a brand with no one to maintain a server container that wants Meta, Google and other platforms fed from a server.
- Not for: a team that needs a lot of its own logic between browser and platform. Tracklution has event mappings, block rules and webhooks, and its rules for creating and transforming events are in beta; a container gives you more room.
- One minus: you move from tags you can read to a vendor’s connectors. When a number looks wrong, you depend on its dashboard and its support, not your own Preview.
It says customer data is stored in the EU, in AWS Stockholm, and that it passes the visitor’s Consent Mode states to Google without changing them. On Shopify it installs through an app with a Custom Pixel and an order webhook.
The two-way choice, with logs, Meta dedup and consent defaults, is in Stape vs Tracklution.
Moving off Stape (or onto it)
The container moves as it is. The work is the DNS, the testing and the switch-over, not a rebuild. (Coming from a browser-only setup rather than another host is a different job: see moving from client-side to server-side GTM.)
- Connect the new host. It needs a Container Config from Tag Manager (Admin, Container Settings). A container set up by hand, as on Stape, can usually be relinked with its Container Config. One that Tag Manager provisioned on Google Cloud cannot: TAGGRS and Addingwell then ask for a new server container, into which you import an export of the old one (Admin, Export Container). Stape’s own migration guide always uses a new container and an import.
- Set up the tracking subdomain at the new host: a DNS record at your domain provider.
- Repoint everything that sends to the server: the Google tag’s server container URL, any other tags, and any webhooks. A host’s Shopify app may send order and refund webhooks to the old server.
- Test in Preview until every purchase tag fires.
- Publish, then switch off the old server, so purchases aren’t sent twice (F-102 ).
Moving to Tracklution is a different job: you rebuild what the container did in its connectors, then retire the container.
What no host changes
- Consent. A server event must still respect what the visitor agreed to (F-201 ). Every host forwards what your tags send. The checks are in Consent Mode v2 with server-side GTM.
- Double counting. Browser and server both sending a purchase without a shared
event_iddoubles it in Meta, on any host (F-102 ). - Ad-blocker losses, by themselves. A server on your own subdomain gets back some of the events blockers stop, for visitors who agreed, and more if the scripts are also served first-party (F-401 ). How much depends on your audience. Measure it before and after.
When you need a person rather than a tool
Choosing the route, moving the container, and leaving you owning every account, with one page that says where it runs: that is who to hire to set up or fix server-side GTM.
I’m Baris Asa, a London tracking consultant. Eight years in tracking, 19 faults on file in the archive.
Send your current host, your store platform and which numbers disagree to [email protected].
If you are still deciding whether to run a server at all, start with server-side tracking explained.
Common questions
What are the alternatives to Stape for server-side GTM?
TAGGRS and Addingwell host the same server-side GTM container Stape does, and Google Cloud Run runs it in your own Google Cloud project. Tracklution is a different kind of product: it runs server-side tracking with its own connectors and needs no server-side GTM container.
Is Tracklution the same as Stape?
No. Stape hosts a server-side GTM container that you, your agency or a consultant build and maintain. Tracklution says you need no server-side GTM container: it runs the server side itself, with its own connectors for GA4, Google Ads, Meta and others. You trade control over each tag for less to maintain.
Can I move my server-side GTM container from Stape to another host?
Yes, and the tags come with you. The new host takes a Container Config from Tag Manager. A container set up by hand, as on Stape, can usually be relinked; one provisioned by Tag Manager on Google Cloud cannot, so you create a new server container and import an export of the old one. Then point everything that sends to the server at the new subdomain: the Google tag’s server container URL, other tags, and any webhooks such as Shopify order and refund webhooks from a host’s app. Test in Preview, then switch off the old server so purchases are not sent twice.
Which server-side GTM host keeps data in the UK?
Cloud Run can: provision it manually in Google Cloud and choose europe-west2 (London). Stape lists a zone called EU North (England). TAGGRS asks for a server location at set-up but does not publish a region list, and Addingwell does not publish where its servers are, so ask both in writing. Tracklution says customer data is stored in the EU, in AWS Stockholm.
Which host is best for Shopify?
Stape, TAGGRS and Addingwell each have a Shopify app that sets up a GTM data layer for their server container, and Tracklution installs through a Shopify app with an order webhook. Before any of them, check whether Shopify’s own Facebook & Instagram and Google & YouTube apps already cover you: Elevar vs Stape vs Littledata vs native.
Sources
Read on 8 November 2026:
- Google for Developers: manual set-up (Container Config, any Docker environment) and Cloud Run set-up (automatic or manual provisioning, region in the manual commands, new revisions, at least two instances, logging charges, billing alert); Google Cloud: Cloud Run locations (
europe-west2, London) - Stape: create a server container, server zones, logs, custom loader, migration to Stape, pricing, Shopify app
- TAGGRS: home page, infrastructure, GTM server hosting, switching from Google Cloud, pricing, Shopify app
- Addingwell: home page, set up the server-side environment, logs, alerting, Shopify app, pricing
- Tracklution: home page, Tracklution vs server-side GTM, GDPR and Consent Mode v2, Shopify installation, pricing