How to measure press preview success: metrics that matter

Engagement data from cloud-streamed press previews gives you six categories of signal. Here's what each one measures, what "good" looks like, and what to do with the data.

Session count and access rate

Access rate is the foundational metric: sessions played divided by invitations sent. If you invited 100 journalists and 40 played, your access rate is 40%.

A low access rate doesn't mean your game is unappealing. It signals friction somewhere upstream: bad timing (you launched the preview during a major industry event), wrong audience (your media list included journalists who don't cover your genre), a weak pitch (the email didn't convey why this preview matters), or technical barriers.

Cloud streaming removes the biggest technical friction point. There's no download, no install, no hardware requirement. The journalist clicks a link and plays. If your access rate is still low after removing that barrier, the problem is almost certainly in your pitch or targeting.

Session duration

Session duration is the single most useful signal for engagement quality. A journalist who played for 90 minutes is far more likely to write substantive, detailed coverage than one who played for 8 minutes.

For context, HowToMarketAGame's demo playtime benchmarks show consumer demo sessions ranging from 7-65 minutes median depending on game tier (HowToMarketAGame Benchmarks). Journalist sessions typically skew longer because they're evaluating professionally, taking notes, testing edge cases, and exploring content they'll need to describe in their review.

Virtual event attendees spend 27% longer online compared to in-person event participants (PassiveSecrets). Cloud-streamed previews benefit from this same dynamic: the convenience of remote access removes scheduling constraints that cap in-person session length.

Duration alone isn't enough, though. A 90-minute session where the journalist was stuck on a loading screen is not engagement. Pair duration with completion rate for the full picture.

Completion rate

Completion rate measures what percentage of journalists reached the end of your preview content. It's the quality check on duration data.

If completion is low, the causes are usually identifiable: the preview was too long for the time window, pacing dropped in the middle, a bug blocked progress, or objectives were unclear. Consider a scenario where 80% of journalists completed levels 1 and 2 but only 40% reached level 3. That's a pacing problem the design team needs to address before launch, and you now have the data to prove it.

Low completion isn't always bad. If journalists spent 45 minutes exploring an open-world preview without reaching the "end," that's a different story than journalists quitting after 10 minutes. Context matters.

Geographic distribution

Geographic distribution shows which regions generated the most engagement. This data feeds directly into regional marketing budget allocation.

If EU journalists average 75 minutes of playtime but US journalists average 35 minutes, that's a signal about where your game resonates most. It might reflect genre preferences, cultural alignment, or simply the strength of your PR relationships in each market.

Over multiple campaigns, geographic patterns become strategic assets. You'll learn which markets respond to which types of games, and you can adjust your media lists, localization priorities, and launch timing accordingly.

Temporal patterns

When journalists play matters as much as how long they play. Temporal data reveals time-of-day preferences, day-of-week patterns, and whether journalists return for additional sessions.

Return sessions are one of the strongest engagement signals available. A journalist who comes back for a second or third session is deeply invested. They're either exploring more content for a comprehensive review or showing the game to a colleague. Either way, that's a journalist worth prioritizing in your follow-up outreach.

Temporal patterns also inform preview window design. Your access window needs to be long enough for schedules to accommodate (journalists juggle dozens of pitches daily) but short enough to create urgency and prevent indefinite procrastination.

Device and connection data

Device and connection data tells you what journalists played on and how connection quality varied across sessions and regions.

This metric is primarily useful for understanding experience quality. If journalists in a specific region experienced consistent latency issues, their engagement data should be interpreted with that context. A short session might reflect a connection problem, not a content problem.

Cloud streaming normalizes the hardware variable entirely. Every journalist plays on the same server specs regardless of whether they're on a high-end workstation or a Chromebook. This eliminates one of the biggest confounding variables in press preview data: you know that differences in engagement reflect the game experience, not the hardware experience.

For more on how to structure the full workflow from build preparation through data collection, see the journalist demo workflow guide.