Journey Debugger for GA4 & GTM

Journey Debugger turns one deliberately recorded web journey into a visual, screen-by-screen analytics report. Start capture from the toolbar, complete the flow you want to test, then stop capture to review the journey. Each report connects the visible page, the CTA or control selected, the before-click screen, the next state, and the browser-observed GA4/GTM evidence. Use Journey Debugger to: - follow a clear journey-so-far path; - review screenshots and aligned CTA markers; - see event name and Event Category at a glance; - inspect eventAction, eventLabel, event parameters, user properties, item parameters, consent fields, and custom dimensions; - inspect Data Layer pushes, privacy-safe computed state, and detected GTM or Google tag containers; - distinguish product events from GTM technical activity; - connect supported GA requests without presenting them as downstream GA reporting proof; - copy event names in one click; - export a privacy-scanned offline HTML report or safe JSON evidence summary. The optional “Follow tabs opened by this journey” control is off by default. When enabled, Journey Debugger can continue only into a direct child tab that Chrome verifies was opened by the recorded journey. A new destination origin requires explicit approval. Tab evidence remains separated and the report connects the source CTA to the destination landing step. A focused DevTools panel provides live analytics inspection for the selected tab, including observed events, Data Layer/container state, and bounded recovery of recognized GA requests already present in that tab. Raw DevTools HAR content is not stored. Privacy controls run before durable local storage. Detected personal, payment, authentication, account, and vehicle-identifying content is masked or redacted. A final privacy scan can block unsafe exports. Users should still review every report before sharing it. Captured evidence remains in Chrome extension storage on the user’s device. Version 0.1.5 does not upload reports to the publisher, use remote AI, include publisher telemetry, sell captured data, or send captured evidence to an external service. Users can delete one capture or all local Journey Debugger data. Important limitations: - browser-observed requests do not prove that Google Analytics processed or reported an event; - authenticated Google Analytics property readback is not enabled; - restricted pages, inaccessible frames, protected media, or inactive-tab screenshot misses are shown as capture limitations; - the extension captures screenshots and structured evidence, not video. Journey Debugger is designed for product managers, analysts, developers, and QA teams who need to understand a funnel screen by screen and CTA by CTA.