Console cross-play and the mobile funnel

A console title that adds a mobile companion client, or a mobile-first game that adds a console version, creates an audience overlap question a UA team rarely gets asked to help answer, and almost never gets clean data to answer well.

The overlap is easy to describe. Measuring it isn't. A player who owns the console version and installs the mobile companion app is not a new acquisition in any meaningful sense, yet most mobile attribution stacks have no reliable way to flag that installer as an existing player arriving from another platform rather than a genuinely new user sourced by a paid campaign. SKAN and AdAttributionKit postbacks fire the same way whether the install represents new demand or a console player simply adding a second client; a campaign optimising toward installs can therefore collect credit for traffic it never actually acquired.

Where store rules complicate the picture further

Cross-purchase entitlement, where owning a title on one platform grants access on another without a second payment, adds a policy layer on top of the measurement gap. Apple and Google both have rules governing how a cross-purchase entitlement can appear inside an app, and a studio that gets the in-app messaging wrong risks a review rejection that has nothing to do with UA but stops a mobile companion launch cold regardless. A UA lead should flag this early in any cross-play project. Not because UA owns the compliance question, but because a delayed launch changes every campaign timing assumption already built into the media plan.

The fix most studios land on is manual. Rather than building attribution logic that detects cross-play installs, several publishers running dual-platform franchises simply exclude console-linked account creation events from paid UA performance reporting entirely, treating that population as a retention and engagement cohort rather than an acquisition one. It's blunt. It undercounts the genuine new-user value a console companion app occasionally generates among console owners' friends and family, but it avoids the larger error of crediting a campaign for installs it did not create. Until MMPs build a standard way to flag cross-platform account linkage inside an SKAN-constrained postback, that blunt exclusion remains the more defensible reporting choice.

Related archive reading

• A Year-End Measurement Stack Review Before You Rebudget
• Gamescom on a phone: capturing PC and console attention for mobile launches