Journey needs 1,000 premium sessions, not just 1,000 visits
586 words · about 3 min · Updated
In a hypothetical 30-day period with 2,000 total sessions and a 40% qualifying share, only 800 sessions count toward a 1,000-session threshold. Journey’s current requirement refers to premium sessions; total worldwide visits are not a substitute.
- How it was measured
- We checked Journey’s current help page and Mediavine’s updated Journey announcement on 2026-10-19, then computed explicitly hypothetical traffic-share examples. The share values are invented sensitivity inputs, not observed country mixes or a reproduction of Journey’s private eligibility assessment.
- Last checked
Two thousand total sessions can still fall short of a thousand qualifying sessions. At a hypothetical 40% qualifying share, the relevant count is 800, not 2,000.
That arithmetic is simple. The difficult part is knowing what the application actually counts. Journey's current minimum-requirements page specifies at least 1,000 premium sessions over 30 days and says applicants connect GA4 for evaluation.
Mediavine's updated Journey announcement describes the threshold in terms of sessions from tier-1 markets and gives the US, Canada, UK and Australia as examples. Those examples are not an exhaustive country list or a public implementation of its approval rules.
Three numbers that should not be mixed
| Number on your screen | What it counts | Can it replace the requirement? |
|---|---|---|
| Users | People as counted by the analytics system | No; the stated threshold is sessions |
| Pageviews | Page loads or views recorded | No; a session can include several |
| Total sessions | All recorded visits in the chosen period | Not necessarily; the requirement narrows the traffic population |
A country breakdown is useful for understanding the audience. It does not prove that every session from a named country meets the provider's definition of premium, nor does a large worldwide total guarantee acceptance.
What the traffic mix changes
These shares are invented inputs for a sensitivity calculation. We are not claiming to know your qualifying share or Journey's internal assessment.
| Assumed qualifying share | Total sessions needed to yield 1,000 |
|---|---|
| 20% | 5,000 |
| 40% | 2,500 |
| 60% | 1,667 |
| 80% | 1,250 |
| 100% | 1,000 |
Required total sessions = round up(1,000 / qualifying share)
Example: round up(1,000 / 0.40) = 2,500The table explains why there is no universal worldwide-session shortcut. It is not an eligibility calculator: the qualifying share is precisely the unknown that a public homepage scan cannot establish.
Check your data before applying
- Choose a complete 30-day reporting period and record its start and end dates.
- Confirm you are reading sessions, not users or pageviews. Record the GA4 property and reporting time zone too.
- Examine session counts by country and source to understand the audience composition. Treat that as context, not a certificate of premium traffic.
- Check that the connected analytics property is the one collecting the website you are applying with. A missing tag or wrong property can make your records disagree.
- Use the application dashboard's decision and explanation for the actual eligibility result. If its count differs, ask which dates and definition were used rather than buying traffic to reach a headline number.
The help page also makes clear that traffic quantity is only one part of review: content, audience quality and technical fit matter. Reaching a number does not establish approval.
Journey's traffic gate and Mediavine's revenue gate are separate
Do not turn these sessions into advertising dollars with a universal RPM. The Journey-to-Mediavine comparison explains the separate revenue requirement and the limits of a historical RPM scenario.
If you already earn from advertising, session RPM versus page RPM helps you avoid comparing different units. If you want to inspect the sample behind our earnings scenarios, use the downloadable page-RPM data.
Evidence grade: B. The current threshold is provider-published, and the arithmetic is repeatable. We have no access to the provider's private eligibility model or your analytics, and the illustrative shares are not measured audience data.
Tracked as JOURNEY-PREMIUM-SESSION-COUNT. If a number here looks wrong, tell us and we will check it against the source.