The Steam wishlist problem
Steam wishlists are the default pre-launch KPI for PC games. They are also a weak owned channel:- You cannot email or message wishlisters yourself.
- Valve’s launch email competes with every other game launching that week.
- Months of silence between wishlist and ship cools intent.
- Paid UA that only optimizes for wishlists rarely proves it created players.
What Engage does
Messages use CDP traits and events—signup source, Funnel Page tier, last active date, quest completion—not a static CSV from six months ago.
Typical setup for a Steam game
1
Capture an owned identity
Send UA and social traffic to a Funnel Page (or Web SDK on your site) so players leave an email or linked account. Keep the Steam wishlist button as a parallel CTA.
2
Import what you already have
Upload existing lists in Hub if you have them (Ingestion).
3
Turn on Engage in Hub
Enable welcome, nurture, win-back, and launch sequences for your game. Adjust segments when you care about high-intent vs cold traffic.
4
Instrument the game
After launch, send session and progression events (Unity / REST) so win-back and post-launch campaigns use live behavior.
Channels
Steam remains the storefront and wishlist surface. Engage is the channel you control.
Targeting
Target on profile data from the CDP, for example:- Signed up but never completed a quest
- Funnel Page tier or referral source
- Inactive for N days before launch
- Came from a paid campaign (via Attribution) but has not installed
Funnel Page triggers
When players live on a Funnel Page, common triggers include:Next steps
Funnel Page
Capture owned players next to the Steam CTA
Ingestion
Get signups and events into the CDP
Analytics
See which segments are worth messaging
Attribution
Tie spend to signups and installs—not only wishlists