Baymard's research puts average cart abandonment around 70%. Most of those shoppers weren't saying no they were saying not yet.
But the cart gives them only two buttons: buy or leave. So they leave, and the intent is gone.
We added a third button: Save for later it moves the item to their wishlist, syncs it to the store's email platform, and follow-ups happen automatically (price drop, low stock, back in stock).
How does the has_active_wishlist flag handle the gap between a shopper removing all items and re-saving something later — does it reset the profile each time or carry over historical value data to keep segments accurate?
Thanks for the reply, @farukjrew.
Good question — think of it as a live mirror rather than a log. The flag always reflects the wishlist as it is right now: remove the last item and has_active_wishlist flips to false on the spot, with wishlist_count and wishlist_value dropping to zero in the same moment. Save something again next week and it flips straight back to true — real time, no scheduled resets, no carry-over.
That's deliberate: the property's one job is to answer "does this shopper have live buying intent right now?" So a has_active_wishlist = true segment can never email someone looking at an empty wishlist.
And because segments in Klaviyo/Mailchimp/Omnisend are dynamic, shoppers flow in and out of them automatically as their wishlist fills and empties — no maintenance, and the segment stays honest instead of drifting stale over time. 🥷