How to Track App Installs With Links: The 2026 Guide

TL;DR

• To track app installs with links: create a unique link per source, add a lightweight SDK to your app, and see which links produced which installs in a dashboard.
• No IDFA, no ATT prompt, no MMP required. The method works for creator partnerships, bio links, email campaigns, UGC, podcasts, paid press — anywhere you share a URL.
• Setup time: about five minutes per app.
• Cost: free for low-volume use. Paid tiers start at $40/mo for unlimited links and revenue tracking.
• What you get: clicks, installs, and revenue attributed to each link in real time.

If you want the full walkthrough, keep reading. If you already know the shape of the problem and just want the shortest path, jump to how the setup actually works.

What "tracking installs with links" actually means

When someone shares your app, they share a link. A creator on TikTok, a newsletter email, a Reddit comment, a QR code on a poster — it's all a link.

Every one of those links produces traffic. Some of that traffic installs your app. Some doesn't. Without tracking, you have no idea which link did what. You just see your install count go up and have to guess.

Tracking installs with links closes that gap. Each link gets a unique URL. When someone taps it, the click is recorded. When the install finishes, the install is recorded. Both events are tied back to the original link.

That's the whole idea. You create a link, you share it, and later you look at a dashboard that says "link X drove 43 installs." Multiply that by every place you share your app and you can finally see which channels are actually moving the needle.

Why plain App Store and Play Store links don't work

The default thing every developer does is drop a raw App Store URL or Google Play URL into their bio, tweets, and emails. That works for getting users to the store. It fails at everything else.

Three specific problems:

You can only link to one store. Half your iPhone audience taps a Google Play link and bounces. Half your Android audience taps an App Store link and bounces. You lose traffic to whichever store you didn't pick. Having two separate buttons ("iPhone" and "Android") shifts the problem onto your users, and a meaningful fraction of them will tap the wrong one. UTM parameters don't survive the store handoff. On web, UTMs work because the destination is a browser page that can read the query string. On mobile, the destination is the App Store or Play Store. Neither store passes UTMs into your app when the user finally installs it. So even if you add ?utm_source=tiktok to your URL, your app has no way to know the user came from TikTok. There's more detail in why UTM parameters don't work for app installs. Clicks aren't installs. App Store Connect and Google Play Console both show you install counts. Neither tells you which link produced which install. A visitor can tap your link, browse the App Store for two minutes, install, and you have no way to trace that install back to the specific link they came from.

The point of per-link install tracking is to fix all three at once.

The seven ways to track app installs with links

Each of these is a specific use case. The underlying mechanic is the same — unique link per source, SDK inside the app, reporting in a dashboard — but the setup and reporting differ depending on where the links live.

1. Creator and influencer partnerships

You give each creator their own tracking link. They drop it in their TikTok bio, YouTube description, or Instagram Stories. You see installs per creator, not a lump sum across your whole campaign.

This is usually the first use case indie devs reach for. It settles the "which creator actually drove signups?" question and makes it obvious who to work with again.

Full walkthrough: how to track creator app installs.

2. Link-in-bio tracking

Your bio link — the one URL at the top of every profile — is usually your highest-intent traffic. Users already know you, already watched your content, and are one tap away from installing.

Generic tools like Linktree weren't built for this. They can't route iOS users to the App Store and Android users to Google Play from the same button. They don't track installs, only clicks. And they don't give you revenue per source.

Setting up a proper app bio link solves all three. One URL that routes by platform, tracks installs, and shows you revenue per traffic source. Deep dive: link in bio for mobile apps.

3. Email campaigns

Drop a unique link in each newsletter send. See which subject lines actually drove installs, not just opens and clicks.

Most email platforms track clicks inside their own dashboard — that's where the funnel usually stops. Extending that funnel all the way through install and subscription revenue is what turns email into a measurable growth channel.

Walkthrough: how to track app installs from email.

4. Website and blog referrals

Every time your marketing site, product page, or blog has a "Download" button, that's a link. Make it a tracked link. You can then see exactly how your landing pages are converting visitors into installs.

If you run multiple blog posts or multiple landing pages, give each one its own link. You find out which content moves product, not just which content ranks.

More: how to track app installs from your website.

5. UGC campaigns

Paying creators per install rather than a flat fee? You need a unique link per participant and per-install reporting so the payout math checks out.

This is where most indie devs give up, because running a UGC program without link-level tracking is a guessing game. With per-link install data, the accounting is straightforward. Full guide: UGC app install tracking.

6. One link for both app stores

The smallest, highest-ROI change most devs can make is replacing their raw store links with a single URL that routes by device. iOS users land on the App Store. Android users land on Google Play. Desktop visitors see a clean download page. Every visit tracked.

How it works: one link for App Store and Google Play.

7. Branded download page

For bio links, press coverage, QR codes on posters, and anywhere else a desktop visitor might land, you need a page that looks like you. Not a generic redirect, not a third-party placeholder. A download page with your logo, your screenshots, your tone.

A branded download page turns desktop traffic into phone installs (via QR code) and reinforces your brand in the places your paid and organic reach touches. More: branded download page for apps.

How to pick the right method

You don't need all seven. Most indie devs start with one or two:

• If creators are your main channel: start with per-creator links and the branded download page.
• If you promote mostly on Instagram or TikTok: link-in-bio + platform routing covers 90% of the leak.
• If you run email newsletters: add email campaign tracking next.
• If you're running paid UGC: per-participant links are non-negotiable.
• If your site drives signups: replace raw store links with a tracked redirect.

The right sequence is: fix the biggest leak first, then add tracking to the next-biggest channel. You don't need comprehensive coverage on day one. You need one honest signal per channel, in rank order of how much traffic that channel produces.

How setup actually works

Three components, and none of them take long:

1. Create tracking links. Inside Instally (or a comparable tool), you make a link for each source. Give it a name you'll recognize later — tiktok-april, creator-alexfit, newsletter-week-14. 2. Add the SDK to your app. One line of code during app launch. iOS (Swift), Android (Kotlin), Flutter, and React Native are all supported. The SDK reports install events back to your dashboard. 3. Share the links. Drop them in bios, emails, campaigns. From that point on, every click and every install lands in your dashboard with the source link attached.

That's it. No ad network credentials, no SKAdNetwork configuration, no ATT prompt, no IDFA. Indie-friendly by design.

Platform-specific setup guides: iOS, Android, Flutter.

What you see in the dashboard

Per link:

• Clicks — how many people tapped the link.
• Installs — how many of those clicks led to a completed install.
• Conversion rate — installs divided by clicks.
• Revenue — subscription or IAP revenue from users who came through that link (via your RevenueCat, Stripe, Superwall, or Adapty integration).
• Geography and device — where and on what device the installs happened.

The interesting view is the ranked list. Sort your links by installs, then by revenue, and the picture of your actual growth channels falls out immediately. In almost every case, a small number of links drive the majority of installs, and you had no way to know which ones before.

When tracking installs with links is the wrong approach

A few cases where per-link tracking isn't enough on its own:

• You spend serious money on paid ad networks. If you're running $10K+/month on Meta, Google, or TikTok Ads, you need an MMP like AppsFlyer or Adjust for SKAdNetwork support, fraud detection, and ad-network attribution. More: how to track app installs without an MMP.
• You need deferred deep linking into specific in-app content. If a user clicks a link to a specific article in your app and must land on that article after installing, a deep-linking specialist like Branch is a better fit.
• You need enterprise compliance. SOC 2, data residency, role-based access control — these are enterprise-tier features that indie-focused tools usually don't carry.

For the 90% of indie apps that grow through organic, creator, and content channels, link-level install tracking is the highest-leverage measurement you can add. The fancy stuff only matters if you're paying for it in ad spend.

FAQ

Does this work without IDFA or the ATT prompt? Yes. Install tracking via links doesn't require IDFA and doesn't trigger the iOS ATT prompt. Users see no consent dialog. Is it legal and privacy-safe? Yes. No advertising identifiers are collected. The approach is compliant with App Store, Play Store, and GDPR expectations. How fast can I set this up? About five minutes. Install the SDK, generate your first link, paste it wherever you'd normally paste an App Store link. Do I need to replace my existing App Store and Play Store listings? No. Your store listings stay as they are. Tracking links sit in front of the stores and redirect to the right one. Can I use this with paid ads? You can, but it's not the primary use case. For scaled paid user acquisition across multiple ad networks, an MMP is still the right tool. For organic and creator traffic, per-link tracking is the better fit. What does it cost? Free tier covers 1 app, 1 link, and 1,000 installs a month. Growth ($40/mo) covers 3 apps, unlimited links, 25,000 installs, and revenue tracking. Scale ($79/mo) adds creator dashboards and automatic payouts. See pricing for the full breakdown. Can I give creators their own dashboard? Yes, on the Scale tier. Each creator or promoter gets a login, sees only their links, and gets paid automatically via Stripe Connect.

Start tracking

The short version: create a link, paste the SDK snippet, share the link. Every install you produce from that point on is traceable back to the source that drove it. No guessing, no attribution warfare, no $500/mo contracts.

If you want to see the dashboard and the SDKs in practice, start a free account. Free forever at low volume, five minutes to set up.