Why this matters
Click counts are the easiest number to celebrate and the easiest one to be misled by. A campaign can pull thousands of clicks and convert almost none of them; another can look quiet at the top and quietly drive most of your installs and revenue. If you only ever see clicks grouped by link, those two campaigns look more alike than they are.
The Campaigns view fixes the unit of analysis. Instead of one row per link, you get one row per campaign — with the whole funnel attached, so you can judge campaigns on what they produced, not on how loud they were.
What you see
Open the Campaigns tab on your Analytics page and your links roll up by UTM. Each row carries the full funnel:
- Clicks — how many clicks the campaign drove.
- Installs — installs attributed to those clicks, following each click through to its app install.
- Conversion rate — installs as a share of clicks, so a high-volume / low-yield campaign can't hide behind its click count.
- Revenue — in-app revenue from the installs each campaign produced (click → install → in-app event).
You can group by campaign, source, or medium, and rows are ordered by installs first — the campaigns moving the needle rise to the top. Pick a campaign value to filter down and focus on a single line.
How it works
The funnel is built link-natively: it starts from real clicks on your links, joins each click to the install it produced, and joins each install to the in-app events it generated. Revenue is parsed straight from your events — no modeling, no estimates. SDK-created share links are excluded so the numbers reflect your marketing links, not in-app sharing.
Getting started
Open Analytics and select the Campaigns tab. Make sure your links carry UTM parameters — campaigns are grouped by utm_campaign, utm_source, and utm_medium — and the funnel fills in as clicks and installs roll up. For more on tagging links and reading the funnel, see the Analytics docs.