Why a workspace-wide install view matters
Your link-level analytics answer "how did this deeplink perform?" But sometimes the question is broader: is my data even arriving? How many app installs am I getting in total, how many got attributed to a link, and how confident is that install attribution? When you're validating an SDK integration or sizing up organic versus attributed growth, you want every install in one place — not filtered down to a single deeplink.
The Installs dashboard is that view: every install your SDK reports for the workspace, attributed and organic together, scoped only to your organization. It's the install-side counterpart to the Events firehose — the "is my mobile attribution data flowing?" surface.
What the Installs dashboard shows
At the top, five headline stats frame the time window:
- Total installs — every install your app's SDK reported.
- Attributed vs Organic — the split between installs traced back to a LinkForty link and the rest.
- Attribution rate — the share of installs tied to a deeplink.
- Avg confidence — how strong those attribution matches are, on average.
Below the stats, an install breakdown table slices the same data by dimension — platform, OS version, language, attributed-vs-organic, attribution confidence, link, campaign, source, or medium. Every row carries installs, attributed count, attribution rate, and open rate, so you can see at a glance which platforms and which campaigns are actually converting installs to app opens.
Attribution quality and retention, in context
Two more cards round out the picture:
- Attribution quality — how installs were matched and how reliable those install-attribution matches are, so you can trust (or question) the numbers.
- Retention — whether the installs from this window actually stuck around.
A time-range selector switches the whole dashboard between the last 7, 30, 90, or 365 days.
How install attribution flows in
If an install is attributed, it counts toward a link; if it isn't, it lands in organic — nothing is dropped. Attribution itself follows LinkForty's attribution windows and matching model, and the SDK identity each install reports (after the iOS, Android, and Flutter SDKs reached parity) feeds the platform and confidence breakdowns.
For metrics scoped to one specific deeplink, the Analytics → Installs tab stays the place to go; this dashboard deliberately shows the whole install stream across the workspace.
Get started with install analytics
Open Installs in your dashboard. Once your app's SDK starts reporting installs, the headline stats and breakdowns populate automatically — no extra setup beyond a working SDK integration.
New to the SDKs? Start with the SDK integration guide, then see app analytics for the full reference on installs, opens, and in-app events.