TAGGRS is a Dutch company that hosts server-side Google Tag Manager containers on European bare metal, and does that well. If your question is "who runs my sGTM container on EU servers", TAGGRS is a fair answer.
Our question is different: who makes sure only consented data flows at all? TAGGRS's answer, in their own documentation, is: you do. Consent Mode is yours to configure in the container, their consent tooling observes signals rather than enforcing them, and their audit tool exists because customers routinely get it wrong. HeySignal was built so that this entire category of mistake cannot ship.
Pick TAGGRS if you are a GTM-fluent team that wants managed EU hosting for a container you fully intend to configure and police yourself, starting free.
Pick HeySignal if you want consent enforced by the platform: signed into every event, verified at the edge, refused on failure, translated per destination. And if "EU infrastructure" should include every product in the box, not most of them.
| HeySignal | TAGGRS | |
|---|---|---|
| What it is | Consent-first tracking gateway, own pipeline | Managed server-side GTM hosting |
| Consent enforcement | Cryptographic (HMAC-SHA256), fail-closed at the edge, per-destination categories | Not enforced; customer configures Consent Mode v2 in GTM; Consent Approval Graph is monitoring-only |
| Consent proof | Signed consent bound to each event, proof ID in the audit log | Google gcs/gcd parameters, unauthenticated |
| Infrastructure | Bunny.net edge + OVHcloud (France/Frankfurt), EU-only across all products | Core sGTM on own/UpCloud EU bare metal; Meta CAPI Gateway on Google Cloud (their docs: "falls under the U.S. Cloud Act") |
| GTM required | Optional (proxy mode keeps it, SDK mode replaces it) | Yes, GTM expertise is the operating model |
| Cookie policy | Identifier lifetimes extended only with matching consent | Cookie Recovery restores deleted marketing cookies; tracking script masks events against ad blockers |
| Certifications | None yet, SOC 2 Type II planned Q4 2026 | ISO/IEC 27001:2022 (DEKRA) |
| Over-limit behavior | N/A pre-GA pricing | Data stops flowing at the plan cap |
| Pricing | Early access; pricing at GA | Free 10k req/mo; Basic €25/mo (750k); Pro €65/mo (3M); Ultimate €145/mo (10M); ~13% off annual |
TAGGRS's Consent Approval Graph shows you which consent signals reached Google. Their docs state it "does not provide or replace a cookie banner" and that you still need a CMP. Configuration of Consent Mode in the server container is a customer task, and their own Tracking Audit Tool ships specifically to find "misconfigured consent mode" in customer setups. When the audit tool finds the problem, the data already flowed.
In HeySignal, an event without verified consent never enters the pipeline. There is nothing downstream to audit, because the mistake gets a 403 instead of a dashboard entry three weeks later.
Credit where due: TAGGRS's core sGTM hosting runs on European infrastructure ("100% TAGGRS Servers - 0% Google Infrastructure") and that is a real differentiator against US-cloud defaults. But their Meta CAPI Gateway runs on Google Cloud, and their own setup docs say the quiet part: it "falls under the U.S. Cloud Act". Sovereignty that depends on which product page you're on is a footnote problem your DPO inherits.
HeySignal has one answer for every product: Bunny.net and OVHcloud, named in a public subprocessor list.
TAGGRS sells Cookie Recovery, which restores marketing cookies that Safari deleted, and a tracking script marketed on "masking events against adblockers". Those features do work. We just think "the browser deleted it, so we put it back" is a sentence you eventually read aloud to a regulator. HeySignal extends identifier lifetimes server-side only while the matching consent is granted, and we put that in writing.
EU bare-metal hosting for the core product with server choice across six European countries, an ISO 27001:2022 certification (DEKRA, evaluated annually), a genuinely useful free tier, a large template gallery, agency features, and rapid feature shipping. If you want managed sGTM and accept consent as your own job, they are a credible European choice, and cheaper than DIY Cloud Run.
TAGGRS provides infrastructure and states plainly that you must collect consent and configure Consent Mode yourself; compliance depends on your configuration. Their core hosting is EU-based; their Meta CAPI Gateway runs on Google Cloud per their own docs.
No. HeySignal can proxy your existing GTM setup first-party, or replace GTM entirely with its SDK and no-code rules. Consent enforcement applies either way.
TAGGRS states data stops flowing when the request limit is exceeded, with an auto-upgrade offer. Check what a traffic spike in week four does to your attribution before choosing any volume-capped plan.
Yes. Keep your GTM container running through HeySignal's first-party proxy on day one, then move capture to the SDK at your pace with shadow-mode validation.
FACTS LAST CHECKED: 7 JULY 2026
All TAGGRS claims verified against taggrs.io pages (pricing, security, GDPR, infrastructure, consent-tool and Meta CAPI Gateway docs) on 7 July 2026. Prices are standard monthly billing; annual rates are lower.
BRAND