Get started
Why are my analytics events or parameters missing from Pixel Trail?
Check recording, filters, browser permissions, capture health, and unsupported payloads.
A quiet timeline can mean the event did not fire, but it can also mean Pixel Trail could not observe it. Check these in order before changing your tracking code.
Check recording and the visible view
Confirm History for is the intended website and Record is On. By default, only tabs you record are captured; opening another website is not permission to record all tabs.
Choose All providers, clear search, reset Filters, and restore Show history if Clear view is active. Then add a marker, repeat the action, and wait for requests to finish.
Recording cannot recover earlier requests. For initial page events, record first and reload. Private windows, browser settings, and extension pages are excluded.
Check website access
Your browser must allow Pixel Trail to inspect the website and the analytics destinations it contacts. Access to the visible page alone may not expose a third-party collector.
In Chrome, review Pixel Trail’s site-access settings under Manage extensions. In Safari, review Safari Settings → Extensions → Pixel Trail and its website permissions. Managed browser policies can restrict what you can grant.
Read capture diagnostics
Open Settings → Capture → Capture diagnostics. Look for missing website permission, unavailable request bodies, or a limited/unavailable page observer. Enable page observations and save if you need API intent or data-layer activity.
Browser-reported request failures appear when exposed to the extension. A blocker can prevent a request early enough that Pixel Trail never sees it. Workers, redirects, iframe permissions, and browser restrictions can also limit capture; Pixel Trail is not a universal log of every blocked attempt.
Check the payload and endpoint
If the request appears but properties do not, open Request, Raw, and Capture notes. Binary or compressed formats, unsupported schemas, size limits, and redaction can prevent a field from being displayed. Clarity and Hotjar collection bodies are not decoded into analytics events.
For a first-party GA4 endpoint, add an exact collector mapping. Other custom proxy endpoints may remain unsupported.
When contacting support, include browser/version, provider, the action, recording/diagnostic state, and a reviewed sample export. Remove sensitive values first. Keep provider ingestion checks separate from what Pixel Trail observed in the browser.
Still need help? Contact support.