Which wishlist events does Wishlist Hero fire?

This is the complete catalog of wishlist events, grouped by destination: Klaviyo onsite events, Klaviyo and Omnisend server triggers, pixel events, storefront document events, and the internal action log. Use it to wire tracking, build flows, and answer “does the app fire an event when…” without reading source.

Plan gates: Klaviyo onsite events and pixel events require Silver and above, and each has its own enable toggle in the app.

Klaviyo onsite events

Sent client side from your storefront through Klaviyo’s onsite script, attached to the logged in shopper’s Klaviyo profile. Enabled by Enable Klaviyo Onsite Tracking.

Event properties:

The same calls send a Klaviyo identify  with two profile properties: MyWishlistProductIDs  (array) and MyWishlistLink  (wishlist URL).

Klaviyo and Omnisend server triggers

Fired server side instead of app sent emails when Klaviyo or Omnisend is the selected email provider. Event names are identical on both platforms:

Reminder payload:

The trigger profile is the shopper’s email. Share payload adds: SenderName , SenderEmail , ReceiverEmail , ShareURL , SenderMessage , with the receiver as the profile.

Pixel events

All three fire the platform’s standard wishlist event, guarded by the presence of the platform’s own script on your storefront:

Enable each from its settings page: Meta Pixel, Google Tag, and TikTok Pixel under Settings. They use the pixel already installed by your Facebook, Google, and TikTok channels; no pixel ID is entered in Wishlist Hero.

Storefront document events

The storefront app dispatches custom events on document . Listen with document.addEventListener . Names are stable strings, all prefixed wishlist-hero- :

Example:

document.addEventListener("wishlist-hero-wishlist-updated", (event) => {
  console.log("wishlist changed", event.detail);
});

The app also re-dispatches Shopify’s ajaxProduct:added  theme event after a wishlist add to cart, so theme cart drawers refresh as they do for normal adds.

The internal action log

Independent of all the above, the admin records every action as one of four types, which power the dashboard, reports, and exports:

There are no order or checkout events: order attribution is out of scope for these events by design. See How activity is tracked for the reporting model.