# Feeding wishlist adds into interest audiences on Hydrogen

Asked by Yara Haddad on 2026-07-05. Tags: shopify, hydrogen, events, audiences.

Auto-tracking already covers what we need for most signals: product views, cart
views, cart updates, collection and search views all flow in without any code
from us.

Our strongest interest signal, though, is the wishlist. When someone wishlists
three abayas in one session, that tells us more than any page view. Wishlist adds
do not seem to be in the auto-tracked set.

Which event should I send for a wishlist add, and how does it connect to the
interest conditions in audiences

## 2 answers

### Accepted answer from Lucas Meyer (2026-07-05)

Correct, wishlist adds are not part of the Hydrogen auto-tracked set (that set
is product views, cart views, cart updates, and collection and search views),
so they need a custom event from your wishlist handler.

The purpose-built event for this is `interestShown`. Fire it when the shopper
adds to the wishlist, passing the interests the product represents:

```js
croct.track('interestShown', {
    interests: ['abayas'],
});
```

Those interests feed the profile, and from there the standard interest
condition works in your audience definitions:

```cql
user has shown interest in ["abayas", "dresses"]
```

So the wiring is: wishlist handler sends `interestShown`, profile accumulates
the interest, audience matches on it, and your slot serves the variant for that
audience. The auto-tracked product views keep contributing interest signals in
parallel, the wishlist events just add the stronger ones.

#### Reply from Yara Haddad (2026-07-06)

Exactly what I needed. Wired it into the wishlist mutation and the interests
show up on the profile right away.

### Answer from Ines Ferrari (2026-07-06)

Small addition from having done the same thing: keep the interest values
consistent with whatever taxonomy your product views already imply. If your
collections produce interests like "shoes" and your wishlist events send
"footwear", the audience conditions end up needing both spellings forever.
We derive the interest string from the same product category field in both
places and it stays clean.