Attribution overview
Attribution overview in the Marketing area (Attribution) — route /marketing/attribution.
Attribution overview lives in the Marketing area of the dashboard, under Attribution.
At a glance#
| Dashboard route | /marketing/attribution |
| Area | Marketing (marketing) |
| Group | Attribution |
| Platforms | Available for every app platform. |
What it does#
Attribution is the control room for install and conversion attribution: connection status per network, KPIs on what is being attributed, the live event feed with a detail drawer per event, and the configuration for how attribution behaves.
It is the page that answers "is attribution working at all?" before any of the reports built on it are worth reading.
When to use it#
First, before any other Marketing page. Every channel report, every ROAS figure and every campaign comparison depends on attribution being connected and matching. A confident-looking channel breakdown computed from 30% match coverage is worse than no breakdown, because people act on it.
Also whenever a network's numbers stop agreeing with the network's own dashboard.
Workflow#
Check every connection is live
A network that has silently disconnected keeps its historical data and stops receiving new attribution. Nothing about the reports will look broken.
Read the unattributed share
It is the honest measure of coverage. Attribution that matches a minority of installs cannot support channel-level decisions.
Open individual events in the drawer
When a specific install attributed wrongly, the event as received is where the answer is.
Then go read the reports
Channels, Campaigns and Cost & ROAS all sit on top of this.
Permissions and prerequisites#
Requires at least one connected network — see Media partners — and install and conversion events from the SDK.
Limits and edge cases#
Networks disagree with each other and with you. Each self-attributes with its own rules and window; overlapping claims are normal.
Attribution windows matter. A conversion outside the window is unattributed rather than attributed to organic.
Unattributed is not organic. Conflating them overstates organic performance.
Troubleshooting#
Everything is unattributed. No network is connected, or install events are not carrying the referral data. Check connection status first.
Our numbers are lower than the network claims. Expected — the network counts its own view-through and click-through generously. Compare trends, not totals.
Where the data comes from#
Device identifiers must be supplied via events.setIdentifiers() once consent allows.
From the SDK
Served by
Attribution
Tracking