Features
Event debugger and lineage
When a number in an ad platform looks wrong, you find out why in one place — not by guessing between browser console, vendor UI and a colleague's memory.
Event lineage
Example data: Static example state — not live traffic, no real customer data.- Event
- purchase · evt_…7f2a
- Origin
- browser SDK + server (shop webhook)
- Configuration
- version 12, signature verified
- Consent snapshot
- analytics, marketing · source: CMP
- Click ids
- gclid (captured 3 days ago)
Delivery attempts
| Destination | Status | Result |
|---|---|---|
| Meta Conversions API | 200 | accepted, deduplicated by event id |
| Google Ads | 200 | accepted, deduplicated by order id |
| TikTok Events API | 503 | retry 2 scheduled with backoff |
{
"event": "purchase",
"event_id": "evt_…7f2a",
"order_id": "A-1042",
"value": 129.9,
"currency": "EUR",
"user": { "em": "sha256:…9c1e" },
"click_ids": { "gclid": "…" }
}One purchase, read from origin to vendor answer.
Example event stream: delivered events, one deduplicated purchase and one server purchase blocked for a missing marketing purpose.
One event, the whole path
Open any event and read its story: source and SDK version, the consent that was granted at that moment, captured click ids, the configuration version that routed it, and the delivery attempt per destination including the redacted payload and vendor answer.
The debugger follows an event from the origin through normalization, the consent decision and every delivery attempt. Drops are never silent: each carries a reason such as missing consent, blocked PII, an invalid name, a duplicate or a paused destination.
How it is built
The technical decisions behind the capability — the proof after the benefit.
01
Redacted, not hidden
Payload previews show structure and hashed identifiers so you can verify mappings without exposing personal data or tokens.
02
Test events through the real pipeline
Test events are flagged, run through the same queue and worker, and report the vendor's verdict — no simulated success.
03
Drops are explained
Every dropped event carries a reason: missing consent, PII blocked, invalid name, duplicate, paused destination or policy block.
Debugging by console versus debugging by lineage
The same question — why did this purchase not reach Meta? — answered two ways.
| Debugging by console versus debugging by lineage | Browser console and vendor UI | Event lineage in Track |
|---|---|---|
| Where to look | Network tab, tag preview mode, the vendor's event manager | One event record with every attempt and answer |
| Consent at that moment | Unknown; reconstructed from the banner settings | Stored as a snapshot with the event |
| Server-side events | Invisible from the browser | Same lineage, marked with their origin |
| Personal data | Raw payloads in logs and screenshots | Hashed identifiers, redacted previews |
What you can verify
Product facts you will find in the dashboard, the docs and the audit log.
- Filter by event name, state and source
- Per-destination attempt history with HTTP status and error class
- Vendor test-mode hints per platform
- Links straight into the destination wizard
Questions
- How long are debugger records kept?
- Delivery attempts default to 90 days and events to 13 months; both are configurable per organization in the privacy center.
More capabilities
Built on the same signed configuration and event schema.
- AI-guided setup
Describe your site, confirm each step, publish a signed configuration.
- Server-side event router
One event, every platform: browser and server delivery with shared deduplication.
- Data quality and health score
A single score with explainable components and issues that link to their fix.
- Consent-aware by construction
Strict opt-in defaults, Consent Mode v2, purpose-based destinations, no replay after consent.
- Click ids and attribution done right
Capture only the ids the destination needs, only with consent, only for the documented window.
Try it on your domain
Create a site, install one snippet and let the assistant configure the first destination in minutes.