Guide · 8 min read
App Redownload Strategy: Win Back Users Who Deleted Your App (2026)
Most indie developers have never opened the Redownloads row in App Store Connect Analytics — which means they're optimizing acquisition while ignoring the channel where 92% of iOS users are already active. Redownloads account for roughly 69% of App Store downloads and, according to Apple's own ad platform data, returning users convert at 3× the revenue rate of cold installs. Here is what to do with that number: the listing updates, push sequences, and ad targeting that turn former users into second-chance customers.
Redownloads account for 69% of App Store volume — most apps manage this channel at zero
Redownloads account for approximately 69% of App Store download volume. This means the majority of growth in a mature app isn't new users — it's former users cycling back. Most indie developers allocate every dollar and hour of ASO work to acquiring users who've never heard of the app, while the returning-user channel runs on autopilot.
App Store Connect Analytics has a dedicated Redownloads metric under the Units tab. Navigate to App Store Connect → Analytics → App Analytics → Units, change the metric dropdown to 'Redownloads,' and apply the Source Type dimension. Most developers see this number for the first time and realize their 'growth problem' is actually a 'win-back problem.' The guide on App Store Connect Analytics metrics covers the full metric set and which signals to act on first.
Apple counts redownloads as conversions for ranking purposes — which explains why navigation, reference, and weather apps sometimes report conversion rates above 100% in certain periods. Returning users install without always viewing the product page, and Apple credits the listing anyway. Your current CVR data is already partly driven by redownloads you haven't deliberately optimized. That means a small improvement in win-back rate compounds on a signal Apple is already measuring.
Update your listing to say "we fixed it" — the cheapest passive redownload signal
Your App Store listing is the first thing a former user encounters when they search your app name after deleting it. A listing unchanged since they left gives them no reason to reinstall. A visibly refreshed listing — updated screenshots, a candid What's New section — signals that whatever drove them away may no longer apply. This is the lowest-cost re-engagement move available, requiring no paid media and no code change.
The 'What's New' section has one job for lapsed users: answering the specific objection that caused deletion. Most apps write it as a changelog ('Bug fixes and performance improvements'). Write it instead as a direct reply to your most common one-star review theme. If negative reviews cite loading speed, the What's New copy should address speed by name. A former user who sees their objection addressed before they've tapped through has already started reconsidering.
Screenshot updates can be pushed to App Store Connect at any time without submitting a new binary. An updated first screenshot that leads with a resolved pain point, a new feature, or a social-proof number changes the redownload calculus for former users encountering your listing via search. Review the App Store screenshot size requirements for every device class before uploading — wrong dimensions are the most common reason a listing update gets rejected at review.
The 3-message push sequence that recovers dormant users before deletion
Users who stop opening an app rarely delete it immediately — there is a 14-to-30-day dormancy window where a targeted push sequence recovers a meaningful share of lapsed users before they delete. Reaching someone while the app is still installed removes all reinstall friction: they tap, they're in. No App Store, no redownload, no fresh onboarding.
The sequence that converts: message one at day 7 of dormancy recaps the core value in specific terms ('You haven't [completed action] in a week — here's what you're missing'); message two at day 14 surfaces something new or improved ('We shipped [feature] since your last session'); message three at day 21, for monetized apps, adds a concrete incentive ('Your account and data are still here — we've extended your trial by 30 days'). Each message names one action and one reason. Three messages is the ceiling — past that, dormant users who haven't re-engaged will delete specifically to stop the notifications.
This entire sequence requires push permission. For apps with sub-30% opt-in rates, the dormancy channel is already limited before a single message sends. The opt-in rate is set at the first session, making the initial push permission request the highest-leverage moment in your entire re-engagement strategy — more so than the push copy itself.
Apple Search Ads Redownloads campaigns: targeting former users with a warmer audience
Apple Search Ads has a dedicated Redownloads campaign objective that shows ads exclusively to users who previously installed your app. Apple's own platform data puts revenue from these returning users at 3× the rate of cold-install campaigns. Most indie developers running Apple Search Ads have only ever activated the Downloads objective and have never touched this audience.
In Apple Search Ads Advanced, create a new campaign and set the goal to 'App redownloads.' Start with broad match keywords — former users searching a competing app name are at the moment of re-evaluation, which is the highest-intent signal in reacquisition. Two weeks of broad match data will surface which search terms your lapsed users are actually querying. Then narrow to exact match on the highest-converting terms. The Apple Search Ads basics guide covers campaign structure and bid strategy for indie-scale budgets.
Budget calibration: $3–5/day in your primary market establishes a cost-per-redownload baseline within two to three weeks. Compare it directly to your Downloads CPI. Redownload CPI typically runs lower because the audience is warmer and bid competition for this specific targeting is thinner. Scale only after confirming the unit economics hold.
Build a Retention Custom Product Page for users who left, not users who never installed
A Custom Product Page built specifically for lapsed users — showing what changed rather than what the app does — converts at a higher rate than the default product page when served through an Apple Ads Redownloads campaign. The default page is designed for first-time persuasion. The retention page is designed for objection reversal. These are different jobs and the same screenshots don't serve both.
Three changes make a Retention CPP distinct from your default: first, screenshot one addresses the most-cited deletion reason, not the hero feature — if users left because onboarding was confusing, frame one shows the simplified current flow; second, the What's New field drops all version numbers and instead lists the three biggest improvements since the app's initial release; third, supporting frames include social proof that postdates the user's original install — review counts, press mentions, or milestone numbers they didn't see when they first tried the app.
Keep the Retention CPP exclusive to your Redownloads campaign — don't assign it to organic search, where it would confuse first-time visitors who haven't seen the default page. Apple allows up to 70 Custom Product Pages per app, and each can be assigned to specific campaigns. The Custom Product Pages organic ranking guide covers when and how to expand CPP usage to free discovery channels once the paid version is proven.
Email re-engagement for users who left account data behind
Users who created an account before deleting can be reached by email after the app is gone from their phone. The highest-converting format is a 'here's what you missed' email sent 30 days after last recorded login. Not a generic 're-engage' campaign — a specific, factual account of what the app became while they were away.
Name the specifics: features shipped, metrics improved, community milestones, content added since their last session. 'Since you were last here, we launched [feature], cut load times by 40%, and 50,000 new users joined' is objectively verifiable and non-manipulative. This format outperforms 'we miss you' copy by the same mechanism that makes specific What's New notes work: former users are skeptical, and concrete facts are more persuasive than sentiment.
Pair the email with a web landing page that mirrors the 'what changed' message and deep-links directly to the App Store listing. A lapsed user who receives the email on a laptop will click through to a web page before installing from a phone — that intermediate page needs to exist and tell a coherent story. The app web preview page guide covers how to structure this page so it also ranks for branded searches by users who deleted the app and later search for it by name.
Reading your Redownloads source breakdown — the data most indie devs never open
The source breakdown inside App Store Connect's Redownloads metric is the most actionable data most indie developers have never examined. In Analytics → App Analytics → Units → Redownloads, apply the Source Type dimension. This splits redownloads into App Store Browse, App Store Search, Apple Search Ads, and Referral — each source tells a different story about where former users are returning from and what's working.
If most redownloads come from 'App Store Search,' former users are searching your app name directly and have already decided to return — the barrier here is remembering the name, not persuasion. If most come from 'Apple Search Ads,' paid campaigns are doing the re-engagement work while your organic listing signals underperform. If 'App Store Browse' leads, Apple's editorial or algorithmic surfaces triggered a wave — often a major version update or an app featuring event. Knowing the source tells you where to invest the next lever.
Check this data monthly, not daily. Redownload signals lag listing updates and campaign changes by two to four weeks because former users encounter your refreshed presence through different touchpoints at different times. Set a recurring calendar item: review Redownloads source breakdown, compare month-over-month, and identify which channel shifted. That's the signal that tells you whether last month's listing update or ad campaign actually moved the needle.
Run one redownload experiment this week before building a system
The highest-ROI starting point is the listing update — rewrite your 'What's New' field to speak directly to the most common reason users left, and refresh the first screenshot to show what changed. This takes under an hour, costs nothing, and starts generating passive redownload signal within two weeks as former users encounter the updated listing through search.
Once the listing is refreshed, open App Store Connect and look at your Redownloads metric for the first time. The number you see is your baseline. Everything else — push sequences, Apple Ads Redownloads campaigns, email re-engagement, Retention CPPs — layers on top of that baseline. Start with one lever, measure it after a month, and add the next.
Refresh your App Store screenshots in the editor →
Frequently asked questions
does apple count redownloads as new installs in app store connect
Apple records redownloads separately from first-time downloads in App Store Connect Analytics. Under the Units tab, 'App Units' shows first-time downloads and 'Redownloads' shows reinstalls by users who previously deleted the app. Both count as conversions for ranking purposes — which is why some apps report conversion rates above 100% in certain periods. Returning users install without always viewing the product page, and Apple credits the listing anyway.
can i target users who deleted my app with apple search ads
Yes. Apple Search Ads Advanced has a 'Redownloads' campaign objective that targets users who previously had your app installed. Create a new campaign, set the goal to 'App redownloads,' and target keywords your former users are likely searching. Revenue from returning users reached through Apple Ads runs at approximately 3× the rate of cold-install campaigns, according to Apple's platform data.
what is the best timing for re-engagement push notifications to dormant users
Day 7 and day 14 of dormancy are the highest-response windows for re-engagement push notifications. Day 7 recaps value in specific terms; day 14 surfaces something new or improved. A third message at day 21 with a concrete incentive works for monetized apps. Cap at three messages — users who haven't re-engaged by then delete the app specifically to stop receiving notifications.
how do i win back users who deleted my app and never created an account
Anonymous users can only be reached through paid re-engagement via Apple Search Ads Redownloads campaigns, or organically when they search your app name and encounter your updated listing. You cannot email or push-notify users who never gave you an identifier. This is the clearest argument for collecting at minimum a push token or email address in the first session — before users decide whether to keep the app — even if the rest of onboarding is gated.
does updating my app store listing help redownloads organically
Yes, in two ways. First, an updated listing changes what former users see when they search your app name — refreshed screenshots and a candid What's New section signal the app has changed since they left. Second, major version updates can trigger Apple's 'Recently Updated' editorial surface in some markets, putting your app back in front of category browsers who previously installed it. Neither is guaranteed, but a listing refresh is the lowest-cost passive re-engagement signal available and takes under an hour to deploy.