Steam and PC as part of a mobile UA plan
Steam wishlists, PC creators and cross-progression now feed a mobile UA plan directly, if a studio times the sequencing right.
Wishlists on Steam function as a pre-registration mechanism that most mobile UA teams do not think to measure, even when their studio ships the same title on PC and mobile at launch. A wishlist add costs nothing to the platform and nothing to the studio beyond the page's existence, yet it behaves like a genuine intent signal. Valve's own guidance to developers has long treated wishlist counts as one of the best available predictors of day-one sales, and a studio running a joint PC and mobile launch can use the same signal to time a mobile UA ramp against actual demand rather than a release-date guess.
The more useful shift is how much easier Google has made the mechanics of treating PC and mobile as one funnel rather than two. Google's GDC announcements, covered at the time in this newsletter's piece on Game Trials, Sidekick and Buy Once, Play Anywhere, introduced cross-device pricing that lets a player buy a title once and play it on both a PC through Play Games and an Android phone. That change removes a purchase-decision barrier that used to sit between a studio's PC audience and its mobile install numbers: a player no longer has to decide whether the mobile or PC version is the purchase, because it is the same purchase either way.
What this means for a UA plan that spans both platforms
For a studio with a genuine cross-platform title, the practical UA question becomes sequencing rather than channel selection. PC-first creators and Steam's own discovery algorithm, curated lists, wishlist-driven visibility spikes around a demo or a festival, tend to build an audience with strong purchase intent well before a mobile campaign would normally start. Treating that PC audience as a warm list for mobile UA, through owned channels like a newsletter signup gated behind the Steam page or a Discord server built during early access, gives a UA team a cohort worth testing against before spending a single pound on cold mobile acquisition.
Cross-progression, where a save file or an account carries between PC and mobile, changes the retention argument enough that a UA team should pay attention even without budget authority over the feature itself. A studio that ships cross-progression can justify a slightly higher CPI tolerance for mobile installs sourced from players who already own the PC version, because those installs carry demonstrably higher retention than a cold acquisition, a pattern several publishers running dual-platform strategy and survival titles have described in earnings commentary without publishing the underlying cohort numbers.
Steam's periodic festival events, timed clusters of demos across many titles at once, generate a second signal worth folding into the same sequencing logic. A studio that times a demo drop to coincide with one of these festivals typically sees a short, sharp spike in wishlist adds that says more about near-term purchase intent than the steady background rate the page accumulates the rest of the year. A UA team that treats that spike as a leading indicator, rather than noise to average out, can use it to decide whether a mobile campaign should launch alongside the PC release or wait a further month for the wishlist-to-purchase conversion window most Steam-side analysts describe as landing within the first fortnight after launch. Skipping that read and defaulting to a fixed mobile launch date regardless of what the PC-side demand signal shows is the single most common planning mistake studios make when they treat the two platforms as entirely separate campaigns rather than one funnel running at two different speeds.
The honest limits of the crossover
None of this replaces a mobile UA plan. Steam's audience, even a large one, is a fraction of the size of a mainstream mobile network's reach, and PC discovery signals do not transfer cleanly into an SKAN or AdAttributionKit conversion value schema, since the intent being measured happens on a platform outside the mobile measurement stack entirely. A UA lead who tries to build a formal attribution bridge between a Steam wishlist and a mobile install is solving a problem that mostly does not need solving. The useful move is sequencing and budget timing, not a unified dashboard.
The studios getting genuine value from this crossover treat Steam as a demand-sensing tool that informs when to open the mobile UA taps, and treat cross-progression as a retention feature that justifies the spend once the taps are open, rather than trying to attribute a mobile install directly to a PC-side action.
