Skip to content
AI search

Bot Tracker: Connect Cloudflare

5 min read · Updated Nov 22, 2026

Read search and AI crawler visits from your Cloudflare analytics once a day, with a token you create and no log upload. Counted by user agent. Starter and up.

Bot Tracker shows how often search and AI crawlers ask for each page of your site. If your site is behind Cloudflare, PerfBee can read those visits from your Cloudflare analytics once a day, with a token you create. You do not upload a log file. Cloudflare tells PerfBee which user agent made a request, not the address it came from, so these visits are counted by user agent only and are never shown as verified. The connection is part of Bot Tracker, on the Starter plan and above, and costs no credits.

Before you start

  • Your site must be behind Cloudflare. The address of the site must belong to a zone in your Cloudflare account.
  • Be the workspace owner. Only the owner can connect, test or disconnect Cloudflare. Everybody else in the workspace sees the state of the connection and the numbers, and cannot change them.
  • Your Cloudflare plan must give access to request analytics. If it does not, PerfBee says so on the card.

Create the token

  1. In Cloudflare open My Profile, then API Tokens, then Create Token and Create Custom Token.
  2. Give the token these two permissions. Both only read: Zone > Analytics > Read and Zone > Zone > Read.
  3. Under Zone Resources choose Include, Specific zone and the zone that holds your site.
  4. Create the token and copy it. Cloudflare shows it only once.

Connect

  1. Open Bot Tracker for the site (in the site menu, as a tab of AI Readiness, or as a tab of Site Crawler) and find the Connect Cloudflare card.
  2. Paste the token into Cloudflare API token and press Connect Cloudflare.
  3. PerfBee checks the token with Cloudflare and looks for the zone that holds your site. If it finds it, the card shows the zone name and the state Connected.

PerfBee never shows the token again, and the field is empty after you press the button. The first read of the last days runs in the background and can take a few minutes. The card says Reading now while it runs. If Cloudflare refuses the token, the card says why, in plain words, and PerfBee keeps nothing.

What PerfBee reads

  • The zone that holds your site's address. Each question PerfBee sends to Cloudflare carries the token, the host name of your site and the names of the ten crawlers.
  • Once a day, for the days it has not read yet: how many requests came from search and AI crawlers, grouped by page address, crawler and response status group (for example success, redirect, not found, refused, server error).
  • It reads back as far as your plan keeps its history, up to 30 days, as long as Cloudflare still has the data.

What PerfBee does not read

  • IP addresses. PerfBee never asks Cloudflare for them.
  • Visitor data. It reads no cookies and no content of any request or page, and no query strings.
  • Anything it could change. PerfBee only asks Cloudflare questions. It never changes your Cloudflare account.

What PerfBee keeps

  • The token, encrypted. It is never shown again and never appears in an answer, a log or an error.
  • The zone name, the state of the connection and the time of the last read.
  • For each day, the number of requests of each crawler to each page address, by status group. PerfBee keeps the name of the crawler, not the user agent text, and no single request. Cloudflare cannot tell a real crawler from a client that only claims to be one, so PerfBee keeps the page address of those visits too.
  • Those counts stay for as long as your plan keeps its Bot Tracker history, at most 365 days. PerfBee's nightly clean-up deletes the older days.

PerfBee uses the counts only to show you the crawler visits of your site. The details are in the Privacy Policy.

Why these visits are "user agent only"

Anybody can send the name of a crawler. A visit that says it is Googlebot may come from another program. When you upload a server log, PerfBee checks the address of each visit against the addresses the crawler's operator publishes, and only those visits count as verified. Cloudflare gives PerfBee no address, so it cannot check. That is why every number from Cloudflare carries the label User agent only, is never counted as verified, and is kept apart from the numbers of an uploaded log. Cloudflare may also sample busy days, and then its counts are estimates.

Test, disconnect and what happens to your data

  • Test connection asks Cloudflare again with the stored token. If a token was stopped because it lost a permission, a passing test brings it back.
  • Disconnect asks you first, then deletes the token and every count PerfBee read from Cloudflare for this site. Visits from uploaded server logs stay. The page addresses that only those counts used are removed at the latest in PerfBee's nightly clean-up.
  • Deleting or switching off the site in PerfBee, changing its address to one the zone does not hold, or closing your account does the same. If PerfBee cannot finish that deletion at once, its nightly clean-up finishes it, at the latest the next night.
  • If your plan no longer includes Bot Tracker (a plan change, an ended subscription or an ended trial), PerfBee stops reading from Cloudflare and keeps the token and the counts for 30 days. If your plan has not come back by then, PerfBee deletes the token and every count it read from Cloudflare, as if you had disconnected. If your plan comes back before then, nothing is deleted.
  • If you delete the token in Cloudflare, PerfBee can read nothing new. The counts it already read stay until they pass your plan's history limit, or until you disconnect.

If something stops working

  • Needs a new token: Cloudflare refused the token or one of its permissions. Create a new token with the two permissions above and press Connect again.
  • None of the zones holds this site's address: the token does not cover the zone of the site. Check Zone Resources when you create it.
  • The plan does not give access: your Cloudflare plan does not offer the request analytics PerfBee reads.
  • Cloudflare is limiting the account or did not answer: PerfBee tries again later. Nothing for you to do.
  • The card is missing: the connection is not open for your workspace yet.