Why per-project analytics matters
If you run more than one thing through LinkForty — separate marketing campaigns, different clients, a couple of mobile apps — your analytics have always been org-wide. That's useful for the big picture, but frustrating when you just want to know how this client's links performed last month without mentally subtracting everyone else's traffic.
Projects already let you group related links. Now that grouping flows all the way through to your numbers: every project has its own analytics view, scoped to exactly its links — nothing else mixed in. It's the per-project reporting layer that agencies, multi-brand marketers, and multi-app teams have been asking for.
A full analytics suite, scoped to each project
Open a project and you get the same analytics tabs as the org-wide Analytics dashboard — only filtered to that project's links:
- Clicks — click volume, trends, and UTM breakdowns for the project's links.
- Mobile — install attribution and in-app events attributed to those links.
- Web — on-site activity and conversions from the visitors those links brought in, via the Web Pixel.
The headline metrics, charts, and breakdowns on every tab refilter to the project automatically — the project's page mirrors the org Analytics page, link-for-link, just narrowed in scope. Your org-wide Analytics page stays exactly as it was, so the whole-organization view is always one click away.
What project-scoped reporting is good for
- Per-client reporting for agencies. Give each client a project and report on their links in isolation — no cross-contamination from other accounts, ready to screenshot or export.
- Campaign analysis. Bundle a campaign's links into a project and read its click, install, and conversion performance on its own, away from evergreen traffic.
- Multi-app and multi-brand views. Running deep links for more than one app or brand? Scope each one's analytics to its own project.
How project scoping works
A single project filter is threaded through the analytics endpoints. When you open a project, each query restricts to the links that belong to it; when you're on the org Analytics page, behavior is exactly as before — fully org-wide. It's additive and backward-compatible, so existing dashboards, links, and saved habits keep working unchanged.
One natural consequence worth knowing: organic, link-less activity belongs to no project, so a project-scoped view shows link-attributed activity only. That's usually what you want for client and campaign reporting — the results your links actually drove.
Get started with project-scoped analytics
- Group related links into a Project (see Organizing links with projects).
- Open the project from your Projects page.
- Use its Clicks, Mobile, and Web tabs to read that project's performance on its own.
Need the whole-organization picture instead? Your main Analytics page is unchanged and always shows every link across the org.