THE TRACKING PLAN
Every event, as it happens
Browse the store in another tab and watch this fill up. Each event shows its canonical payload, whether it conforms to the schema, and what every destination did with it, including the ones that deliberately refused it.
- Events captured
- 0
- Schema conformity
- -
- Plan version
- 2026.08.3
- Consent
- Unresolved
Routing mode
Direct talks to each vendor SDK from this page. Segment makes one call and lets the CDP fan out. Dual runs both, so the same event can be compared on each path - it carries one messageId either way, which is what makes it a comparison rather than two unrelated streams. Server silences every browser tag and sends from our own edge instead: no vendor JavaScript runs in the page at all. The choice persists across tabs, so you can set it here and browse elsewhere.
Synthetic population
Generate traffic with a known answer
Warehouse · ClickHouse
Every event above also lands in ClickHouse. These queries run against it live, from this page. The questions are a fixed set rather than a SQL box - an open query interface on a public page would let anyone spend money on a database billed by the second, which is a worse demonstration than a curated one.
Pick a question above. The warehouse is idle; the first query will pay the wake.
Warehouse · BigQuery
The same events land in BigQuery too, on a different cloud with a different row shape and no shared code between the two legs. That is the portability claim being shown rather than asserted: pick "Most recent" on both panels and the same messageId appears in each. BigQuery has no idle state to wake, so what is worth watching here is not the clock but the bytes - it bills by what a query scans, and the panel reports that.
Pick a question above. Not reachable right now.
Registered destinations (6)
Local collector
server · functional · free
Amplitude
direct · analytics · billed
Google Analytics 4
direct · analytics · billed
Segment
segment · analytics · billed
Microsoft Clarity
direct · analytics · billed
Server leg (/api/track)
server · functional · free
The server leg is one destination here and several vendors behind it. Its own verdict reports what our edge did with the event; each vendor it forwarded to reports separately, indented, with the status code that vendor actually returned. A browser tag cannot do that - it hands off to an SDK and never hears back, which is why the tags below say “queued” where the server leg says 204.
Event stream
Nothing captured yet. Navigate the store and events will appear here immediately.
Detail
Select an event to see its payload and dispatch results.
The plan itself
Version 2026.08.3, stamped on every event above. 19 events, following the Segment V2 Ecommerce Spec. Anything not on this list is rejected at runtime rather than quietly accepted.
| Event | Fired so far |
|---|---|
| Page Viewed | 0 |
| Products Searched | 0 |
| Product List Viewed | 0 |
| Product List Filtered | 0 |
| Product Clicked | 0 |
| Product Viewed | 0 |
| Product Added | 0 |
| Product Removed | 0 |
| Cart Viewed | 0 |
| Checkout Started | 0 |
| Checkout Step Viewed | 0 |
| Checkout Step Completed | 0 |
| Payment Info Entered | 0 |
| Order Completed | 0 |
| Signed Up | 0 |
| Signed In | 0 |
| Consent Updated | 0 |
| Experiment Viewed | 0 |
| Tool Used | 0 |