Email marketing for mobile apps: onboarding and retention

Mobile apps have push notifications, in-app messages, and stories baked right into the interface. So why bother with email? Because 77% of users delete an app within three days of installing it. A push never reaches someone who already uninstalled. In-app messaging is invisible to anyone who never opens the app. Email is the only channel that works outside the app itself, regardless of whether it is still on the user's phone.

Why mobile apps still need email

Push is fast but fragile. According to Airship, the average opt-in rate for push notifications is around 49% on Android and 36% on iOS. That means you cannot reach half to two-thirds of your audience through push at all. Even among users who did allow notifications, one annoying push is often enough for them to disable the entire channel.

Email works differently. It does not disappear after a swipe. It sits in the inbox until the person decides to open it. It can carry long text, screenshots, tables, and deep links, none of which fit into a 120-character push notification. Most importantly, email reaches a user even if they deleted your app two months ago. Push is useless in that scenario. In-app messaging even more so.

There is a less obvious reason too. Email is an owned channel. Push goes through Firebase or APNs; the platform decides whether to deliver the notification and how to display it. The App Store can change its rules overnight and break your push channel. Your email list belongs to you. It is an asset that survives iOS updates.

Collecting email: timing and context

The classic mistake is demanding an email address at registration, before the user understands what the app is for. Someone downloads from the App Store, opens it, sees "enter your email to register," and closes it. Or types a junk address to skip past the screen faster. Localytics data shows 21% of users open an app exactly once. If registration is your only shot at collecting email, one in five addresses will be invalid or disposable.

A better approach: delayed collection. Let the user try the product without registering (guest mode, limited features), then ask for an email once they have seen real value. A fitness app can ask after the first workout. A finance tracker after the first spending report. A delivery service after the first completed order. At that point the user has a reason to give a real address, and the share of throwaway inboxes drops.

Even with that approach, some addresses will still be invalid. Typos on a mobile keyboard are their own problem: gmial.com, yandx.ru, two spaces instead of a dot. Real-time validation through an API catches these errors before the address enters your database. Without validation, your onboarding sequence fires into the void, bounce rate climbs, and you do not even know half your welcome emails never arrived.

Onboarding: the first seven days

Mobile app onboarding is different from SaaS or e-commerce. The user is on a phone. Sessions are short, the screen is small, and ten other apps are competing for attention. Your email sequence needs to account for that context.

Email 1 (immediately after registration). Keep it short. One specific action. Not "explore all features" but "set up your profile in 30 seconds" or "add your first goal." A button with a deep link that opens the app on the right screen. If the app is not installed, the deep link should route to the store. This is a basic scenario many teams skip.

Email 2 (day 2, if the key action has not been completed). A reminder that explains the value. Why the first step is worth taking. A short data point: "Users who set up their profile on day one are 3x more likely to still be active a week later." A fact, not a plea.

Email 3 (day 3-4). The app's second value prop. The user knows the main feature by now. Show them the next one: an integration, a widget, a feature most people miss. Again, a deep link straight to that screen.

Email 4 (day 5-7). Social proof. A real user testimonial. Stats: "200,000 people use the app every day." If you have behavioral data for this specific user, use it: "You completed 3 workouts this week. Four more and you will start seeing the results."

The rule across all four: one deep link, one action, under 40 seconds to read. Mobile users check email between tasks. Nobody reads a five-step tutorial standing on the subway.

A deep link is the bridge between email and app. An email without a deep link is a billboard without an address: the person saw it, got interested, and has no idea where to go next.

Deep links: the technical layer that drives conversion

A deep link in email is not just a link to your app. It is a link to a specific screen inside the app. The difference matters. A regular link opens the home screen and forces the user to navigate to the right section. A deep link opens exactly what the email described: a promotion page, a settings screen, an incomplete action.

According to Branch.io, emails with deep links show roughly 2x the CTR of emails with plain links. The reason is friction: the user does not have to search. They land exactly where they were invited.

The technical implementation depends on the platform. Universal Links on iOS, App Links on Android, deferred deep links for cases where the app is not installed. That last scenario matters most for reactivation: the user deleted the app, received an email, tapped the link. A deferred deep link routes them to the store first, then opens the right screen after install. Without it, they install and land on a login screen instead of the content that caught their attention. Conversion dies on the last step.

One common mistake: testing deep links only on your own device. Links behave differently in Gmail, Outlook, Apple Mail, and other clients. Some wrap links in their own redirect layer, which breaks Universal Links. Test on real devices, in real email clients, on both platforms.

Push vs email: not competition, but orchestration

Asking "push or email?" is the wrong question. Each channel handles a different job, and neither substitutes for the other.

Push fits urgent, short signals: "Your order was delivered," "EUR just moved 3%," "A friend joined your challenge." These messages are time-sensitive. Two hours later they are irrelevant.

Email fits substantive messages worth reading later: a weekly summary, a curated set of recommendations, an explanation of a new feature, personal results for the month. This content holds value a day or a week after it was sent.

A well-designed strategy uses both in sequence. User inactive for 3 days? Start with a push. No response within 24 hours? Send an email with more context and a deep link. Still nothing after a week? A second email, different angle. That is sequential escalation, not blasting every channel at once.

The most common mistake: sending the same message through push and email simultaneously. The user receives two notifications about the same thing, feels pressured, and disables both channels. If a push was delivered and opened, skip the email. Customer.io, Braze, and Iterable all support this natively: a rule that suppresses the email if the push was opened within N hours.

Retention: winning back users who drifted

The average day-30 retention rate for a mobile app is around 6% (Adjust data). That means 94 of every 100 users stop using the app within a month. The number looks grim, but it includes everyone who downloaded accidentally and never intended to stay. Still, for email marketers, retention is the main arena. Acquisition belongs to performance marketing and ASO. Keeping users and bringing them back is where email sequences earn their keep.

Inactivity trigger. User has not opened the app in 7 days. First email: what happened since they left. Not "we miss you" (a cliche that moves nobody) but something concrete: a new feature, content they skipped, their friends' activity in the app. Deep link to the screen with that content.

14 days without activity. More direct. Personal stats: "Last month you ran 42 km. This month you are at zero." Or an offer to help: "Something not working? Write us, we will sort it in 5 minutes." A specific question lands better than "we would love to see you again."

30 days without activity. The last email before the address moves to the dormant segment. An incentive is reasonable here: a discount on premium, a free period extension, exclusive content. If this email is also ignored, further attempts are more likely to hurt sender reputation than recover the user.

Seasonal reactivation. Fitness apps see spikes in January and September. Finance apps get attention at the start of each quarter. Education apps pick up in September. Every app category has moments when user motivation is naturally higher. Reactivation campaigns timed to those windows perform 2-3x better than the same emails sent at a random date.

Email design for a mobile audience

If your app is mobile, your emails get read on phones. Litmus data puts 43% of all email opens on mobile. For a mobile app's audience the number is closer to 70-80%.

Practical rules. Email width: no more than 600 px, but everything must adapt down to 320. CTA button: at least 44x44 px, positioned above the fold. Body font: minimum 16 px. Images: keep them light because emails over 100 KB get clipped in Gmail. Preheader: actual sentence, not "Email not displaying correctly? View in browser."

Dark mode deserves its own attention. Over 80% of iOS users enable dark mode. If your logo is black text on a transparent background, dark mode makes it invisible. Test every email in both modes. Use prefers-color-scheme in CSS where client support allows it.

List hygiene: specific issues for mobile apps

Mobile apps collect emails under conditions that invite errors. Small keyboard, autocorrect, time pressure. The user is registering between subway stops. As a result, the share of invalid addresses in a mobile app's database tends to run higher than in a web product.

Disposable email services add a second layer. Mobile users reach for temp inboxes more often than desktop users, usually to unlock content without committing. That address is useless: within 24 hours the inbox stops existing, and your email hits a hard bounce.

The fix is two-stage validation. Stage one: real-time check at registration. An API call taking 200-300 ms, while the user is still on the input screen. It checks syntax, domain existence, MX records, and flags disposable services. If the address is invalid, the user sees a prompt and corrects it on the spot.

Stage two: periodic validation of the full list. Monthly for active apps, quarterly for others. Inboxes degrade: users switch providers, services shut down, mailboxes fill up and stop accepting mail. Regular validation removes those addresses before they damage your domain reputation.

Metrics worth tracking

• Deep link click-to-open rate. What share of recipients tapped the deep link into the app after opening the email. High open rate with low deep-link click rate points to a technical problem with the links.
• Reinstall rate from email. How many users reinstalled the app after an email campaign. Measure it through deferred deep links with UTM parameters.
• Day-7 retention by cohort. Compare retention for users who received the onboarding sequence against those who did not. The gap shows email's actual contribution.
• Bounce rate by acquisition source. TikTok ad traffic can produce very different address quality than organic search. Use that to apply stricter validation on channels that consistently generate bad addresses.
• Unsubscribe rate by email type. Onboarding should stay below 0.5%. Retention emails below 1%. Reactivation up to 2% is acceptable. Higher numbers mean the content is not matching expectations.

Checklist for mobile app email marketing

• Add real-time email validation at registration. Block disposable inboxes and typos at the point of entry.
• Build an onboarding sequence of 4-5 emails, each with a deep link to a specific app screen.
• Implement deferred deep links for the "app not installed" scenario.
• Keep push and email separate: do not duplicate messages, use channel suppression.
• Set inactivity triggers at 7, 14, and 30 days, with three distinct emails that get progressively more direct.
• Test emails on mobile devices in dark mode.
• Run the full list through a validator monthly. Remove addresses that have degraded.

Email for a mobile app is neither a secondary channel nor a push replacement. It is a separate tool with its own rules: deep links instead of plain URLs, short emails instead of long reads, event-driven logic instead of calendar blasts. And like any tool, it only works on clean data. Invalid addresses in a mobile app database are not an abstract hygiene problem. They are specific users you cannot reach once they uninstall and push can no longer find them.