Click any row in Live Events to open the drawer. It slides up over the bottom of the panel and shows everything Pixel Auditor knows about that fire.
What the drawer shows
- Header — event name, platform, method, time, latency badge
- Payload table — every parameter and its value, sortable, copy-on-click
- Validation — required and recommended params for the event, with ✓ / ✗ marks
- Funnel mismatch alerts — when the event sequence doesn't match a known funnel (e.g.,
begin_checkoutwithout precedingview_item) - Routing summary — for GA4 hits, which property received the data (correlated by GTM hash or by timing)
- SST signals — if the fire was classified as server-side, the breakdown of why
- PII findings — every leaked field with the original key and a redacted preview of the value
- Consent state at fire — the
gcs=param value if present, plus the observed consent state
Resizing the drawer
- Drag the top grip to set any custom height
- Double-click the grip to toggle between default 45% and expanded 90%
- Click the framed × to close (or press Esc)
Parameter validation
Each platform has a validator with required and recommended parameters per event. Examples:
| Event | Required | Recommended |
|---|---|---|
GA4 purchase | transaction_id, currency, value, items | tax, shipping, coupon |
GA4 add_to_cart | currency, value, items | — |
Meta Purchase | value, currency | content_ids, content_type |
Bing UET purchase | revenue_value, currency_code | — |
Routing summary (GA4)
gtag.js routes hits through a single /g/collect endpoint. The drawer's routing summary shows which configured GA4 property actually received the hit, so you can tell "this purchase landed in property G-X but not property G-Y".
Correlation is by GTM container hash where present, or by timing window when the hash isn't available.
Funnel mismatch
For commerce funnels, Pixel Auditor tracks the expected sequence:
If an event lands out of sequence (or a step is skipped), the drawer flags it. This catches bugs like a purchase firing on every page reload.