Skip to content
Topics and reading paths

Growth & updates

Roblox Home PTR and early exits: find the weak stage

A fall in Home impressions does not identify the change to make. Inspect the chain in order: eligibility and delivery, play after impression, early exit, and later behavior of the organic RFY cohort.

Focused deep dive

Concepts and tools in this topic 8
Original MARPLA conceptual illustration: Roblox Home PTR and early exits: find the weak stage
Original conceptual diagram. Not a product interface or measured results.

Read the chain, not one number

Current Roblox documentation separates retrieval from ranking. Its core ranking-signal set includes PTR, first-play bounce, play days and playtime across several windows, co-play, qualified sessions, and monetization. Roblox does not publish exact signal weights. These signals use players acquired organically from Recommended for You. Sponsored CTR is a different measure.

Save the metric name and live tooltip because older qPTR material may describe a previous model. If impressions fall, align the change with PTR and bounce, but retain alternatives: platform demand, competition, and audience composition can also move distribution.

ObservationCheckNext action
Stable impressions, falling PTRPromise accuracy, legibility, segmentTest one thumbnail concept
Stable PTR, rising bounceLoading, spawn, promised actionRepair the demonstrated entry blocker
Stable entry, weaker returnPlay days, playtime, progressionTest the reason to continue
All averages move togetherSource, country, platform, maturityDecompose audience mix

Worked hypothetical example

Suppose Home impressions double, PTR moves from 4% to 3%, and plays rise from 400 to 600. First-play bounce increases only among mobile players in a newly reached country. This does not establish a failed thumbnail: expansion changed the mix while absolute plays rose. Check loading and the opening screen on representative devices for that segment, then compare performance inside a matching cohort.

If source × country × platform is not available as a joint breakdown, record the limit. Separate charts do not prove that the same players create the observed problem.

  1. Record the window, definition, and source of every metric.
  2. Compare impressions, PTR, and bounce without ad metrics.
  3. Review mature behavior windows and supported breakdowns.
  4. Choose one repair or test and preserve its date as a milestone.

Primary sources

Put this into practice in MARPLA

Discussion0

Loading comments…