Basic cart recovery follows a simple rule: cart activity happened, purchase did not, send a reminder. That can recover intent, but it can also message a customer too soon, during the night, after another channel already converted them, or repeatedly across several devices.
Start with the cart, then qualify the customer
SegmentHub keeps the useful cart context—the number of items, total and first item name—then waits for the configured delay. Before producing a notification, it checks whether the cart still qualifies, meets any minimum value, belongs to an eligible customer audience and remains within the per-customer reminder limit.
This makes the audience a policy layer. A retailer can target opted-in members, suppress recent purchasers, treat high-value customers differently or limit a campaign to customers whose lifecycle stage makes a reminder appropriate.
Respect time as part of relevance
A technically relevant message can still arrive at the wrong moment. Quiet hours are evaluated in the account timezone. If a campaign becomes due inside that window, SegmentHub postpones it to the end rather than discarding it or sending immediately.
Scheduled campaigns use the same timezone-aware principle. One-time sends handle launches and announcements; recurring sends resolve their audience again on each daily, weekly or monthly run; triggered campaigns respond to states such as cart abandonment.
Choose one reachable device
Profiles may contain several device tokens, and tokens may be reassigned as people change or share devices. SegmentHub selects a recently active device per profile, deduplicates shared tokens and skips stale registrations. Jobs are divided into provider-safe batches before delivery.
TTL and collapse keys prevent an old or duplicated notification from remaining useful forever. Deep links send the customer directly to the relevant app destination, while image, sound, badge, Android channel and custom data fields support the intended native experience.
Cap pressure across scheduled messages
Frequency limits protect profiles from receiving too many non-triggered pushes in a day. Triggered campaigns retain their own eligibility and reminder controls because a behavioral response should not be treated exactly like a broadcast calendar.
Measure the delivery chain
A campaign is not successful merely because it was scheduled. Reporting should distinguish the profiles that matched, devices that remained reachable, messages sent, provider outcomes, failures and invalid tokens. Invalid registrations are cleaned up so future reports and sends become more accurate.
Cart recovery checklist
- Define the abandonment delay and minimum cart value.
- Choose eligible audiences and explicit exclusions.
- Set quiet hours and per-customer reminder limits.
- Write message variables with safe fallbacks.
- Use a deep link that restores the intended cart experience.
- Review targeted, sent, failed and invalid-token outcomes.
Learn how one-time, recurring and triggered campaigns fit together on the Mobile Push page.