Docs
Provider coverage
Add to Chrome

Which analytics providers and payloads can Pixel Trail inspect?

Understand supported endpoint detection, decoded properties, and the limits of opaque transport.

Pixel Trail recognizes supported browser endpoints and payload shapes. Coverage is specific to those endpoints and formats; it is not a promise to decode every SDK version, proxy, worker, or server-side integration.

Analytics and advertising requests

The current detector includes GA4, Google Ads, Meta, Heap, TikTok, LinkedIn, Pinterest, Snapchat, X, Microsoft Ads, Segment, Mixpanel, Amplitude, PostHog, Plausible, and Matomo Cloud. It also recognizes Google Tag Manager and Google tag scripts. Legacy Universal Analytics IDs can appear as Universal Analytics.

Provider details vary. Supported payloads can expose event names, destination IDs, custom properties, ecommerce items, values, currencies, and event IDs when those values are present and readable. Known user identifiers and credentials are redacted.

Default endpoint matching uses recognized provider domains and paths. A self-hosted or proxied installation may not match. The configurable first-party mapping currently applies to exact GA4 collector URLs.

Heap payloads

Pixel Trail decodes supported Heap 5 Protocol Buffers messages and supported JSON or encoded JSON event batches. Depending on the message, details can include custom properties, page context, interaction targets, SDK information, and capture time. Binary Heap property values retain their wire-format strings.

Unsupported schemas, unavailable bodies, and decoder limits produce an Event batch or capture note rather than invented events. Account-defined Heap labels and server-only details cannot be recovered simply from an outgoing browser payload. Identity fields are deliberately excluded from supported binary decoding.

Clarity and Hotjar

Pixel Trail can identify supported scripts and collection requests. Their session-recording transport is not decoded into individual analytics events. Seeing their logo means recognized browser activity was observed, not that Pixel Trail can reconstruct a recording.

Supported page consent commands are shown as technical observations. GA4 wire fields such as gcs and gcd are preserved where available; Pixel Trail does not translate them into a complete consent-state verdict.

Browser Meta events do not establish Conversions API delivery or browser/server deduplication. Segment source requests do not establish downstream delivery. No request status proves attribution or provider ingestion.

Search documentation