Feature
GA4 + GTM Debugger Built Into Session Replay
See every analytics event, dataLayer push, and consent decision overlaid on the actual session. Stop guessing why your conversion event didn't fire.
Why teams pick this
GA4 event timeline
Every gtag call, conversion event, and parameter dump is overlaid on the session timeline. See `purchase` fire — or not — in the exact moment the user clicked checkout.
GTM container inspection
Container ID, version, all loaded tags, every trigger condition. We highlight tags that fired, tags that were blocked by consent, and tags that misfired.
Consent state at every event
The consent banner state, the user's choice, the resulting Consent Mode v2 signals — all logged per-event. "Why didn't Google Ads fire?" answered in 5 seconds.
dataLayer diff
See dataLayer state before and after every push. Catch the moment ecommerce.purchase.value goes from a number to a string and breaks all downstream tags.
How it works
- 1
Install Relyv (you probably already have)
No additional GTM tag, no separate snippet. The same Relyv SDK that records sessions also picks up the analytics layer.
- 2
Tags fire as users browse
The decoder watches gtag, dataLayer, and the GTM container in the background. Every event is captured with timestamp, parameters, and consent context.
- 3
Decoder annotates events
In the replay UI, an "Analytics" panel lists every tag firing, color-coded by status — fired, blocked, misfired, or pending consent.
- 4
Replay shows everything in context
Click any event to jump to that frame. See the page state, the click that triggered it, and the resulting tag fire — all on the same timeline.
Under the hood
Why DevTools isn't enough
DevTools shows what fired in your browser, right now. It doesn't show what fired in production for the user who couldn't complete checkout last Tuesday. Relyv decodes the same telemetry retroactively, on real user sessions, with full context — including consent state and the page DOM at the moment of firing.
Consent debugging
Consent Mode v2 is a leading cause of "tracking is broken" tickets. Relyv shows the consent state at every event: granted, denied, or pending. We show whether the tag was blocked because of consent, blocked because of a custom GTM rule, or simply never fired because the trigger didn't match.
Server-side GTM ready
For teams running server-side GTM, Relyv tags client-side events with a Relyv-issued correlation ID. Match the client event with its server-side counterpart in your sGTM workspace; debug the round-trip in one place.
Frequently asked
Which tag managers are supported?
Google Tag Manager (web), GTM Server-Side, Segment, Tealium, and any custom dataLayer-driven setup. Adobe Analytics / Launch is on the backlog and has a community vote.
Can I see custom GA4 events, not just standard ones?
Yes. Every gtag("event", ...) call is captured, including custom event names and arbitrary parameters. The dashboard groups by event name and shows parameter histograms.
Is this real-time or batched?
Real-time. Events are decoded in the user's browser and surfaced in your dashboard within seconds. There's no separate Relyv → GA pipeline; we read the same telemetry your tags emit.
Can I get alerted when a tag stops firing?
Yes. Pro and above can set rules — "alert if `purchase` event fires fewer than 3× / hour for any 1-hour window". Alerts route to Slack, email, or webhook. The alerts microservice (gt-relyv-alerts) handles delivery.
Does the decoder run for mobile tags too?
Yes. The decoder reads tag calls as they happen in the browser regardless of device — mobile-web GA4 / Meta / Segment / GTM events surface the same way as desktop, alongside the new Wave-7 mobile-capture signals (PointerEvent, pinch-zoom, virtual-keyboard).
Can I push tag-validation failures into CRM tickets?
Yes. A failing tag (e.g. `purchase` not firing despite a checkout click) can route an alert into HubSpot or Salesforce as a Case, pre-filled with the session evidence and the AI-written root-cause analysis — bridging the marketing-team-detected issue and the engineering-team queue.
Ready to try it?
See every analytics event, dataLayer push, and consent decision overlaid on the actual session. Stop guessing why your conversion event didn't fire.