How it works
Trigger and data needed
Trigger: browse or cart-add event without purchase, then a 30-minute wait
- Product ID, category and browsing duration from Web SDK events
- Loyalty tier and fan interests on the profile
- Purchase history for recommendations
- Email and SMS consent
Audience and journey logic
- Capture browse and cart events with product ID, category and duration
- Enrich profiles with loyalty tier and team affiliation; build a high-value segment such as fans who browsed several products and are loyalty members
- Start the journey 30 minutes after abandonment
- Email popular products plus a few personalised picks; test two subject-line variants
- Send an SMS reminder if the email is unopened after 24 hours, where SMS consent exists
- Exit fans who purchase
Channels
- SMS
- On-site recommendation
How to measure it
- Conversion rate against a holdout group
- Revenue per email
- Lifetime value and unsubscribe rate
- Review A/B results and refine recommendations roughly every two weeks
Guardrails
- Send SMS only with explicit consent
- Do not offer discounts that conflict with licensing or pricing rules
- Cap total reminders per fan
See it in a case study
This use case is implemented in the related case study.
Last updated: