Home / Guides / Why paid D1 retention is lower than organic

Why paid D1 retention is lower than organic

Paid D1 retention below organic is partly normal, as organic users arrive with intent. See the causes, from targeting to measurement errors, and how to check.

Short answer

Some gap between paid and organic Day 1 retention is normal, because organic users usually arrive already looking for the app. The real question is whether your gap is normal or a fault, and you answer it by checking who you bought, what happened after the click, and whether both sides are measured the same way.

What does paid vs organic D1 retention compare?

Paid vs organic Day 1 retention compares the share of each channel's install cohort that came back on the day after install, so it tells you how well each source brings in users who return.

Day 1 retention (classic): the share of a cohort active on exactly Day 1. Day 0 is the install day and does not count as a return.

Organic install: an install with no paid campaign credited to it, such as someone finding the app in the store or hearing about it from a friend.

Is it normal for paid D1 retention to be lower?

Yes, to a degree. Organic users usually arrive with intent, having searched for the app or been told about it, while paid users were interrupted by an ad, so some gap is expected.

The useful question is not "why is there a gap?" but "is this gap normal for us, or a sign that something is broken?" Track the gap over time and by campaign. A steady gap is a feature of the channel; a gap that suddenly widens, or one campaign far below the rest, is worth investigating.

As an illustration, in the sample app on this site, a made-up app, organic classic Day 1 retention is about 43% and paid is about 24%. That is sample data built to show the method, not a benchmark.

Reasons the gap exists

Who you bought

Lower intent. People who see an ad were not looking for the app, so fewer of them come back.
Broad targeting. Wide audiences reach people with little need for the app.
Optimising for installs. A campaign set to optimise for installs finds people who install cheaply, not people who stay. An event further down, such as onboarding complete, usually brings different users.
Incentivised or low-quality placements. Users rewarded for installing often never open the app again.
Creative that over-promises. If the ad shows something the app does not do, users leave on Day 0.
Geo or platform mix. Paid spend may lean towards countries or devices where retention is lower overall.

What happened after the click

A deferred deep link that lands on the home screen instead of the product or offer the ad promised.
A slow first open, often from a heavy first load or a long permissions sequence.
Onboarding friction, such as a forced sign-up before the user sees any value.

Measurement artefacts

Misattributed installs. If paid installs are recorded as organic, or the reverse, both sides are distorted. This guide to paid installs showing as organic covers the usual causes.
Reinstalls counted as new installs, which can push either side up or down.
Different definitions or time zones for the two numbers.
An immature or tiny paid cohort, where a few users swing the rate.
Comparing classic with rolling. Rolling is always at least as high as classic, so a rolling organic figure against a classic paid one inflates the gap.

Fraud

Fake installs from bots or install farms rarely come back, so fraud shows up as very low retention on specific sources or sub-publishers.

How to check what is going wrong

Work through these in order. The first three rule out false alarms before you change any campaigns.

Use the same definition and day boundary. Both numbers should be classic Day 1, in the same time zone, from the same cohort dates. The retention types page explains why mixing definitions breaks the comparison.
Check the cohort size. If the paid cohort is small, read it as directional and pool more days before acting.
Check attribution. Confirm that installs are landing in the right channel, and that reinstalls are handled the same way on both sides.
Split by campaign and creative. A blended paid number often hides one bad campaign. The channels section of the reading guide shows how to lay this out.
Check Day 0 onboarding completion by channel. If paid users drop out before finishing onboarding, the problem is the first session, not Day 1.
Compare cumulative Day 3 as well. If paid users come back at least once within three days at a closer rate to organic, they are returning, just not on exactly Day 1.

If you need to calculate these yourself, the formulas page has SQL and spreadsheet versions for all three definitions. For more on splitting a cohort table, see retention by channel and campaign and this walkthrough on measuring app retention by channel.

Note: Example numbers come from a made-up app to show the method, not a benchmark.

Questions

How big should the gap between paid and organic D1 be?

There is no universal number, because it depends on the app, the channels and the targeting. Track your own gap over time and by campaign, and investigate when it widens or one campaign stands far apart.

Can paid retention ever be higher than organic?

Yes. A tightly targeted campaign that optimises for a meaningful in-app event can bring users who retain as well as or better than organic. Mislabelled installs can also produce this, so check attribution before celebrating.

Does optimising for a deeper event fix low paid retention?

It often helps, because the ad platform then looks for users who complete that event rather than users who install cheaply. It usually raises the cost per install, so judge it on retained users per unit of spend.

Should I compare paid and organic on rolling retention?

Only if both sides use rolling and the cohorts are the same age. Rolling keeps rising as late returns arrive, so classic is the safer basis for comparing channels.

Could my organic number be wrong rather than paid?

Yes. If paid installs are being recorded as organic, organic retention is pulled down and paid looks better, or the reverse. Checking attribution is part of reading any channel comparison.

What is the difference between classic, rolling and cumulative retention?

Classic counts users active on exactly Day N. Rolling counts users active on Day N or any later day, and cumulative counts users active at least once from Day 1 to Day N. They use the same raw activity but answer different questions.