Integration · Google Tag Manager
Validate Every GTM Tag With Real Session Telemetry
Stop QA-ing tag firing in DevTools. Relyv watches every container load, validates trigger conditions, and flags tags blocked by consent.
What you get
Tag firing audit
Every tag that loaded, fired, or was blocked is logged per-session. Filter by tag name, by trigger, by consent state. Audit logs export to CSV.
Consent validation
See exactly which tags were blocked by Consent Mode v2 — and why. Catch the moment your consent banner started blocking conversions.
Trigger debugging
When a tag didn't fire, find out why: trigger condition didn't match, consent denied, custom HTML errored, prerequisite tag failed.
Server-side GTM ready
Tag every client-side event with a Relyv correlation ID. Match it to its server-side counterpart in your sGTM workspace; debug the round-trip.
Setup in four steps
- 1
Install Relyv (one snippet)
No additional GTM tag, no separate config. The Relyv SDK picks up your container automatically by reading window.google_tag_manager.
- 2
GTM container loads as usual
Your container, your tags, your triggers — unchanged. Relyv reads the firing telemetry as it happens; we don't intercept or modify execution.
- 3
Decoder annotates events
In the replay UI, an "Analytics" panel lists every tag firing — color-coded green / red / yellow for fired / blocked / errored.
- 4
Replay shows tag history
Click any tag entry to jump to the moment it fired. See the page state, the trigger condition that matched, and the resulting downstream events.
Implementation details
How we read the GTM data layer
Relyv attaches a non-blocking listener to dataLayer.push and to window.google_tag_manager. We never modify the container, never intercept tag execution, never delay anything. The decoder runs in a separate execution context with its own state.
Consent Mode v2 specifics
Every tag-firing event is tagged with the consent state at that moment: ad_storage, analytics_storage, ad_user_data, ad_personalization. Tags blocked by consent are logged with the specific signal that blocked them. "Why didn't Google Ads conversion fire?" answered with one click.
Server-side GTM correlation
When the user fires a client-side gtag event, Relyv injects a correlation ID into the event payload. Your sGTM container forwards the ID to downstream destinations (Google Analytics, Facebook CAPI, etc.). In Relyv's dashboard, click the client event to see the matching server event — including any transformations.
Frequently asked
Do you support server-side GTM?
Yes. Relyv injects a client-issued correlation ID into events; your sGTM container forwards it to downstream destinations. The dashboard shows the matched pair so you can debug the round-trip.
What about Adobe Launch / Adobe Analytics?
On the backlog. Currently supported: GTM (web), GTM Server-Side, Segment, Tealium. Adobe is community-vote tracked; teams contributing are getting prioritised.
Can I see custom HTML tag firings?
Yes. Custom HTML tags are logged with their name, trigger, and execution result. If the tag throws an error, the error message is captured — including any console.error output.
How real-time is this?
Real-time. Tag-firing events are decoded in the user's browser and surfaced in your dashboard within seconds. No batching, no delay.
Ready to wire up Google Tag Manager?
Stop QA-ing tag firing in DevTools. Relyv watches every container load, validates trigger conditions, and flags tags blocked by consent.