How it works
The building blocks every report shares, from visits and sources to models and views
Every report in Attribution is built from the same pieces: how visits are sorted into sources, which model splits the credit, which traffic counts, and which of these choices are saved as a view. This section explains each piece and where you shape it.
- Channels, filters & groups: the three levels the dashboard is organised in, and how a visit lands in one.
- Default traffic sources: the filters every project starts with, from Direct to Unknown Source, plus the All Traffic and Raw Traffic rows.
- The Dashboard Builder: turn unsegmented visits into filters of your own.
- Attribution models: linear, first touch, last touch, time decay and position based, with worked examples.
- Traffic options: whether direct visits receive credit, and the cutoff event that ends it.
- Saved views: one named set of all these choices, read by the dashboard, the reports and the MCP tools.
How these choices read on the dashboard itself is in the Dashboard report and its reference.
Updated about 1 hour ago