CONNECTIONS / Server-side GTM
Your sGTM container, extended to every ad platform.
Signals reads the event stream already passing through your server-side GTM container and forwards it to every platform you map. Add the Signals tag alongside your existing tags, or hand over the container, and each event reaches its destinations as it fires.
- ● sgtm :: signals live
- > tag fired event=purchase container=web-prod
- > tag fired event=lead container=web-prod
- hash sha256(email,phone) pii=cleared
- route meta · google · tiktok · x
- ✓ 4 destinations synced · match 79%
The signal Server-side GTM yields.
Every kind of signal that moves between Server-side GTM and the platforms, through one hashed, deduplicated route.
- Web conversions
- A container already tagging Meta or Google gets a Signals tag added alongside them, reading the same event stream without a second copy of your tagging plan.
Pick your platform. Every use case for it, in one place.
Every way Server-side GTM data moves, grouped by platform and ranked by how many use cases Server-side GTM supports.
Meta 2 
Google 1 
LinkedIn 1 
OpenAI 1 
Pinterest 1 
Reddit 1 
Snap 1 
TikTok 1 
X 1 From authorization to delivered signal.
-
Connect
Add the Signals tag to your existing sGTM container, or hand Datahash the container to configure and run.
-
Map
Event names, PII fields, and consent flags standardized against each destination's schema in the visual mapper.
-
Dedupe
Shared event IDs matched against whatever pixel or tag already fires client-side, so nothing counts twice.
-
Deliver
Per-destination delivery status and match feedback, checked in the live debugger before campaigns rely on it.
Server-side GTM questions, answered.
Does Signals replace our sGTM container?
No. Signals works as a tag inside the container you already run, or as a container Datahash manages on your behalf if you would rather hand that over. Either way, sGTM keeps doing whatever else it already does; Signals adds partner-verified destinations, dedupe, and match-rate monitoring on top of the tags already firing.
Who keeps the destination tags current as platforms change their specs?
With the Signals tag, Datahash does. Ad platforms change field names and endpoint requirements often enough that a tag left unmaintained starts failing without warning, so Signals ships updates to the destination side of the container as specs change, without your team tracking every platform's changelog.
How does dedupe work when a pixel is already firing on the same page?
Each event carries a shared event ID that both the pixel and the server-side tag send, so a destination receiving the same purchase from both paths counts it once, not twice. That ID is generated once per event and passed through the container unchanged, whichever path fires first.
NEXT STEP
See your Server-side GTM data working in every ad platform.
Ready to enable a use case, or still mapping what Server-side GTM data could do? Our team helps you find the right place to start.
