What 225 Million Simulated Website Visits Reveal About Traffic Failure Rates
We analysed 225.9 million simulated visits dispatched between July and November 2026. 0.47% failed - and 82% of those failures were our own analytics call timing out, not a site blocking the visit.
Quick answer
Between 10 July and 12 November 2026 our platform recorded 225,904,296 delivery events, and 0.47% of deliveries failed. 82% of everything we count as a failure is our own reporting call to Google Analytics timing out, not the target site refusing the visit.
Key takeaways
- Failure rate: 225.9 million delivery events, 0.47% failed - measured between 10 July and 12 November 2026.
- Main cause: 82% of those failures were our own analytics call timing out, not a website blocking the visit.
- Page depth: 95.8% of all visits were single-page, even though page depth is configurable on every campaign.
- Countries: Ten countries account for 70.5% of delivered volume; the platform covers 183.
Most writing about automated traffic argues from opinion. We have delivery logs, so we looked at our own.
Between 10 July and 12 November 2026 our platform recorded 225,904,296 delivery events across 4,882 projects. Not clicks on ads, not impressions - individual simulated browsing sessions dispatched to customer sites.
We expected the interesting number to be how often sites block us. It turned out to be something else.
0.47% of deliveries failed - and almost none of it was blocking#
| Outcome | Deliveries | Share |
|---|---|---|
| Delivered | 224,841,556 | 99.53% |
| Failed | 1,062,740 | 0.47% |
The reason matters more than the rate. Breaking down those 1,062,740 failures:
82% of everything we count as a failure is our own reporting call to Google Analytics timing out - not the target site refusing the visit. All proxy errors together, which is what a site's defences would actually disrupt, account for under 2%.
That has a practical implication for anyone buying traffic: if a vendor reports "98% success", ask what the denominator is. A vendor that never calls an analytics API will always report 100%, because it never measures anything.
95.8% of visits are single-page#
| Pages per visit | Share |
|---|---|
| 1 | 95.8% |
| 2 | 0.7% |
| 3 | 0.7% |
| 4 | 0.6% |
| 5 or more | 2.2% |
Almost every campaign we deliver is configured for a single page view. Page depth is available on every campaign; almost nobody uses it.
That matters for two reasons. A single-page visit with a short dwell time is the exact fingerprint analytics tools are best at spotting, and depth is one of the few levers a buyer actually controls. It also means "engagement" claims from traffic vendors deserve scepticism until you see a depth distribution, not just session counts.
Volume is heavily concentrated#
| Country | Deliveries | Share |
|---|---|---|
| United States | 40,695,448 | 18.0% |
| United Kingdom | 22,482,697 | 10.0% |
| India | 20,462,552 | 9.1% |
| Canada | 15,739,641 | 7.0% |
| Spain | 12,793,865 | 5.7% |
| Australia | 12,233,425 | 5.4% |
| France | 9,425,770 | 4.2% |
| Italy | 9,349,579 | 4.1% |
| Germany | 8,898,236 | 3.9% |
| New Zealand | 7,181,384 | 3.2% |
Those ten account for 70.5% of all volume. The platform covers 183 countries, but the long tail is thin: if a campaign needs meaningful volume from Portugal or Vietnam, that has to be planned, not assumed.
Top cities were New York, London, Los Angeles, Toronto, Mumbai, Chicago, Madrid, Bengaluru, Sydney and Barcelona.
Daily volume grew by half in four months#
October averaged 2.15 million deliveries a day, 52% more than July (1.41 million a day, counted from 10 July). That is our own growth, not the market's, and it says nothing about overall demand in this category.
What this data does and does not show#
It shows how often our delivery pipeline completed, why it failed when it did, how campaigns are configured in aggregate, and where the volume comes from.
It does not show how many of these visits appeared in a customer's Google Analytics. That depends on their own tagging, consent settings, filters and bot-detection configuration, which we neither control nor measure. A visit that is delivered and a visit that is counted are two different events, and conflating them is the most common mistake in this category.
It also does not show whether any of this affects rankings. We do not measure that and we do not claim it.
Methodology#
- Source: an internal daily aggregate table, queried read-only.
- Period: 2026-07-10 to 2026-11-12.
- Population: 4,882 projects with analytics reporting enabled. Projects without reporting are excluded, so the failure rate is calculated on recorded events, not on all dispatched work.
- A delivery event is one simulated browsing session that reached the status-recording stage.
- All figures are aggregate. No customer, domain or IP-level data is included.
- A "GA4 timeout" means our call to the Google Analytics endpoint exceeded its timeout - not that Google rejected the visit.
The takeaway#
If you are buying traffic, the useful question is not "what is your success rate" but "what do you measure, at which layer, and what happens when the measurement itself fails?"
In our case, four out of five failures were the measurement, not the delivery.
Questions about this article?
Spotted an error or an offer that has changed? Send us the source and we will check it and correct the article.