Cloudflare says it denied analytics access when I try to connect my site to Trakkr. What permissions does the token need?
Updated June 30, 2026 · Reviewed by [email protected]
This means the Cloudflare API token you created doesn't have the right scopes. Trakkr's Cloudflare connection reads zone-level analytics, so the token needs both Account > Account Analytics: Read and Zone > Zone: Read permissions, scoped to the specific zone (domain) you're connecting.
Create a new token in the Cloudflare dashboard under My Profile > API Tokens with exactly those two permissions, then reconnect using that token. A token created for a different purpose (like DNS editing) won't have analytics access even if it otherwise looks valid.
Related questions
- Can I install crawler tracking on a site that isn't Cloudflare, Vercel, Netlify, or WordPress (like Wix, Framer, or a custom PHP site)?
- AI Pages says "Waiting for First Request" and the scan just keeps spinning. Is that normal?
- Connecting my Vercel-hosted site to crawler tracking keeps failing. What's going on?
- Why does Trakkr say my site is blocking AI crawlers when I can see GPTBot traffic getting through in my own logs?
- Crawler tracking shows visits from some AI bots (like Meta or Mistral) but not others (like ChatGPT or Perplexity), even though I know those engines have visited. Is tracking broken?