Your shoppers' wishlists are one of the clearest signals of what they actually want to buy. With this new integration, Wishlist Plus pushes each shopper's wishlist into Klaviyo as a Swym object tied to their profile, so that wishlist intent can power any email or flow you run in Klaviyo, not just your wishlist reminders.
What this unlocks
Today, Wishlist Plus already sends the right message when something changes on a wishlisted product. Through the Klaviyo integration you can trigger dedicated flows for:
Wishlist reminders
Price drop on a wishlisted item
Wishlisted item running low on stock
Wishlisted item back in stock
These flows are great, but they only fire when a wishlist event happens. Every other email you send, your newsletter, win-back, VIP, post-purchase, and browse abandonment messages, currently has no idea what a shopper has saved.
This integration closes that gap. Once your shoppers' wishlist data lives in Klaviyo as an object, any campaign or flow you own can reflect that intent. The wishlist goodness is no longer limited to Swym-triggered emails. It flows into the rest of your Klaviyo stack.
What you can do with wishlist data in Klaviyo
Once the data is in Klaviyo, how you use it is up to you. Here are some of the most popular ways merchants put it to work:
Post-purchase cross-sell. After a shopper's order arrives, show the remaining items on their wishlist instead of generic recommendations. They are already in a buying mindset, and you are showing them things they have told you they want.
Win-back and re-engagement. Instead of a generic "We miss you," remind lapsed shoppers of the specific items they saved before going quiet.
Browse abandonment. Alongside the product a shopper just viewed, surface a couple of their active wishlist items to give them more reasons to come back.
VIP and early access. When VIPs get early access to a sale, feature their own wishlisted items at the top of the email.
Newsletters and campaigns. Add a personalized block to your regular sends that shows each shopper's saved items, turning a batch email into a personalized nudge.
Smarter segments. Build Klaviyo segments off wishlist data, for example shoppers with active wishlist items, high-value wishlisters, or shoppers who saved something in the last two weeks, and use them as triggers or conditional splits in any flow.
In Klaviyo, the wishlist records appear under Content > Objects, and you can pull them into email templates and segments using Klaviyo's standard editor.
Eligibility
This feature is available only to merchants meeting the below conditions:
On the Wishlist Plus side
You are on the Premium plan or above.
On the Klaviyo side
You have Klaviyo connected to your store.
Your Klaviyo account is on a paid email plan or an Advanced KDP plan. Klaviyo's custom objects feature (which this integration relies on) requires one of these. You can read more about Klaviyo's plan requirements and account limits for custom objects in Klaviyo's help center.
If you are not sure whether your Klaviyo plan qualifies, our team can help you confirm when we reach out.
How it works
Setup is handled entirely by our team. To set up this feature, please write to us on [email protected]. Here is what happens once you reach out to us:
We set it up for you. Once we receive your email, our team reaches out and configures the Swym wishlist object in your connected Klaviyo account. There is no complex setup on your end.
We backfill the last 60 days (Only Enterprise plan eligible). When your integration goes live, we populate your shoppers' wishlist activity from the previous 60 days, so you have meaningful data to work with from day one.
We keep it current with a daily sync. From then on, we sync wishlist activity to Klaviyo every day. Your Klaviyo account keeps an up-to-date record of each shopper's wishlist as Swym Wishlist Product objects, so your segments and email content stay accurate over time.
What's in each wishlist object
Each Swym Wishlist Product object represents a single product a shopper has saved, tied to that shopper's Klaviyo profile. If a shopper has five items saved, they have five objects on their profile, each with its own wishlist_item_id.
We intentionally keep each object lightweight. It carries the identifiers, status, and timestamp, not a frozen copy of the product's title, price, or image. Product content is pulled live from the catalog Klaviyo already syncs from Shopify, using the product_id (covered in the next section). This way your emails always show the current price, image, and availability instead of whatever was true on the day the shopper saved the item.
The fields on each object:
Field | What it is | How you use it |
| Unique ID of this saved-item record. Every product a shopper saves gets its own object with its own | Reference or de-duplicate individual saved items |
| The Shopify Product ID of the saved item. This is the key you pass to Klaviyo's catalog lookup to hydrate full product details. | Look up live product data via |
| The Shopify Variant ID of the exact option the shopper saved (size, color, and so on). | Show or branch on the specific saved variant |
| The current state of the saved item, either | Keep templates and segments to items a shopper still has saved |
| When the shopper saved the item. | Sort saved items most-recent-first, or build recency segments |
Sample record:
wishlist_item_id: 843530578
product_id: 7578545619028
variant_id: 41762975055956
wishlist_status: active
wishlisted_at: Sep 3, 2026, 1:24 PM
These last two fields are what power the segment ideas above: filter on wishlist_status for active to target only currently-saved items, and use wishlisted_at to build audiences like shoppers who saved something in the last two weeks.
The exact property names, as they appear on your object, are visible in Klaviyo under Content > Objects. Use those keys when you reference fields in your templates and segments, since the lookups are case and name sensitive.
Using product_id and variant_id with Klaviyo's catalog tag
Because the object stores identifiers rather than full product content, you use Klaviyo's catalog lookup tag to pull in the product's title, image, link, and price at send time. You pass the product_id from the object, and Klaviyo returns the current details from the catalog it already syncs from your store.
A basic lookup looks like this:
{% catalog product_id unpublished="cancel" %}
{{ catalog_item.title }}
{{ catalog_item.link }}
{{ catalog_item.featured_image.full.src }}
{{ catalog_item.price }}
{% endcatalog %}What each part does:
product_id: replace this with theproduct_idfrom the Swym object. Klaviyo matches it against the Shopify Product ID, not the SKU.unpublished="cancel": if the product is no longer published, this stops the send so you never email a shopper a dead link.catalog_item.*: the product fields Klaviyo returns. Commonly used ones aretitle,link,featured_image.full.src,price, anddescription.
Pulling custom metadata. If your catalog carries extra product fields (for example a custom color or material attribute), reference them through the metadata object:
{% catalog product_id %}
{{ catalog_item.metadata.color }}
{% endcatalog %}Working with the variant. For most emails, product_id is the reliable lookup key, so use it to render the product, and use the object's variant_id where you need to display or branch on the specific option the shopper saved. If you do need variant-level catalog data, you can tell Klaviyo the ID is a Shopify variant:
{% catalog variant_id integration:'shopify' %}
{{ catalog_item.variant.featured_image.full.src }}
{% endcatalog %}Seeing every available field. To view all the data available on a given product, drop one product's ID into a test template and preview the full catalog_item object. Klaviyo's Catalog lookup tag reference documents the preview snippet and the full list of supported attributes, including how to target a specific catalog if you have more than one.
Frequently asked questions
Do I need to do any technical setup or write code? No. During the beta, our team configures the Swym wishlist object in your Klaviyo account for you. Once it is live, you build segments and email content using Klaviyo's standard drag-and-drop tools.
Will this replace my existing wishlist flows? No. Your wishlist reminder, price drop, low stock, and back-in-stock flows continue to work exactly as they do today. This integration adds wishlist data to the rest of your Klaviyo emails on top of those.
How far back does my wishlist data go? When we first set you up, we bring in the last 60 days of wishlist activity. After that, we keep the data current with a daily sync.
What if my Klaviyo plan does not qualify? Custom objects require a paid Klaviyo email plan or an Advanced KDP plan. If your current plan does not include it, you may need to upgrade with Klaviyo. Our team can point you in the right direction during onboarding.