How it works
Trigger and data needed
Trigger: commerce.productListAdds with no purchase within the wait window
- Cart-add and purchase Experience Events
- Product lookup data (name, image, price)
- Email or push consent
- Authenticated identity linked to ECID
Audience and journey logic
- Enter on cart-add event for known profiles
- Wait for the agreed window
- Exit immediately if a purchase event arrives
- Check channel consent and frequency caps
- Send a reminder with cart items from lookup data
- Optional second reminder; then exit
Channels
- Push
- On-site banner
- Paid-media suppression
How to measure it
- Conversion rate within 7 days vs holdout
- Revenue per journey entry
- Unsubscribe and complaint rates
Guardrails
- Never message without consent
- Cap reminders per person per week
- Do not show out-of-stock items
See it in a case study
This use case is implemented in the related case study.
Last updated: