Adoption Nurture

Adoption nurture belongs in your plan when most users who complete their first meaningful action never return for a second one, or product analytics shows usage falling away sharply right after the first value moment. Define regular use around the product's natural rhythm, confirm that the first meaningful action and repeat actions are tracked per user and that push permission is known, and pick in advance the related feature and the next-use scenario you will highlight. If users clearly fail to see the product's value or hit friction after the first action, investigate that first; more push notifications will not solve it.

Incremental regular-use rate vs control

Some users build the habit without a reminder, so the measure is how far the pushed group's regular-use share exceeds the control group's, not opens or taps.

How it is counted: Everyone assigned at the first meaningful action to the journey or control group forms the denominator; the numerator is those who reach the regular-use definition you set within the same follow-up window from assignment. Whether a push was delivered or tapped does not change the denominator.

Also track

• Repeat action rateAmong assigned users, the share who repeat the same or a second meaningful action; the intermediate step before regular use, tracked separately from it.
• Result by branchRead users who repeated on their own at the first check separately from those who repeated after the feature push, and judge the regular-use push's contribution within each of those groups.
• Use of the highlighted featureUsers who actually use the highlighted feature after the feature push, as a share of those pushed; if it is low, the feature you chose may not build on the first value.
• Opt-outs after the pushesCount users who switch push off after either push; losing permission from a new user closes that channel for every later journey.

• Trigger and entryCompleting the first meaningful action opens the journey; finishing onboarding is not the trigger. Split entrants at random into a journey group and a control group that gets no push from this flow.
• Who must not enterWhat is followed is the user's product usage after activation, so only one flow runs per user at a time. Users whose usage is already regular stay out, and a user who has not yet completed the first meaningful action is still an onboarding matter, not this journey's.
• Timing and channelsThree days after entry, the journey checks for a repeat action; if none, a push highlighting a different relevant feature goes out, then a 3 to 7 day wait. On a repeat, it checks whether usage is regular; if not, a push with the next-use scenario goes out, then a 5 to 7 day wait.
• Exit and handoffWhen usage becomes regular, reminders stop and the journey ends. If there is still no repeat action after the feature push, or usage has not become regular after the second push, messaging stops; there is no handoff, and the flow closes in its three exits.
• Frequency and consentA user receives at most two pushes: one feature push that points to another path to value, and one regular-use push. Push goes only where permission exists, and no upsell message is planned for this user until repeat value has actually shown up.

1. 1No gap in regular use between the two groups means the pushes went to users who would have built the habit anyway; more repeat actions without more regular use is not enough either. Do not scale the journey when the rise in push opt-outs eats the gap.
2. 2The result holds for the regular-use definition you set, these waits and at most two pushes. Nothing is handed off: regular use is credited to this journey, but do not start an upsell for the same user before that exit is seen, and never add the upsell's outcome to this journey's score.
3. 3A strict regular-use definition makes the outcome rare; with a small gap, give the A/B test significance calculator each group's users and how many reached regular use, and when it falls short of significance, lengthen the follow-up to cover the longest chain of waits.
4. 4Do not add messages when the feature push still brings no repeat; investigate the product's value and its friction first, then check that the feature you highlight is really a path that builds on the first value.