MONOPOLY GO! Prediction Check: The Successor Fleet Arrived on Schedule — and the June 18 Cohort Refuses to Die

#MONOPOLY GO! Prediction Check: The Successor Fleet Arrived on Schedule — and the June 18 Cohort Refuses to Die

By the AdMapix Research Team — data as of August 25, 2026

Eighteen days ago, in our MONOPOLY GO! ad strategy teardown, we did something UA content rarely does: we published a prediction that could fail in public. Reading Scopely's operating rhythm from raw creative timestamps — generations launched weeks apart, hero creatives retired in synchronized sweeps near the 60-day mark — we wrote:

"The June 18 cohort, which turned 50 days old on August 7, is due for its own reset in late August or early September, and a successor batch should surface in the index before that happens. Anyone can check this claim against public data in a month."

It has been most of a month. We checked. This is the honest scorecard: one half of the prediction confirmed ahead of schedule, one half still inside its window — but already bending the model that produced it.

#TL;DR — The Scorecard at August 25

• ✅ "A successor batch should surface first" — confirmed, three times over. New launch cohorts appeared on July 22, July 27, and July 29-31, and a July 27 creative is already the #2 US video by 30-day delivery. Then August went further: ~100 new video files launched between August 12 and August 24, in daily batches as large as 23 files.
• ⏳ "June 18 cohort reset in late August / early September" — not yet, and now historic. All six June 18 durations (8s / 13s / 22s / 29s / 30s / 34s) were still live on August 25 — day 68. That is past the 60-67 day age at which every previous hero generation was cut.
• 🆕 Something the model didn't predict: the August flood introduces durations MONOPOLY GO! has never run at scale in the US — 59s, 83s, and 94s cuts — a long-format experiment layered on top of the usual 8-35s band.
• The verdict window closes in early September. Either the reset lands and the cadence model survives with a wider tolerance — or the June 18 cohort becomes the first generation allowed to age past 70 days, and the "fixed ceiling" parameter gets rewritten.

#Part 1: The Succession — Confirmed Early and Then Some

The prediction's logic was that Scopely never retires a hero generation before its replacement is live and proving itself. That part of the model has been over-fulfilled. Since the original snapshot (August 7), the US index shows three distinct pre-August launch waves, followed by an August cascade:

Two readings jump out. First, the July 29-31 launch wave landed within about 48 hours of the July 29 sweep that retired the May generation — the launch-sweep-launch interlock we described is visible again, at minute-level precision. Second, the August volume is not normal succession: roughly a hundred new video files in thirteen days is several times the cohort size of any generation we documented in the original teardown. Combined with the brand-new 59-94 second durations, this looks less like the next rotation and more like a format-expansion program running alongside it — YouTube-style long cuts entering a mix that had lived almost entirely under 35 seconds.

For UA teams, the transferable observation is unchanged but now better-evidenced: this advertiser builds the successor fleet before touching the incumbent one, every single time.

#Part 2: The Reset That Hasn't Happened — Day 68 and Counting

Here is the more interesting half. The six June 18 creatives — the single-day duration experiment (8, 13, 22, 29, 30, 34 seconds) that anchored the original piece — were all still delivering in the US on August 25, their 68th day. So was a seventh June 18 file (27s) that launched with the batch but never made the original top 15:

*The index also surfaces June 18 files beyond the six that made the original top 15 — the cohort was launched wider than its chart presence suggested. Impressions are AdMapix modeled estimates over the trailing 30-day window, not lifetime totals.

Why this matters: in the original data, no hero creative survived past 67 days at full intensity. The May generation was cut at 60-67 days in one synchronized 31-minute operation, while still averaging tens of millions of daily impressions. That consistency is what made "~60-day ceiling" a model parameter rather than an anecdote — and the June 18 cohort has now outlived it.

The prediction window itself is still open; "late August or early September" runs through roughly September 7. But the cohort has already done something no predecessor was allowed to do, which leaves exactly two endings:

1. The sweep lands in the next ~two weeks. The cadence model survives, with the ceiling revised from "~60 days" to "~60-75 days" — a tolerance, not a constant. Watch for the signature: multiple June 18 creatives sharing a final timestamp within the same hour.
2. The cohort keeps running past mid-September. The fixed-age policy is falsified, at least for this generation — and the most likely explanation becomes visible in Part 1: with a hundred August files absorbing the testing budget and long-format cuts entering the mix, Scopely may have shifted from replacing winners on schedule to stacking new formats on top of proven ones.

Either ending teaches more than a confirmed guess would have. That is the point of publishing falsifiable reads: when the data breaks your model, the break is the finding.

#What We Got Right, What We're Revising

Held up: succession-before-retirement (confirmed three times); the launch-cohort structure (August batches are single-day, multi-duration launches — same fingerprint as June 18); the sweep mechanics (July 29's synchronized shutdown remains the template).

Under revision: the 60-day ceiling as a fixed constant. Day 68 with all six creatives live already forces a wider tolerance band, whatever happens next.

Genuinely new: the long-format experiment. 59s, 83s, and 94s files at this account's scale have no precedent in our window, and their arrival alongside a record-volume month suggests a placement-mix shift the next teardown should quantify properly.

We will publish the final verdict once the window closes. The check itself took about five minutes against the live index: one product filter, one country, one sort by first-seen. If you want to run the same falsifiable-prediction loop on your own competitors — read their cadence, write the date down, check it in a month — an AdMapix account gets you the same live data this series is built on.

#FAQ

What was the original prediction?

That MONOPOLY GO!'s June 18 creative cohort would be reset (retired in a synchronized sweep) in late August or early September 2026, and that a successor batch would appear in the creative index before that reset — based on the rotation cadence visible in the account's timestamps.

Did it come true?

Half confirmed, half pending. Successor batches arrived on schedule (July 22, July 27, July 29-31, then ~100 files across August 12-24). The reset itself has not happened as of August 25 — the June 18 creatives are on day 68, past the 60-67 day age that ended every previous generation.

What are the 59-94 second creatives about?

They are new to this account's US mix, which previously lived almost entirely at 8-35 seconds. Long cuts at 59/83/94 seconds are consistent with a long-format placement push (YouTube-style inventory), but the data shows arrival, not intent — we flag it as the thing to quantify next.

Are these numbers official Scopely data?

No. All figures are AdMapix modeled estimates built from public creative-index data — first-seen/last-seen timestamps and 30-day delivery estimates. They describe observable ad behavior, not internal budgets or performance.

#Related Reading

• MONOPOLY GO! ad strategy teardown — the original analysis and prediction
• Ad strategy teardowns (series index) — every advertiser in this series
• Royal Match ad strategy teardown — the opposite playbook: 305-day creatives, zero resets