Organic vs paid installs

What is an organic install?

An organic install is an install that an attribution system cannot connect to any qualifying ad or tracked link inside an attribution window. In most MMPs, that is the full definition: no eligible touchpoint, so the install is organic.

A paid install is the opposite. Some campaign, whether an ad, an influencer link or a QR code on a tracked link, had a click or view in time, and it gets the credit.

Why is organic a residual and not a channel?

Because nothing reports organic installs as organic; the MMP simply finds no touchpoint and assigns the install to the leftover bucket. Every tracking failure therefore increases organic, without any warning.

Paid channels each send their own evidence: clicks, impressions, SAN claims. Organic has no evidence of its own. It is defined by absence, which makes it the least trustworthy number in the report unless the tracking around it is complete.

The broad shape of the calculation:

If one of the paid lines is under-counted, the organic line grows by exactly the same amount.

What counts as organic in practice

Installs usually labelled organic include:

• people who found the app by searching the App Store or Google Play without an ad;
• people who heard about it from friends or the press and searched by name;
• installs from untracked links, such as a plain store link in a newsletter;
• installs where the ad touchpoint fell outside the attribution window;
• installs where tracking broke somewhere along the chain.

Only the first two are organic in the sense marketers usually mean. The rest are tracking gaps that look like organic.

Common leaks into organic

These are the most frequent reasons paid installs end up in the organic bucket. Several are platform-stated, and the rest are general practice.

Integration and setup leaks

• SAN not connected: if Meta, Google or TikTok is not connected to the MMP, their claims never arrive, and those installs fall to organic.
• Untracked links: campaigns that use a raw store URL instead of a tracking link leave no click to match.
• Missing parameters: tracking links without campaign or network values cannot be credited properly.

Platform and privacy leaks

• iOS tracking denied: when someone declines tracking permission, the IDFA returns all zeros. Installs from ad networks that rely on it may show as unattributed at user level, even though Apple's aggregated reports count them.
• No Play referrer: installs from third-party Android stores, or sideloaded APKs, have no Google Play Install Referrer.
• Referrer stripped: redirects that drop the referrer value on the way to Google Play break deterministic matching.

Timing leaks

• Outside the window: an install after the click window ends is organic by definition. Short windows push more installs into organic.
• SDK starting late: if the SDK reads the install signal after a login screen or a crash, the first open may be lost or delayed.

A worked example

A food delivery app sees organic installs rise from about 30% to about 45% of the total in a week when it also launched a large influencer push. Paid installs from tracked channels stayed flat.

The team checks the leaks in order:

1. Integrations are all connected.
2. The influencer posts used a plain store link rather than tracked links, so none of those installs could be credited.
3. After switching to tracked links, the influencer installs appear as their own source and organic returns towards its earlier share.

The influencer campaign was working all along. The measurement setup was simply filing its results under organic.

Making organic more meaningful

The more of your real acquisition you track, the more organic means what you want it to mean. General practice:

• Use tracked links for every channel you control, including email, SMS, WhatsApp, QR codes, partners and influencers.
• Connect every SAN you spend on, and check the connection after any account change.
• Start the SDK on first launch and confirm it reads the install referrer then.
• Keep windows stable so organic share is comparable week to week.
• Watch organic share as a trend, not a single number.

Tracking non-paid channels matters as much as tracking ads. In an MMP such as Linkrunner, for example, links for QR codes, WhatsApp, SMS and influencers are tracked alongside paid networks, so those installs get their own row rather than joining organic.

How should you report organic installs?

Report organic as a share of total installs over time, next to a note of any tracking changes in the same period. A single week's organic figure says little on its own; the trend and the reasons behind each jump say a lot.

A simple weekly view that works for most teams:

• total installs from the SDK;
• installs per tracked source, including non-paid links;
• organic as the remainder, and as a percentage of the total;
• a short change log: integrations added or removed, app releases, new link types, window changes.

When organic moves by more than a few percentage points, the change log is the first place to look. If nothing changed in tracking, the movement is more likely to be real demand, such as store featuring, press coverage or a seasonal peak.

It also helps to split organic by platform. Because iOS user-level matching depends on tracking permission, iOS organic tends to include installs that Apple's aggregated reports would credit to a campaign. Reading iOS and Android organic separately stops one platform's privacy rules from distorting the overall picture.

Organic uplift and halo effects

Paid ads can lift organic installs indirectly. Someone sees an ad, does not tap it, then searches for the app by name days later. If the view falls outside the view window, the install is organic, even though the ad played a part.

There is no exact way to measure this at the level of one user. Teams usually look at organic trends when paid spend changes. If organic falls when spend is paused, part of that organic was being driven by ads.

For more on windows, see attribution windows. For how iOS privacy rules affect what can be matched, see iOS ATT and SKAN. Every term used here is in the glossary.