Why one wishlist per shopper isn't enough
People don't shop with one intention. The same customer might be planning a birthday gift, eyeing a few things for summer, and keeping a running "one day" list of bigger-ticket items. If they only get a single wishlist, all of that collapses into one undifferentiated pile — and most shoppers will simply stop using it, because it stops being useful to them.
Named lists fix that. When a shopper can organise saves by occasion or theme, the wishlist becomes a tool they actually return to. That's good for them, and it's good for you: an organised, regularly-used wishlist is a far stronger purchase-intent signal than a forgotten one.
How named lists work in WishList Ninja
Setting up multiple wishlists is entirely the shopper's choice — there's nothing for you to configure. From the wishlist drawer or page they can:
- Create a new named list — e.g. "Birthday", "Summer wardrobe" or "Gift ideas for Mum" — with no limit on how many they keep.
- Choose which list to save into when they tap the heart on a product or collection card.
- Save a whole collection to a list in one go, not just individual products.
- Share a single list with a share link, so family or friends can see exactly that list and nothing else.
One profile, clean data
Here's the part merchants worry about: if a shopper keeps five lists, does your email data turn into a mess of five separate records? No. However many named lists a shopper keeps, they all roll up into a single customer profile in your email platform.
That means the properties WishList Ninja syncs — wishlist_count, wishlist_value and has_active_wishlist (and the matching Mailchimp merge fields WL_COUNT, WL_VALUE, WL_URL and WL_ACTIVE) — always reflect the shopper as a whole. You segment and trigger on the customer, not on individual lists, so your Klaviyo, Mailchimp and Omnisend flows stay simple while your shoppers get all the organisation they want.