A server-side Google Tag Manager container on Stape works without any extras, but Stape also offers a set of optional features it calls power-ups. Clients see a long list of toggles in the dashboard and ask which ones they should switch on. Some of them solve real data-loss problems; others are only useful in specific cases. This guide goes through the power-ups I use most, what each one does in plain English, and how I decide whether a store needs it.
If you are not sure what Stape is yet, start with what Stape is and how server-side GTM hosting works.
What are Stape power-ups?
Stape power-ups are optional features you enable for a server container in the Stape dashboard. They sit on top of the standard server-side GTM container and handle jobs that Google's software does not do on its own, such as serving scripts from your domain, keeping cookies alive longer or removing personal data. Each power-up is switched on per container, and some are only available on paid plans.
Here is a quick overview before the details:
| Power-up | Problem it solves | When I use it |
|---|---|---|
| Custom domain | Requests going to a third-party URL | Always |
| Custom Loader | Ad blockers blocking GTM and gtag scripts | Almost always |
| Cookie Keeper | Safari shortening cookie lifetime | When Own CDN is not possible |
| Own CDN | Server cookies treated as third-party in Safari | When the site's DNS and CDN allow it |
| Global CDN | Slow script loading for distant visitors | International audiences |
| Anonymizer | Personal data reaching GA4 | Privacy-sensitive businesses |
| Stape Analytics | Not knowing how much data is recovered | To measure the impact |
| Multi Domains | Several domains on one container | Brands with several stores |
Custom domain: the foundation
A custom domain is the first thing to set up on any Stape container. It connects your container to a subdomain of your own website, such as data.yourstore.com, using a DNS record. Without it, requests go to a Stape URL, which browsers and blockers treat as third-party.
Strictly speaking it is part of the core setup rather than a power-up, but nothing else on this list works well without it. On every Stape project I build, the subdomain is verified as Ready before I touch a single server tag.
Custom Loader: fewer scripts blocked
Custom Loader serves the Google Tag Manager (gtm.js) and Google tag (gtag.js) scripts from your own domain instead of Google's domains. Ad blockers keep lists of known tracking URLs, and Google's script domains are on most of them. When the same scripts load from your domain with a different path, they are much harder to recognise, so fewer visitors lose tracking entirely.
What it changes in practice:
- Stape gives you a new GTM snippet that loads from your tracking subdomain.
- You replace the standard GTM snippet on the website with that snippet, or let the Stape Shopify app or WordPress plugin do it.
- Events from visitors with ad blockers are more likely to reach your server container.
Custom Loader does not make tracking invisible. Some blockers and privacy browsers still detect it. But it is the power-up with the biggest effect on raw data volume for most stores I work with.
Cookie Keeper and Own CDN: longer-lasting cookies
Safari's Intelligent Tracking Prevention (ITP) limits how long some cookies can live. Cookies set by JavaScript can be capped to a few days, and in some cases cookies set by a server are shortened too, when the tracking subdomain points to a different IP address than the main website. Shorter cookies mean returning visitors look like new users, and conversions lose their link to the original ad click.
Stape offers two ways to deal with this:
- Own CDN serves your tracking subdomain from the same IP address as your website, usually through your existing CDN such as Cloudflare. The server-set cookies then count as genuinely first-party.
- Cookie Keeper stores key cookie values on the server and restores them when the browser has shortened or removed them.
You rarely need both. If the website's DNS and CDN allow Own CDN, I prefer it because it fixes the cause. When the client's hosting does not allow that, Cookie Keeper is a practical alternative. Either way, I check the cookie lifetime in Safari after the change rather than assuming it worked.
Global CDN: faster scripts worldwide
Global CDN loads your tracking scripts from a server near each visitor instead of one central location. For a store whose customers are in one country it makes little difference. For an international store, it reduces the delay before tags fire, which matters on slow mobile connections where visitors may leave before a purchase event sends.
Anonymizer: removing personal data
Anonymizer removes or anonymizes user data in the events sent to GA4, such as IP addresses and other identifiers. It is useful for businesses in privacy-sensitive markets or industries that want GA4 to receive less personal data by default.
Two things to keep in mind:
- It does not replace consent. You still need a consent banner and Consent Mode v2, and tags should respect the visitor's choice.
- Do not anonymize data that a platform needs for matching. Meta Conversions API and Google Ads enhanced conversions rely on hashed customer data, so those tags should be configured on their own terms, not stripped by a blanket rule.
Stape Analytics: measuring what you recover
Stape Analytics shows how many requests come through your container and how many are affected by tracking prevention or ad blockers. It turns "server-side tracking helps" into numbers you can show a client.
On Urine Shefa's health ecommerce store, for example, the Stape container showed 823 requests (17.37%) flagged as affected by tracking prevention. That is the kind of data loss a browser-only setup would not even report.
Multi Domains and other power-ups
Multi Domains maps several custom domains to one server container, which helps a brand running separate stores or language domains with shared tracking. It needs a higher Stape plan, so I only use it when a business genuinely has several domains.
Stape also adds features over time, such as file proxying, request delays and logs with longer retention. My rule is simple: if a power-up does not solve a problem you can name, leave it off.
How I choose power-ups for a client
I follow the same order on every Stape setup:
- Custom domain verified and working.
- Custom Loader installed and tested in GTM Preview.
- One cookie solution: Own CDN if the hosting allows it, otherwise Cookie Keeper.
- Stape Analytics switched on to measure the effect.
- Anything else only when there is a clear reason, such as Multi Domains or Anonymizer.
After each change I test the full funnel: GA4 DebugView, Google Ads conversion diagnostics and Meta test events, including deduplication between browser and server events. The Tea of Sylhet server-side build is a good example of a Stape container on a custom domain feeding verified revenue to Google Ads.
Final thoughts
Stape power-ups are useful, but they are tools, not a strategy. A custom domain, Custom Loader and one cookie solution cover most stores; the rest are for specific needs. If you want a second opinion on which ones your setup needs, I can review it as part of a free tracking audit or a full conversion tracking setup.