Configuration
—Install
—Verify
| Time | Event | Destination | Match quality |
|---|
Traffic sources
| Source / Medium | Visits | Views | Carts | Checkouts | Sales | Conv. | Revenue |
|---|
A visit is a PageView; each column is the number of events of that kind whose last touch was this source. Conv. = sales ÷ visits. Sources are recorded from 2026-09-15 — earlier events are counted in Verify only.
Campaign learnings
UTM parameters are kept and passed to integrations. Attribution is captured first-party for these learnings and is not forwarded to the ad platforms. Revenue-based — add ad spend for ROAS.
| Campaign | Source / Medium | Conversions | Revenue | Avg order |
|---|
| When | Value | Journey | Touches | Days |
|---|
Change log
Who changed what, and what happened to it. A client editing an operator-only field (pixel ID, access token, platform) is answered 200 OK with that field silently removed — so it shows here as partial rather than as nothing at all. Field names only; no values are ever stored.
| When | Who | Change | Outcome |
|---|