Cloudflare Setup
:::summarybox achieve Create a Cloudflare API token with the right permissions Connect your zone to Trakkr Start receiving AI crawler visit data
Step 1: Create an API token
Cloudflare uses scoped API tokens to control access. You need a token with three specific read permissions.
- Go to dash.cloudflare.com/profile/api-tokens
- Click Create Token
- Choose Create Custom Token (not one of the templates)
- Set these permissions:
| Permission | Access |
|---|---|
| Zone > Analytics > Read | Lets Trakkr read per-zone crawler analytics (the row most setups miss) |
| Account > Account Analytics > Read | Lets Trakkr query Cloudflare's GraphQL analytics |
| Zone > Zone > Read | Lets Trakkr list your zones so you can pick one |
- Under Zone Resources, choose either All Zones or select specific zones you want to track
- Click Continue to summary, then Create Token
- Copy the token immediately - Cloudflare only shows it once
Don't use your Global API Key. It has full access to your entire Cloudflare account. A scoped token is safer and gives Trakkr only the read access it needs.
Step 2: Connect in Trakkr
- Navigate to the Crawler Tracking page in Trakkr
- Click Connect on the Cloudflare card
- Paste your API token and click Verify Token
- Select the zone (domain) you want to track
- Click Connect Zone
That's it. Trakkr will start pulling AI crawler visit data from your Cloudflare analytics within a few minutes.
Cloudflare's adaptive analytics are aggregate. On high-traffic zones, low-volume crawler traffic can be sampled or truncated. If you need per-request capture, deploy the optional Cloudflare Worker after connecting.
What Trakkr reads
With these permissions, Trakkr can only:
- List your zones (domain names and their plans)
- Read analytics (traffic data, including bot visits)
Trakkr cannot modify your DNS, firewall rules, caching settings, or anything else. The token is read-only.
Troubleshooting
"Failed to verify token"
- Double-check you copied the full token (no trailing spaces)
- Confirm the token has Zone > Analytics > Read, Account > Account Analytics > Read, and Zone > Zone > Read
- Make sure the token hasn't expired (check token settings in Cloudflare)
- If you restricted zone access, ensure the target zone is included
"Cloudflare denied analytics access for this zone"
The token verifies and your zones load, but analytics is rejected. Add the Zone > Analytics > Read permission to the token and reconnect: the Account > Account Analytics > Read row alone isn't enough on every account.
No zones appear after verification
- Your token may not have Zone > Zone > Read permission
- The token may be restricted to zones you don't have active
No crawler data after connecting
- Crawler data can take a few hours to appear
- Verify your site is proxied through Cloudflare (orange cloud in DNS)
- Check that you haven't blocked AI crawlers in Cloudflare's WAF or bot management rules
Revoking access
To disconnect at any time:
- Remove the connection in Trakkr (Crawler Tracking page)
- Optionally, revoke the API token in Cloudflare API Tokens
Neither action affects your website or its traffic.
Next steps
visibility|WordPress Setup|Connect WordPress for crawler tracking.|/learn/docs/features/traffic/crawlers/install#wordpress
ai|JavaScript Rendering|Ensure AI crawlers see your content.|/learn/docs/guides/javascript-rendering