Cart abandonment with push and email
Fire one well-timed reminder after someone leaves a cart, deep-link them back, and cap how often it can repeat.
Someone adds to cart and leaves. You want one nudge that lands them back on the cart screen — not a week of generic "come back" mail.
The shape of a useful reminder
A good abandonment campaign has four parts:
- An event that means "started checkout and did not finish".
- A delay long enough that they might still complete it themselves.
- A deep link that opens the same cart, not the home feed.
- A cap so a browsing session cannot generate three notifications.
Skip any one of those and the campaign either feels late, feels random, or feels like spam.
Track the cart, not just the user
The event should carry the cart id (or equivalent) in its parameters. Without that, the notification can only say "you left something behind". With it, the tap can reopen the exact cart.
Keep the delay in hours, not days. An hour later is a reminder. Four days later is a different conversation, and usually a worse one.
One route, every channel
The same structured route — a screen path plus key/value parameters — should travel on push and on email. Your onNavigate handler already maps that route to your own router. Do not invent a second deep-link scheme for email clicks.
Stop once they buy
If the user checks out during the delay, the send should not go out. Evaluate the audience at send time against an attribute that flips on purchase. Emailing someone about a cart they already paid for reads as broken, because it is.
A frequency cap covers the other failure: a user who adds and removes items all afternoon should not collect a stack of nudges.
Where Retainza fits
Retainza event triggers support delay and cooldown, segment filters are evaluated at send time, and campaigns carry a structured route across push, email and in-app. Frequency caps apply per recipient.
