Your wishlist saves are invisible to Meta. Here is how to fix that.

You paid for the click. The shopper landed on the product page. They did not buy.

They saved it instead.

That save is the strongest buying signal you get short of an add to cart. Someone told you, unprompted, exactly which product they want. And on most stores, that signal goes absolutely nowhere.

Your pixel never learns it happened.

What Meta actually logs when someone saves

We tested this on a live store. Wishlist button installed, Meta Pixel firing normally, everything healthy.

A shopper saves a product. Open Events Manager and here is what arrives:

Event	What it means
PageView	Fine. They looked at the page.
ViewContent	Fine. They looked at the product.
SubscribedButtonClick	Meta guessed. It saw a button click it could not classify.

That third one is the problem. It is not a wishlist event. It is Meta's automatic detection shrugging.

You cannot build a custom audience from a shrug. You cannot optimise a campaign toward it. You cannot tell your client it drove anything.

Why this is worse than it sounds

Think about what you already do with add to cart. You build an audience. You retarget it. You exclude purchasers. You let the algorithm optimise toward it. Add to cart is a workhorse.

A wishlist save sits just below it in intent and often above it in specificity. A cart can be a browse. A save is a decision to come back.

And you are throwing it away, on the traffic you paid the most to get.

The fix: send the standard event

Meta has a standard event for exactly this. It is called AddToWishlist. It has existed for years. Standard events are the ones you can build audiences from and optimise against without any custom setup.

What a useful payload looks like:

Field	Why it matters
content_ids	The product id, so you can retarget the exact item they saved.
content_type	Set to "product", so it matches your catalogue.
value and currency	Lets you weight audiences by basket size and report properly.
content_name	Readable in Events Manager when you are debugging at 1am.

Get those four right and the save stops being a mystery click and becomes a targetable intent signal.

How to check your own store in two minutes

Install Meta Pixel Helper, open a product page, save something, and watch what fires. If you see AddToWishlist, good. If you see SubscribedButtonClick, or nothing at all, your wishlist app is not reporting.

Do the same in GA4 Realtime and look for add_to_wishlist. Same test, same answer.

Turning saves into an audience

Once the event is landing, the setup is ordinary Meta work:

• Create a custom audience from the AddToWishlist event, 30 days.
• Exclude Purchase, 30 days. Nobody wants an ad for the thing they just bought.
• Consider excluding AddToCart too, so this audience stays distinct and you can read the results.
• Run dynamic product ads against it so people see the item they actually saved.

Then leave it alone long enough to mean something. A wishlist audience on a small store builds slowly, and judging it after four days will tell you nothing.

What to say to a saver

Resist the urge to open with a discount. They already want it. A discount teaches them to wait next time.

Better angles: it is nearly out of stock, if that is true. Free shipping over a threshold. Or just show them the product again, cleanly, and let intent do the work.

Save the discount for the ones who do not come back. That is what your reminder and back-in-stock emails are for, and email is far cheaper than another impression.

The same signal, everywhere else

Meta is where most people notice this, but the save is worth sending to every platform you run:

Platform	Event
Meta	AddToWishlist
GA4	add_to_wishlist
TikTok	AddToWishlist
Google Tag Manager	dataLayer push, so you can route it anywhere

GA4 is the one people forget. Once add_to_wishlist is landing, your funnel exploration finally shows the step between "viewed" and "bought" where most of your traffic actually sits.

Full disclosure: now grade us

We build Simpll Wishlist, so treat everything above as interested advice and go verify it in your own Events Manager.

Here is where we stand against the thing this article argues for:

Question	Where Simpll Wishlist stands
Fires the standard AddToWishlist event	Yes, with content_ids, content_type, value and currency.
Which platforms	Meta, GA4, TikTok, Google Tag Manager and Pinterest, plus a DOM event you can hook yourself.
Which plans	Every plan, including the free one.
Reports revenue driven by the wishlist	No. Not yet. We show demand and recovery activity, not attributed revenue.
Captures who saved what	Yes, but capture sits on the paid plan. The free plan gives aggregate demand only.
SMS	No. Email only today.

Two of those are honest weaknesses, and we would rather you read them here than discover them in week two. Revenue attribution is the one we get asked about most, and it is not built.

On pricing, the free plan includes the pixel events, because a signal you cannot access is not much of a feature.

Before you install anything, ours included, run the test on the app you already have. Save a product on your own store and open Events Manager. If AddToWishlist is missing, you now know exactly what to ask your current app for.

And if your current wishlist app already fires the event properly, stay where you are. The point of this article is the signal, not the logo on the app that sends it.