Skip to content

FlutterFlow Agency - Expert Flutter & FlutterFlow App Development

user re-engagement

The Re-Engagement Campaign Framework: How Strategic In-App Messages and Push Notifications Revived 25% of Dormant Users

16 min read

The Re-Engagement Campaign Framework: How Strategic In-App Messages and Push Notifications Revived 25% of Dormant Users

The Re-Engagement Campaign Framework: How Strategic In-App Messages and Push Notifications Revived 25% of Dormant Users

A structured user re-engagement campaign that combines behavioral segmentation, timed push notifications, and targeted in-app messaging can revive roughly one in four dormant users. This framework defines dormancy by inactivity windows, splits users into distinct risk segments, and assigns each segment a specific message channel and incentive. The result is a repeatable system for recovering lost users rather than a one-off promotional blast.

Executive Summary

This whitepaper presents a practical, evidence-based framework for re-engaging dormant users through push notifications and in-app messaging. It explains how to define dormancy, segment inactive users by behavior, and match each segment with the right channel and message. The analysis draws on documented re-engagement programs from Pushwoosh, MoEngage, and BelkaCar that collectively demonstrate meaningful recovery rates, including the 25% revival benchmark referenced in the title. The core finding is that user re-engagement succeeds when it is treated as a segmented, timed workflow rather than a single broadcast. Brands that segment by inactivity window and test incentive types see measurable lifts in conversion, click-through rate, and daily active users. This article provides the segmentation criteria, message-mapping logic, testing method, and implementation checklist needed to build that workflow.

Introduction / Background

Mobile apps lose users quietly. A user who does not open an app for a week is unlikely to return without a prompt. The cost of acquiring a new user is generally higher than the cost of reactivating a lapsed one, which is why user re-engagement has become a core growth function rather than an afterthought. The term dormant users refers to people who have installed an app and previously engaged with it but have since stopped opening it for a defined period. User re-engagement is the practice of prompting those users to return through targeted messaging. In-app messaging refers to messages displayed inside the app itself, usually when a user opens it, while push notifications are delivered outside the app to the device's notification tray.

The distinction matters because the two channels reach different moments in the user's life. Push notifications can reach a user who has not opened the app at all. In-app messages only reach users who have already opened it. A complete re-engagement program uses both, assigning each to a different segment. According to Pushwoosh documentation, the users most at risk of churning are typically those who have not opened the app for three to seven days. That window is the practical starting point for any dormancy definition.

The business case is not theoretical. Publishers Clearing House reactivated over 30,000 dormant users and achieved a 3.93% overall conversion rate through a segmented push and in-app messaging program. BelkaCar, one of Russia's largest carsharing companies with more than 2.5 million customers, built inactivity segments of one, three, and six months and reported retention push click-through rates around 17 to 20 percent. These are real programs with published outcomes, and they share a common structure: segment first, then message.

That structure is what this whitepaper formalizes. For teams building or improving an app, the framework here connects directly to broader retention and growth planning. A solid app retention strategy provides the foundation on which re-engagement campaigns operate, and the app growth and optimization guide offers the wider context for measuring whether reactivation programs pay off.

Problem Statement

Most apps address dormancy with a single generic push notification, sent to the entire inactive list, offering a discount or a reminder. This approach fails for three reasons. First, it ignores the difference between a user who left two days ago and one who left six months ago; the first is still forming a habit, while the second has broken it entirely. Second, it uses a channel that cannot reach users who have disabled notifications or muted the app. Third, it treats every dormant user as motivated by the same incentive, when the evidence shows that incentive type matters.

Publishers Clearing House explicitly tested personalization, emojis, tokens, Superprize entries, and weekly grand prize entries through push and in-app messaging, using A/B testing to identify the correct incentive each day. That level of variation is what produced a 3.93% conversion rate across 30,000 reactivated users. A single generic message cannot replicate that result because it does not learn which incentive works.

The second problem is channel mismatch. A dormant user who never opens the app will never see an in-app message. A dormant user who opens the app to check a feature will see a push notification only if it was sent after their last session. The re-engagement problem is therefore a routing problem: deciding which segment receives which message through which channel at which time. Pushwoosh documentation illustrates the routing logic clearly. For users who opened the app within three days, the program shows an in-app message with a button leading to a feedback form, asking why they might abandon the app. That is a different segment and a different purpose from the one-week inactive group. Without explicit routing rules, the messaging collapses into noise.

The third problem is measurement. A campaign that reports open rates without reporting reactivation, conversion, or daily active user lift cannot tell you whether it worked. Publishers Clearing House reported a 58% increase in average in-app click-through rate and a 23% increase in daily active users during its flagship Superprize period. BelkaCar reported click-through rates in the 17 to 20 percent range alongside more than 2.4 million push subscribers and 300,000+ monthly active users. These metrics describe outcomes, not just delivery. A re-engagement program should be judged on the same basis.

Research/Analysis

How Should You Define and Segment Dormant Users?

Dormancy is not a single state. It is a spectrum of disengagement, and the first design decision is where to draw the lines. Pushwoosh documentation recommends identifying users at risk of churning as those who have not opened the app for three to seven days. BelkaCar went further, building inactivity segments at one, three, and six months. The difference reflects app type: a daily-use app may consider a week of silence a serious risk, while a carsharing service with occasional use can afford a longer window.

A practical segmentation model uses four bands. The first band covers users inactive for three to seven days. These users are still in the habit-formation phase and respond best to gentle, feature-focused nudges. The second band covers eight to thirty days; here the habit has weakened, and the message needs a stronger reason to return. The third band covers one to three months, where the user has likely formed new routines. The fourth band covers more than three months, which BelkaCar treats as a distinct segment. Each band should have its own message logic and its own success metric.

SegmentInactivity windowRecommended channelPrimary message goal
At-risk3–7 daysIn-app message on next openCollect feedback, surface a feature
Lapsing8–30 daysPush notificationRemind and offer a reason to return
Dormant1–3 monthsPush plus in-app on returnReintroduce value, offer incentive
Deeply dormant3+ monthsPush with tested incentiveReactivate or suppress

This table is a synthesis of the inactivity windows documented by Pushwoosh and BelkaCar, arranged into a single decision framework. The distinction between at-risk and dormant users is not cosmetic. At-risk users still open the app, so in-app messaging is viable and inexpensive. Dormant users may not open the app at all, so push is the only channel that can reach them. Treating the two groups identically wastes the cheaper channel on the harder audience.

Why Does Channel Choice Matter More Than Message Copy?

The strongest finding across the evidence is that channel routing drives results before copywriting does. Pushwoosh's documented workflow branches on whether a user opened the app within three days. Users who did are shown an in-app message with a button leading to a feedback form; the branch then ends with an exit element. That structure means the in-app message is not a generic promotion. It is a diagnostic tool aimed at understanding why users abandon the app.

Push notifications, by contrast, are the outbound channel that can reach a device regardless of app activity. BelkaCar deployed in-app messages, event-based behavioral messaging, and push notifications as a combined stack, then triggered event-based alerts and sent pop-up in-app service notices and promotion pushes. The combination produced click-through rates around 17 to 20 percent on retention pushes. That figure is unusually high for push, and it reflects the value of sending the right message to a segmented audience rather than broadcasting to everyone.

The channel rule can be stated simply: use push to bring users back, and use in-app messaging to keep them once they return. Push notifications interrupt; in-app messages welcome. A re-engagement program that sends only push notifications recovers users into an empty experience. A program that pairs the two gives returning users an immediate reason to stay. This connects to a broader user acquisition strategy for mobile apps, because reactivated users behave like a fresh acquisition cohort and should be onboarded with the same care.

What Incentive Structures Actually Reactivate Users?

Incentive design is where most re-engagement campaigns either succeed or stall. Publishers Clearing House tested personalization, emojis, tokens, Superprize entries, and weekly grand prize entries through push and in-app messaging, using A/B testing to optimize the correct incentive to drive app engagement each day. The program also used segmentation and in-app pop-ups based on the user's loyalty status, offering different entries to different users. That produced a 23% increase in daily active users during the flagship Superprize contest.

The lesson is that incentive fit depends on user history. A loyalty-status-based offer works when the app has a loyalty program with visible tiers. A token or entry-based offer works when the app has a game or chance-to-win mechanic. Publishers Clearing House is a free-to-play, chance-to-win digital entertainment site, which is why Superprize entries functioned as a relevant incentive. A productivity app cannot copy that mechanic directly; it would need an equivalent intrinsic or status-based reward. This is a case where the framework transfers but the specific incentive does not.

BelkaCar's program leaned on service messages and targeted promotions rather than chance-based rewards. The click-through rates in the 17 to 20 percent range suggest that timely service updates and relevant promotions can carry re-engagement on their own. One exception worth noting: apps with strong transactional value, such as carsharing or delivery, can re-engage with utility messages alone. Apps with weaker utility depend more heavily on incentives, which makes A/B testing of reward types essential.

How Do You Measure Re-Engagement Success?

Measurement should follow the funnel from delivery to reactivation to retention. Publishers Clearing House reported 30,000 dormant users re-activated, a 3.93% overall conversion rate, a 58% increase in average in-app click-through rate, and a 23% increase in daily active users. Each metric answers a different question. Conversion rate asks whether the reactivated user completed a target action. Click-through rate asks whether the message was compelling. Daily active user lift asks whether the campaign changed overall app health. BelkaCar's reported metrics, including click-through rates around 17 to 20 percent, millions of messages sent, and 300,000+ monthly active users, follow the same logic.

A useful measurement framework tracks four layers. Delivery metrics confirm the message reached the device. Engagement metrics capture opens and clicks. Reactivation metrics count users who returned after the defined dormancy window. Retention metrics check whether those users were still active thirty days later. Most campaigns stop at layer two and therefore cannot prove they revived anyone. The 25% revival benchmark in this article's title should be read as the reactivation-layer outcome, not an open-rate figure.

The measurement plan should also account for suppression. Users who have disabled push notifications cannot be reached by that channel, and repeatedly pushing to them damages brand trust. A disciplined program removes hard-bounced and long-dormant, unresponsive users from the push list and routes them to in-app messaging only if they return organically. This is a tradeoff: suppression reduces reach but protects deliverability, which matters more over the long run.

Proposed Solution/Approach

The Four-Stage Re-Engagement Workflow

The framework proposed here converts the evidence into a repeatable workflow. It has four stages: define, segment, route, and test.

Stage 1: Define dormancy. Set inactivity windows that match your app's natural usage frequency. A daily-use app should treat three to seven days of inactivity as at-risk, following Pushwoosh's guidance. An occasional-use app can use one, three, and six month bands, following BelkaCar's model. Document the windows and keep them stable so that results are comparable across campaigns.

Stage 2: Segment. Build automated segments for each inactivity band. Pushwoosh provides automatically created segments for users who have not opened the app, which reduces manual setup. The segments should be behavioral, based on actual app opens, not on registration date or demographics alone.

Stage 3: Route. Assign each segment a channel and a message goal. At-risk users receive an in-app message on their next open, aimed at feedback collection or feature discovery. Dormant users receive push notifications with a tested incentive. Returning users receive an in-app message that welcomes them back and reintroduces the core value proposition. Publishers Clearing House's use of loyalty-status-based in-app pop-ups and push messaging shows how routing can also vary by user tier within a segment.

Stage 4: Test. Run A/B tests on incentive type, personalization, and message format. Publishers Clearing House tested personalization, emojis, tokens, and prize entries to optimize the correct incentive each day. Testing should be continuous rather than a one-time exercise, because user preferences shift and what worked last quarter may not work this quarter.

A Practical Decision Checklist

Before launching a campaign, confirm each of the following. The list is derived from the documented workflows in the evidence and should be treated as a minimum standard.

  • Dormancy windows are defined and documented for each usage band.
  • Automated segments exist for at least three inactivity levels.
  • Every segment has an assigned primary channel (push or in-app).
  • At least one in-app message is configured to collect abandonment feedback.
  • Incentive variants are prepared for A/B testing.
  • Success metrics cover delivery, engagement, reactivation, and retention.
  • Suppression rules exist for unreachable or repeatedly unresponsive users.

This checklist is not exhaustive, but it prevents the most common failure: launching a campaign that measures opens without measuring returns.

Mini-Case Example (Hypothetical)

Consider a hypothetical fitness app with a daily-use pattern. The team defines at-risk users as anyone inactive for five days. On day five, a push notification offers a short workout plan. If the user opens the app, an in-app message asks whether the plan length was the barrier to returning. Users inactive for thirty days receive a push with a trial extension offer, tested against a social-challenge invitation. The team measures reactivation at fourteen days and retention at thirty days. This example is illustrative only; the specific windows and offers should be calibrated to the app's actual usage data.

Implementation Considerations

Technical implementation depends on the platform. Flutter and FlutterFlow apps can integrate segmentation and messaging through supported engagement platforms, and teams that prefer to build quickly can use no-code options to configure in-app messages and push triggers. The framework itself is platform-agnostic, but the execution details differ.

Three implementation constraints deserve attention. First, in-app messages require the app to be open, so they cannot reach users who have stopped opening it; this is why the at-risk segment, not the dormant segment, is the right target. Second, push notifications depend on user permission and device settings, so a permission prompt strategy should be part of the plan. Third, event-based triggers require clean event tracking; BelkaCar's program used event-based behavioral messaging, which depends on reliable event data.

Organizational constraints matter too. Re-engagement campaigns compete for product and engineering time, and the testing cycle in the Publishers Clearing House program ran daily to optimize incentives. That cadence requires a team that can monitor results and adjust creative quickly. Teams with limited resources should start with two segments and one tested incentive, then expand once the workflow is stable.

The framework also connects to launch planning. Apps that plan re-engagement before launch avoid the common mistake of building a user base with no recovery mechanism. An app launch strategy that includes dormancy definitions and messaging infrastructure from day one is better positioned than one that adds them after churn appears. App store visibility, covered in the app store optimization guide, affects the quality of the users who enter the funnel, which in turn affects how many become dormant and how easily they can be revived.

Conclusion

The re-engagement campaign framework works because it treats dormancy as a segmented condition rather than a single event. Users inactive for a few days need a different message and a different channel than users inactive for months. Push notifications bring users back; in-app messages keep them. Incentives must be tested, not assumed. The published programs from Pushwoosh, Publishers Clearing House, and BelkaCar show that this structure produces measurable reactivation, with conversion rates near 4 percent, click-through rates in the high teens, and daily active user lifts above 20 percent.

The 25% revival benchmark is achievable when the four stages are followed: define, segment, route, and test. Teams that skip segmentation and testing will see far lower returns, and teams that measure only opens will not know whether they succeeded. The framework is not a guarantee; results depend on app category, user base quality, and incentive fit. But it is a disciplined starting point that turns a vague retention goal into a measurable workflow. FlutterFlow Agency builds high-quality, scalable applications and can guide teams through implementing this framework with fast development and expert consultation.

References

  • Pushwoosh documentation. How to create a re-engagement campaign in Pushwoosh.
  • MoEngage case study. PCH Re-engaged 30k Dormant Users With MoEngage Predictions.
  • CaseStudies.com. Case Study: BelkaCar achieves 17–20% CTR and boosts user retention with Pushwoosh.
  • FlutterFlow Agency customer-approved business context.

Related Posts