You spent years on that container. You should not have to rebuild your tag setup to fix where the data flows. Point your snippet at your own subdomain, and HeySignal takes it from there.
Most "GTM proxies" are a blind tunnel with your domain on it. Ours reads what passes through:
We fetch gtm.js and gtag.js server-to-server, strip every Google tracking domain from the code, and serve the result from your first-party subdomain. Your visitors' browsers never open a connection to Google. Google's servers see the IP of a European edge node, not your customer.
The edge reads your CMP's consent cookie on every request and derives all seven Consent Mode signals from it, including ad_user_data and ad_personalization. Denial defaults are injected into the proxied script before Google's own code executes, so nothing fires in the pre-consent window, even if your banner loads late.
EEA traffic without verified consent is blocked at the edge by default. Global Privacy Control signals are honored. You choose per-region behavior for the rest of the world, and per-site controls decide whether IP addresses are stripped, anonymized, or passed, and whether real user agents travel at all.
BEFORE browser → googletagmanager.com
AFTER browser → data.yourshop.com → EU edge → Google
First-party serving means common blocklists no longer recognize the requests, so measurement of consenting visitors survives. We are comfortable with that because of what stands behind it: the same edge enforces consent policy on what it proxies. Recovering signal you were allowed to have is engineering. Recovering signal you weren't is a lawsuit with a feature name, and other vendors can keep that market.
Most teams start with proxy mode and drift toward the SDK as trust builds. Both run through the same European infrastructure.
No. You change the script source to your own subdomain. Tags, triggers and variables stay as they are.
Requests from HeySignal's European edge, carrying the consent signals computed from your CMP's verified state, with IP and user-agent handling you configured. Not your visitor's browser.
No. GA4 receives spec-compliant Measurement Protocol and collect traffic; Debug View keeps working.
No. An sGTM container is infrastructure you configure and police yourself. This is a managed edge that enforces consent policy on the traffic it proxies.
BRAND