Cloudflare Analytics Connection Guide
Use a read-only API Token to see traffic and security right at the edge — before requests ever reach your server.
Sign up for freeWhy connect Cloudflare to ClickSentinel?
If your website runs through Cloudflare, every request passes through Cloudflare's edge network before reaching your origin server. ClickSentinel reads this data via the GraphQL Analytics API to show real traffic, cache efficiency and blocked threats — a view Google Analytics simply doesn't have.
The connection uses a narrow-scoped API Token (Zone → Analytics → Read) that you create yourself on Cloudflare — not OAuth, since Cloudflare doesn't support OAuth for personal API access. Data is only available if the domain is actually running on Cloudflare's infrastructure (DNS proxy enabled).
- Measured at the edge — catches traffic before it reaches your origin server
- Track Cache Hit Ratio to see how much load is taken off your origin server
- Threats Blocked directly supports ClickSentinel's own fraud detection
Key concepts
Requests & Page Views
Requests is the total number of HTTP requests Cloudflare handled; Page Views is the count of actual HTML page loads.
Cache Hit Ratio
The share of requests served from the Cloudflare cache instead of hitting the origin server — the higher, the lighter the load on your server.
Threats Blocked
Requests Cloudflare automatically blocked as suspected attacks or malicious bots — a useful cross-signal for fraud detection.
Zone ID vs API Token
The Zone ID identifies the correct domain to pull data for; the API Token is the authentication key — always create it with the minimum permission (read-only Analytics).
How it works
- 1Sign in to dash.cloudflare.com, pick the domain to connect, and copy the Zone ID from the Overview tab (a 32-character string).
- 2Go to My Profile → API Tokens → Create Token, and create one with the minimum "Zone → Analytics → Read" permission.
- 3Go to Cloudflare in ClickSentinel, pick a Site, paste the Zone ID and API Token, then click Connect.
- 4The system verifies the token before saving it; once connected, data syncs automatically every day at 3:25 AM.