DocumentationTroubleshooting and privacy
Resolve common capture problems and understand how PostHog Debugger handles inspected data.
No events after opening DevTools
Reload the inspected page with DevTools and the PostHog panel open. Then confirm capture is not paused and clear any Events search, type, frame, delivery, or warnings-only filters that could hide the event.
Requests are blocked or failing
Ad blockers, privacy tools, browser shields, and corporate network controls can block PostHog ingestion before it reaches PostHog. Check Network for blocked or failed PostHog-shaped requests. To isolate the cause, test a clean browser profile or temporarily allow your development site in the blocking tool.
Self-hosted and proxied setups
Use Network to confirm the path actually sent by the page. Standard PostHog endpoint shapes are recognized, but a proxy that rewrites them into a custom path may not be detected. Include the path, extension version, browser version, and a description of the setup when requesting endpoint support.
How inspected data is handled
The extension processes inspected PostHog debugging data locally in the browser. Captured events, request data, SDK snapshots, and panel state are held in memory while DevTools is open; the extension does not persist captured payloads to its storage or send inspected data to the developer.
Sites can include sensitive values in their own PostHog payloads. Those values may be visible in your local DevTools panel, so treat exported captures and screenshots with the same care as other debugging artifacts. The extension observes requests the inspected page already makes; it does not resend inspected data to PostHog.
Its separate product-usage analytics are narrowly allowlisted and do not include inspected URLs, event names, properties, payloads, distinct IDs, or inspected flag keys. Read the full PostHog Debugger privacy policy for details.
Get help
For support, open a GitHub issue with the extension version, browser version, the endpoint shape you expected to capture, whether the issue remains after a reload with DevTools open, and whether a normal top-level HTTP or HTTPS page changes the result.