1. The flag that makes it work

You need a boolean on the profile — we sync has_active_wishlist (true / false), kept current in real time. Because it lives on the Klaviyo profile and Mailchimp contact, the email platform can read it at send time and decide what to render per recipient.

2. Conditional blocks in Klaviyo

Klaviyo's template language lets you wrap any block in a condition. Around the section you only want active wishlisters to see:

{% if person.has_active_wishlist %} … your wishlist block … {% endif %}

Everything between the tags renders only when the flag is true. You can also do the inverse — show a "start a wishlist" prompt when it's false — so the same email gently pushes both groups forward.

3. Conditional blocks in Mailchimp

Mailchimp uses merge-tag conditionals. With the flag stored in a merge field such as WL_ACTIVE:

*|IF:WL_ACTIVE=YES|* … your wishlist block … *|END:IF|*

Same idea: the block only appears for contacts whose field matches. Pair it with an *|ELSE:|* branch to show different content to everyone else.

Always send yourself two test profiles — one with the flag on, one off — and preview both. Conditional content is invisible until you check the branch you're not in.

4. Ideas that convert

  • "Still thinking about these?" — a saved-items reminder block inside your regular newsletter.
  • Wishlist-only offer — a small incentive shown only to people who've saved something.
  • Start-a-wishlist nudge — the inverse block for everyone without one, to grow the audience for next time.