Help and support
Contact towersjavin@gmail.com. Include your browser and operating system versions, Pixel Trail version, the action you tried, and what you expected. A reviewed, redacted report can help; sending one is your choice.
For step-by-step instructions and screenshots, browse the Pixel Trail docs.
Start a recording
- Enable the extension and grant access to the website and any analytics destinations needed for inspection.
- Open Pixel Trail, choose the website under History for, and use the Record toggle. Opening Pixel Trail starts recording the current website by default; tabs you turn off stay off.
- Reload the website to observe its startup. Use Mark here before an action, then inspect the arriving events and parameters.
The default records the current website when you open Pixel Trail. Disable Record on open in Settings → General for a fully manual workflow. Settings → Capture offers page observation and decoding options. Settings → General offers recording scope and retention. Settings → Capture includes page observations, pinned parameters and explicit first-party GA4 collector mappings.
Choose a view
Both browsers offer a toolbar popup, inspector tab, separate window and developer-tools panel. Chrome also offers a native browser side panel. In Safari, press Option–Command–I on the website, select Pixel Trail in Web Inspector, and use Safari's docking controls. The extension cannot open Safari Web Inspector automatically.
Keep evidence separate
Detected means a tag/script was found. Intent observed and consent rows describe page-origin calls or commands. Sent, Completed, HTTP error and Failed describe browser transport evidence. None establishes analytics-platform ingestion, attribution, server-side deduplication or legal compliance.
Test a flow
Use Test steps to name a run and an action. Optionally specify a provider, event, destination, exact request count and parameter checks. Start the step, perform the action, wait for requests, then finish it. Export a readable report with the outcome and evidence. Checks count outgoing network events separately from API intent and tag detection.
Clear view or delete history
Clear view starts with an empty screen while preserving saved activity. Show history restores it. Settings → History & tools → Delete all history… removes saved events, checkpoints and test runs across every tab after confirmation; settings and recording state remain.
If expected activity is missing
- Check the selected website, recording/paused state and website access.
- Reload after enabling recording to capture startup events and discover scripts.
- Inspect Capture settings for observer/body limitations and recording scope.
- Check filters and restore hidden history.
- A custom/proxied GA4 collector needs an explicit exact-endpoint mapping.
- Unsupported formats, unavailable bodies, workers, redirects and blockers may limit visibility. Absence from the timeline does not prove no event was attempted.
Supported payloads vary by provider and SDK. Heap labels or derived properties defined only inside an account and server-only events cannot be retrieved from browser requests.
Privacy
History stays in your browser profile. Known identifiers are redacted on a best-effort basis; arbitrary custom values can still contain sensitive data. Read the privacy policy and review exports before sharing them.