The most likely cause: the capture page is a dead end, not a detour
The most likely cause of a wishlist drop is a capture page that ends the visitor's journey instead of continuing it. A capture page is a landing page a studio controls that collects an email address or Discord join from a visitor before sending them on to Steam.
If that page's only exit is a "thanks, you're in" message, the visitor has to find the Steam store page themselves: search for the game, hope the search result is correct, and start over. Every one of those extra steps is a chance to lose them, and none of them exist on a plain Steam wishlist button.
The fix is a deep link: a link that lands the visitor directly on the Steam store page's wishlist button, not the store's homepage or a search result. A capture page built with a deep-linked next step adds contact information on top of the existing wishlist click; it does not replace or delay it.
For a studio sending traffic to a capture page, the practical difference is whether the visitor's next click is already queued up. A dead-end page hands the visitor a search box and hopes they use it correctly; a deep-linked page hands them the exact wishlist button they were already headed for, with no extra step in between.
Symptom, cause, and fix
| Symptom | Likely cause | Fix |
|---|---|---|
| Wishlist count drops after adding a capture page | The page ends after email/Discord capture instead of continuing to Steam | Deep-link the visitor to the store page's wishlist button as the immediate next step |
| High capture-page visits, low wishlist completions | Too many form fields before the visitor reaches Steam | Ask for one field (email) or two (email, Discord) and nothing else |
| Visitors bounce on the capture page itself | The capture page loads before the visitor has any reason to trust it | Lead with the same hook (trailer, key art) that earned the click, not a bare form |
| Mobile visitors drop at a higher rate than desktop | The deep link opens Steam's app-switch prompt awkwardly on mobile | Test the mobile handoff specifically; a broken app-switch loses the click entirely |
Ask for one field before the wishlist click, not three. Each additional field is one more reason to abandon the page. Email alone, immediately followed by the deep link to Steam, keeps the sequence to a single decision.
Order the ask correctly: capture, then wishlist, not wishlist, then capture. Putting the wishlist click first (a plain link to Steam) and the capture page after loses the studio the reason to build the page at all, since most visitors who wishlist directly on Steam never return to a second page afterward. Send traffic to the capture page first, collect the contact detail, then hand off to Steam.
Test the deep link on the device your traffic actually uses. A link that opens Steam's store cleanly in a desktop browser can drop into an app-switch prompt on mobile that some visitors don't complete. If most of a campaign's traffic is mobile, this single check matters more than any copy change on the page.
When a wishlist dip is unrelated to the capture page
Not every conversion drop after launching a capture page is caused by the page itself.
- A drop that started before the capture page went live points to a different cause: seasonal traffic, a store page change, or a paid campaign ending.
- A drop isolated to one traffic source (say, a single creator's video) usually reflects that source's own audience quality, not the capture page every visitor goes through.
- A capture page with a genuinely low completion rate (well under half of visitors finishing the email step) can still coexist with an unchanged or improved wishlist count, if the visitors who do complete it convert to wishlists at the same rate as direct traffic.
Rule out these three before assuming the capture page is the problem; changing the page when the real cause is a paid campaign ending wastes a week fixing the wrong thing.
Escalating past a one-time check
A single before/after comparison can mislead if traffic volume shifted for another reason in the same window. Compare wishlist conversion rate (wishlists divided by store page visits from that traffic source), not raw wishlist count, before and after the capture page launched, so a change in traffic volume doesn't get mistaken for a change in conversion behavior. If the rate is genuinely lower with the capture page live and the deep link is confirmed working, the next step is owning your game audience, which covers the tradeoffs of capturing an audience at all before optimizing the mechanics of doing it.
Conversion Funnel's landing pages are built around this exact deep-link pattern: they capture email and Discord alongside the wishlist at the same point of traffic, so a correctly built capture page produces a reachable list instead of just a Steam-side count. See Conversion Funnel.
Sources: Steamworks wishlist and store-page documentation (partner.steamgames.com); Immutable product mechanics for capture-page-to-wishlist deep-linking.
