How do I test that wishlist events reach Klaviyo?
Wishlist Hero sends three wishlist events into Klaviyo from your storefront. Before you build flows on them, verify the events arrive. This guide walks through enabling the integration and running a complete test cycle in about ten minutes.
Available on Silver plans and above.
Enable the integration
- Go to Settings and open the Klaviyo onsite tracking page.
- Switch on Enable Klaviyo Onsite Tracking.
- Save.
The integration uses Klaviyo’s own onsite script on your storefront, so it works with the Klaviyo account already connected to your store. No API key is needed for these storefront events.
The three events
| Klaviyo metric | Fires when |
|---|---|
Added To Wishlist (WH) |
A shopper saves a product |
Removed From Wishlist (WH) |
A shopper un-saves a product |
Cleared Wishlist (WH) |
A shopper empties their list with Remove All |
Each event carries product properties you can use in emails: Name , ImageURL , URL , Price , PriceFormatted , ProductID , VariantID , SKU , Vendor , Tags , CurrencyCode , and Quantity . The shopper’s Klaviyo profile also receives MyWishlistLink and MyWishlistProductIDs .
Run the test
- Open your storefront in a browser where you are logged in as a customer. Klaviyo onsite events attach to the logged in profile.
- Add a product to the wishlist.
- Remove it, then add it back so the list is not empty.
- In Klaviyo, open Analytics > Metrics (or the activity feed for the profile).
All three metrics should appear within a minute or two, each with the product properties on the event.
If the events do not appear
| Symptom | Fix |
|---|---|
| Nothing arrives | Confirm you were logged in on the storefront; guest actions do not attach to a Klaviyo profile |
| Toggle was already on, still nothing | Hard refresh the storefront so the script reloads, then retry |
| Events arrive for one shopper only | That is expected in testing; each browser tests its own profile |
| Metric missing in the flow builder | Klaviyo lists a metric in flow triggers after the first event fires. Send the test event yourself, then reopen the trigger picker |
That last point is the most common trip: Klaviyo cannot offer a flow trigger for a metric it has never seen, so always run this test before building flows.
After the test
Your events are ready for flows. Continue with: