Traffic
Where players come from
Loading…Campaigns & placements
How attribution works
Visits are visible browser arrivals, grouped into 30-minute sessions. Known automation is excluded; browsers are not verified people. Link requests include previews and repeat requests and are shown separately.
Played means at least two saved plies; Finished excludes aborted games. Player milestones are credited once to their first recorded source, using the players first attributed in the selected period. Signups include guest upgrades. Returned means a later measured session at least 24 hours after first arrival. Existing accounts can enter this measured cohort. Later direct visits preserve the last tagged source.
A shared bio link identifies a platform, not the video that prompted the visit. Typed homepage visits and missing referrers appear as Direct / unknown. Reports start when tracking is enabled; prior traffic cannot be reconstructed. Browser identifiers expire after 30 days and measurement records after 90 days. The traffic-scope and client-category controls below do not change this player report.
Activity
What’s happening
Where from
Responses
Explore details
Client types
All activities
Countries & clients
All responses
API routes & files
More statistics
HTML loads
Estimated visits
Requests
Page loads and visits include bots and tests.
Countries
Devices
Browsers
How traffic numbers work
Browser traffic is not a confirmed human count. Automation includes headless browsers and scripts. Crawlers includes verified services and unverified crawler claims; expand Client types to separate them.
Countries locate connections, not people. Referrers and unique humans aren’t available in the Cloudflare traffic dataset. Reads can be preloads or refreshes; writes aren’t necessarily completed games or puzzles. Game bots counts runner/operator connections, not moves.
The 13 October production audit alone recorded 12,921 browser requests. Tests without an automation signature remain in Browsers.
Cloudflare data can be sampled. Percentages use classified requests. Data refreshes every 20 seconds, with caching and processing delay. No IPs, player IDs or raw user agents are published.