Saved Product Reminder

Consider this journey when a large share of saved or favourited products is still unpurchased days later and app analytics show that few users return to their saved list on their own. Save, purchase and stock status events have to match on the same user and product, push and email consent must be stored separately, and Back-in-Stock Alert should be ready to take over out-of-stock items. If users cannot find their saved items or the list does not carry across devices, repair that experience first; a reminder is no substitute for a list that disappears.

Incremental saved-product purchase rate vs control

What matters is how much more often the reminded group buys the product it saved compared with the control group; a seen push or an opened email does not show that.

How it is counted: Among all users assigned to either group at the moment of saving, the share who buy the saved product within the same follow-up window from assignment; the difference between the groups is the journey's effect. A message that never arrived or was never clicked does not remove the user from the denominator.

Also track

• Purchases per touchTrack purchases in the 2 days after the push and the 5 to 7 days after the email separately; if the second touch adds no sales, rework the email.
• Alternative product purchasesCount users who buy one of the email's alternatives apart from purchases of the saved product; an alternative sale is not a recovered saved product, and a higher margin does not make an alternative relevant.
• Share handed to back-in-stockHow many entries are handed off because the product was out of stock at the first check; when that share is high, the stock problem behind saved items comes before any reminder.
• Push opt-outs and unsubscribesWatch users who turn off notifications or unsubscribe from email after each touch; saving is a strong signal, but two touches may still be too many for some users.

• Trigger and entryThe journey begins when a user saves a product or adds it to favourites. Split users randomly at that moment: one group receives the reminders, the control group sees no message about this product.
• Who must not enterUsers who have already bought the product do not enter. When the same product sits in a cart, Cart Reminder holds the flow and this journey is suppressed for that user; a user who only viewed the product belongs to Browse Abandonment. Each saved product gets a single flow; no second one opens for it.
• Timing and channelsAfter 3 days the journey checks purchase and stock; if the item is unpurchased and in stock, a push goes out. If there is no purchase 2 days later, an email with the saved product and genuinely relevant alternatives follows, and a final purchase check comes 5 to 7 days after that.
• Exit and handoffA purchase ends the journey at once, and any queued message is cancelled. If the first check finds the product out of stock, the user is handed to Back-in-Stock Alert without a sales message; and when 5 to 7 days pass after the email with no purchase, no further reminders are sent.
• Frequency and consentAt most one push and one email per saved product. Saving an item is not consent for every channel: push requires notification permission, email requires a subscription, and the back-in-stock handoff requires that the user asked for that alert.

1. 1No more saved-product purchases in the journey group than in the control group means the reminder merely caught users who were coming back anyway; push views or email clicks do not alter that reading. The decision rests on the purchase gap between the groups.
2. 2The finding holds for this push-then-email order and these waits. A later purchase by a user handed to Back-in-Stock Alert is credited to that journey, and once the product enters a cart the flow passes to Cart Reminder; do not show the same sale under two journeys.
3. 3When the gap is small, compare each group's users and purchases in the A/B test significance calculator; do not treat a non-significant gap as a win, let more saves accumulate and repeat the same read.
4. 4Sales messages reaching users for an out-of-stock product, or an email showing an outdated price, mean the stock and price data is stale; fix that freshness before reading the result.