App retargeting campaigns that bring users back (and prove they worked)

Retargeting looks great in attribution reports because it targets people already likely to return. Here's how to build audiences, deep link properly and measure real lift.

App retargeting campaigns pay to bring back people who already installed your app. Done well, they reactivate lapsed users and push trial users to pay at a lower cost than finding new ones. Done badly, they mostly buy credit for users who were coming back anyway. The difference comes down to four things: the audiences you build, the deep links behind each ad, how often people see you, and whether you measure incremental lift instead of attributed conversions.

This guide covers each of those, plus the platform rules that limit what you can do on iOS.

When app retargeting campaigns make sense (and when they don't)

Retargeting, also called re-engagement, works best when you have a large installed base and a clear action you want lapsed users to take: finish a purchase, renew, book again, return to a game. It is usually a poor fit when:

• Your user base is small. Audiences shrink fast once you segment them, and some platforms set minimums. Google, for example, says App campaigns for engagement need a base of at least 250,000 installs to be eligible (see Google's eligibility requirements).
• Your owned channels aren't working yet. Push notifications, email and in-app messages reach the same people for close to nothing. Fix those before paying to reach users you already have contact details for.
• The product is why people left. If users churn because of a missing feature or a bad onboarding flow, ads bring them back to the same problem.

Build re-engagement audiences around intent

"Everyone who installed" is not an audience. Segment by what the user did last and how long ago, then match a message to each segment. A starting set:

Two rules make audiences work. First, always exclude users who converted recently, so you stop paying the moment someone comes back. Second, set membership durations that match the buying cycle. A food delivery app might retarget a lapsed user after a week; a tax app might wait a year.

Deep links are not optional

A retargeting ad that opens the app's home screen wastes most of its value. The click should land the user exactly where the ad promised. You need:

• Universal Links (iOS) and App Links (Android) so a link opens the app directly when installed, and falls back to the web or store when it isn't.
• Deferred deep linking, usually via your MMP, for users who uninstalled: they reinstall and still land on the right screen.
• Parameters for personalization, such as product ID, plan or offer code, read by the app on open.
• Login handling, so a logged-out user returns to the intended screen after signing in instead of losing the context.

Test every link on real devices, with the app installed, uninstalled and logged out, before the campaign goes live. Broken deep links are the most common reason a retargeting test "doesn't work". Our comparison of AppsFlyer, Adjust and Branch covers how each handles deep linking.

Where to run retargeting, and the iOS caveat

The main paid options are:

• Google App campaigns for engagement, which serve across Search, YouTube, Display and Play. Google requires conversion tracking through Firebase or an attribution partner and deep links, and recommends running them in a separate account from install campaigns.
• Meta app ads with custom audiences built from app events, aimed at people who used your app, with a deep link destination.
• Programmatic retargeting networks, which buy in-app inventory across many apps using device or hashed IDs. They can scale, but need the strictest fraud and incrementality checks.

On iOS, retargeting runs into App Tracking Transparency. Apple's own examples of tracking include sharing a list of emails or advertising IDs with an ad network that uses it to retarget users in other developers' apps, and that requires the user's permission through ATT. Using a hashed email instead of the IDFA doesn't get around it, according to Apple's user privacy and data use guidance. In practice, iOS retargeting audiences are limited to users who opted in, so expect most re-engagement scale to come from Android and owned channels.

Frequency, timing and creative

People who installed your app are a small, finite audience. Hitting them too often burns the audience and annoys your customers. Practical guardrails:

• Cap frequency where the platform allows, and watch frequency reports weekly. Rising frequency with flat conversions means the segment is saturated.
• Front-load the first days. Intent decays fast after cart abandonment or trial expiry. Spend more in the first few days of a segment's window and less after.
• Write for people who know you. Skip the explainer. Show the specific item, the new feature or what they left unfinished.
• Coordinate with CRM. If a user gets a push, an email and three ads on the same day, you've overspent. Stagger paid touches after owned ones.
• Refresh often. Small audiences see the same creative many times, so fatigue arrives sooner than in acquisition campaigns.

Measure incrementality, not attributed conversions

This is where most retargeting programs fool themselves. Attribution gives the campaign credit when a user clicks or views an ad and then converts. But many of those users were already on their way back. Retargeting tends to look great in last-touch reports because it targets your most likely converters.

The fix is a holdout test. A simple version:

1. Pick one segment, for example users lapsed 14–30 days.
2. Split it randomly into a test group (gets ads) and a control group (excluded from ads). An 80/20 or 90/10 split keeps most of the audience in market.
3. Run for a full cycle, typically two to four weeks, without changing the setup.
4. Compare conversion rates between groups, using your own backend data, not ad platform reports.
5. Calculate incremental cost per action: spend divided by (test conversions minus the conversions you'd expect from the control rate).

If the test group barely beats the control, the campaign is mostly buying credit. Google and Meta also offer conversion lift studies for eligible accounts, and geo-split tests work when audiences are too small to hold out cleanly.

KPIs and budget for a retargeting program

Track these per segment, weekly:

• Reactivation rate: share of the targeted segment that returned and completed the goal action.
• Incremental CPA: from your holdout test. This is the number to compare against new-user acquisition costs.
• Incremental revenue or ROAS: for commerce and subscription apps.
• Retention after reactivation: did they stay for 7 and 30 days, or bounce again?
• Frequency and audience size: to spot saturation early.

Start with a small share of your paid budget on one or two high-intent segments, prove lift, then expand. For overall budget splits between acquisition and re-engagement, see our guide to the app marketing budget.

Common retargeting mistakes

• Retargeting yesterday's active users. If someone opened the app today, an ad tonight is wasted money. Set a minimum inactivity window.
• One campaign for every segment. Mixing cart abandoners with year-old lapsed users blends very different conversion rates and hides what works.
• Discounting by default. Offers train users to wait for a deal. Test a no-offer message first.
• Judging success in the ad platform. Platform-reported conversions include users who would have returned anyway. Use your holdout results.

Getting help with re-engagement

Appryze's founder has spent over 12 years running growth and user acquisition for consumer and fintech apps on Google, Meta and Apple Search Ads. We set up the event tracking, deep links and holdout tests first, then scale only the segments that show real lift. Read more on our Growth page, or see how retargeting fits into app install campaign optimization.

Frequently asked questions

What is app retargeting?

App retargeting, or re-engagement, means showing ads to people who already installed your app to bring them back for a specific action, such as finishing a purchase, starting a subscription or returning after a period of inactivity. The ads should deep link straight to the relevant screen in the app.

Do app retargeting campaigns work on iOS?

Only partly. Apple treats using data from other companies' apps or sharing ID or email lists with ad networks for retargeting as tracking, which requires the user's permission through App Tracking Transparency. That limits iOS retargeting audiences to users who opted in, so many apps rely more on Android and owned channels like push and email.

How do you measure the incrementality of retargeting?

Run a holdout test. Randomly split a segment into a group that sees ads and a control group that doesn't, run the campaign for a full cycle, and compare conversion rates using your own backend data. The difference between the groups is the real lift, and spend divided by the extra conversions gives your incremental cost per action.

What is the minimum audience for Google App campaigns for engagement?

Google's eligibility guidance says advertisers need a base of at least 250,000 installs for App campaigns for engagement, along with conversion tracking through Firebase or an attribution partner and deep links. Requirements can change, so check the current Google Ads help page before planning a campaign.

How often should retargeting ads be shown?

There's no universal number. Concentrate spend in the first days after a high-intent event like cart abandonment, cap frequency where the platform allows, and watch weekly frequency against conversions. When frequency keeps rising while conversions stay flat, the segment is saturated and you should cut spend or refresh creative.

Keep reading

More in App Retargeting Campaigns · All app marketing guides