Media
5 items
Description
Debug PostHog analytics and Web Scripts in DevTools: config, events, network, identity, flags, replay, and privacy. PostHog Debugger (Unofficial) adds a dedicated PostHog panel to Chrome DevTools for developers validating analytics on their own sites, staging environments, localhost apps, embedded widgets, and self-hosted or reverse-proxied PostHog setups. It helps you inspect live PostHog behavior without leaving the page you are debugging: - Start with a Config view for loaded state, SDK version, destination, capture settings, consent/opt-out state, identity, and visible PostHog instances. - Inspect live PostHog events, custom properties, PostHog `$` properties, `$set`, `$groups`, timestamps, API keys, and raw JSON payloads. - Decode requests sent through fetch, XHR, sendBeacon, batch payloads, gzip, base64, form-encoded bodies, and query-string payloads. - Use the Network view to spot blocked requests, failed requests, wrong hosts, missing tokens, non-2xx responses, endpoint timing, and decoded-event matching. - Read feature flags, payloads, local override state, identity state, session IDs, replay diagnostics, and cookieless identity mode evidence when the page exposes a readable PostHog SDK instance. - Follow identify, alias, group, and reset activity in a dedicated Identity view. - Filter captured activity by search text, event kind, issue state, frame source, and request status. - Export captured sessions as JSON or HAR for local debugging, bug reports, and support handoffs. - Compare captured events against a local JSON tracking plan for naming convention drift and missing required properties when the linting feature is enabled. - Preview likely PostHog autocapture output locally so you can inspect target elements and property shape without sending a real autocapture event. Web Scripts debugging: - See a clear delivered, loading, loaded, failed, or unavailable status for Web Scripts in the top page and each observed iframe. - Review a compact per-script list using sanitized runtime IDs to confirm delivery and, when readable runtime state is available, whether each script initialized in that frame. - Continue to see delivery evidence for module-scoped PostHog SDKs that do not expose a readable `window.posthog` instance. - Correlate SDK lifecycle state with PostHog configuration and legacy Site App network requests while keeping executable JavaScript and JSON response bodies out of panel state, exports, and the DevTools bridge. - Use the Network view to verify Web Script resource status, size, and timing without capturing script source, functions, names, or arbitrary configuration metadata. Validation checks flag common implementation problems such as missing event names, missing distinct IDs, missing API keys, failed requests, duplicate fires, reserved prefixes, large payloads, clock skew, inconsistent naming, and likely PII in event properties. PostHog Debugger displays inspected analytics data locally in the DevTools panel. It does not send inspected event payloads, browsing data, or SDK state to the developer or to any external service, and it does not sell, share, or use inspected data for advertising or profiling. This extension is not an official PostHog product and is not affiliated with, endorsed by, or sponsored by PostHog.