How to Track Influencer-Driven App Installs

Why cookies and UTM parameters don't work for app installs

The entire existing influencer-tracking toolkit — cookies, click IDs, UTM parameters — assumes there's a browser session to write information into. See how that mechanism works technically for a webshop. An app install has no such foundation: the app isn't installed on the device when the customer clicks the creator's link, so there's no cookie store to write anything into, and an ordinary UTM parameter typically gets stripped the moment the browser hands the customer off to the App Store or Google Play. App-install tracking therefore runs on entirely different infrastructure: a Mobile Measurement Partner (MMP) — the most widely used are AppsFlyer, Adjust, Branch and Singular — generates an attribution link per creator, and an SDK built into the app itself matches the install to the original click the first time the app is opened.

The building blocks of app-install attribution

Four concepts recur across every MMP:

• Attribution link (deep link). A link that opens directly to a specific place inside the app, if the app is already installed on the device.
• Deferred deep link. The same idea for users without the app: the link routes them to the App Store or Google Play, and once the app is opened for the first time, the user is recognised and carried through to the original destination inside the app.
• Media source / creator parameter. The part of the link that identifies which creator or campaign the install should be credited to — the practical app-world counterpart to a UTM parameter; see UTM parameters for influencer campaigns for the web version of the same idea.
• Attribution window. How much time is allowed to pass between the click and the install before the MMP stops trying to match them. Typically shorter than web attribution windows, because an install usually happens the same day as the click; see attribution windows in influencer marketing for how the same concept plays out on web.

From click to attributed install — step by step

1. Share. The creator shares an MMP-generated attribution link in a bio, Story, or video description.
2. Click. The customer clicks. The MMP logs the click and stores the creator parameter along with a timestamp and device data.
3. Redirect. If the customer doesn't have the app, they're sent to the App Store or Google Play (deferred deep link).
4. Install and first open. The customer installs and opens the app. The MMP's SDK inside the app sends device data back to the MMP's server.
5. Matching. The MMP tries to match the install against a previously logged click.
6. Attribution. If there's a match, the install is credited to the right creator, and later in-app events (a purchase, say) can be tied to the same creator.

Step five — the matching — is exactly where iOS and Android diverge sharply, and where most brands are surprised by what they can actually see.

iOS vs Android: two different matching mechanisms

What this actually means for an influencer campaign

On Android, the install count from a creator's link is close to a complete, deterministic count, because the Install Referrer API isn't gated by any consent requirement. On iOS, the picture is different: for an organic (unpaid) creator link, you can only deterministically attribute installs from the share of users who actively granted ATT permission. The remaining installs are just as real, and just as much a result of the creator's content — they simply can't legally be tied to the specific creator, because Apple has, since 2024, prohibited the fingerprinting techniques MMPs previously used as a workaround for the missing IDFA. SKAdNetwork and its successor AdAttributionKit don't solve this either, because they cover only paid ads shown through a registered ad network — not a link a creator puts in their own bio.

Setting this up in practice

1. Choose an MMP (AppsFlyer, Adjust, Branch, Singular, and others) and integrate its SDK into the app — that's a development task, not something an influencer marketing platform can do around the app's own engineering team.
2. Generate one attribution link per creator with a unique media source parameter, the same principle as a unique UTM link on web.
3. Set up deferred deep linking so new users land in the right place inside the app — a welcome screen with a pre-filled campaign offer, say — instead of just the home screen.
4. Pair the link with a redeemable in-app code as a backstop: a code the customer types in after installing can be tracked independently of ATT consent and platform, because it's an action inside the app — not a technical match between a click and an install. Same logic as the code-based half of discount codes vs tracking links on web.
5. Set a realistic attribution window, typically 1-7 days for app installs — much shorter than the 30 days that's standard for a webshop purchase.

Comparison: web tracking vs app-install tracking

Worked example: how much of your app installs can you actually see?

The numbers below are illustrative only, built to demonstrate the mechanism — not a real Make Influence customer case and not a benchmark. The 55/45% iOS/Android split and the 8% install rate are assumptions, not measured figures; the 38% ATT-consent share, by contrast, is taken from Adjust's own published Q1 2026 benchmark.

Assume a creator's attribution link gets 5,000 clicks over a campaign, split 55% iOS (2,750 clicks) and 45% Android (2,250 clicks), and that 8% of clicks genuinely lead to an install on both platforms.

Android: 2,250 clicks × 8% = 180 installs. Because the Install Referrer API needs no consent, effectively all 180 are matched to the creator's link.

iOS: 2,750 clicks × 8% = 220 genuine installs. Only the roughly 38% who granted ATT permission can be matched deterministically: 220 × 38% ≈ 84 installs. The remaining 220 − 84 = 136 installs are just as real — they genuinely happened via the creator's link — but show up in the MMP dashboard as organic or unknown, because there's no legal way to tie them back to that specific creator.

Total: The campaign generates 180 + 220 = 400 genuine installs. The brand can see and attribute 180 + 84 = 264 of them to the creator — 66%. The last 136 (34%) are invisible to per-creator attribution purely because of iOS's consent requirement, not because tracking technically failed.

Decision framework

• IF your app's user base is mostly iOS → expect only around a third of installs to be deterministically attributable to the individual creator, and build a redeemable code in as a backup from the start.
• IF your app's user base is mostly Android → the Install Referrer API gives you effectively full visibility with no extra work.
• IF you're running the campaign as paid ads through Meta or TikTok Ads (not organic creator posts) → SKAdNetwork/AdAttributionKit is relevant, but it's a different system from the one that covers an organic link in a creator's bio.
• IF you're only working with a handful of creators on the app → a manually tracked, redeemable code can often be enough, without needing a full MMP integration.

Common mistakes

• Assuming an ordinary UTM link works for app installs. The parameters typically get stripped the moment the browser hands the customer off to the App Store or Google Play — it takes an MMP-generated link.
• Reading a drop in attributed iOS installs as a drop in real installs. It could just as easily be a drop in ATT consent, not in the creator's effect.
• Using SKAdNetwork terminology for an organic creator link. SKAdNetwork and AdAttributionKit only cover paid ads through registered ad networks.
• Skipping a redeemable code as a backstop. Without one, a large share of your iOS installs are structurally invisible to per-creator attribution, regardless of which MMP you choose.

Getting the technical tracking right is necessary but not sufficient — it only tells you whether an install can be attributed, not whether the attribution link or QR code actually gets used in the first place. See influencer marketing for app installs: creative strategy, not just tracking for the brief and content-format side of the problem — launch bursts vs evergreen programs, link/QR placement, and how to test creative systematically.

Make Influence's operational perspective

Make Influence's own tracking model — a tracking cookie for up to 30 days plus IP fallback for up to 3 months, see how it works technically — is built for webshop purchases, not native app installs. If a brand's growth goal is an app install rather than a webshop purchase, a dedicated MMP integration is the right tool, and that's a different job from the one Make Influence's own tracking solves. That's not a weakness in either — they're two different technical problems that each need their own solution.

FAQ

Can I use an ordinary UTM link to track app installs?

No. UTM parameters typically get stripped when the browser hands the customer off to the App Store or Google Play. You need an attribution link generated by an MMP, built specifically to survive that handoff.

Does this mean I can't see how many people install the app via a specific creator on iOS at all?

You can see the overall install trend for the whole app in App Store Connect, but attributing each individual install to one specific creator is only reliable for users who granted ATT consent — unless you pair the link with a redeemable in-app code.

What's the difference between a deep link and a deferred deep link?

A deep link only works if the app is already installed, and points straight to a specific place inside it. A deferred deep link also works for users without the app: they're sent to the App Store/Google Play, and after installing, they're carried through to that same destination.

Do I need an MMP if I'm only working with a couple of creators on my app?

Not necessarily. At low volume, a manually tracked, redeemable in-app code is often enough. A full MMP integration pays off most once you're running several creators and campaigns at once and need automated reporting.

Does the ATT consent requirement only apply to paid ads, or organic creator posts too?

ATT governs access to IDFA and other device signals broadly — not just paid ads. What is ad-specific is SKAdNetwork/AdAttributionKit, Apple's own aggregated fallback system, but that covers only installs from ads shown through a registered ad network, not an organic link in a creator's bio.