Bot Analytics is available to selected workspaces. Ask your Slate contact to turn it on for your workspace.
Before You Start
- Your website runs through Cloudflare.
- You can create API tokens in that Cloudflare account.
- You have the Admin role in your Slate workspace. Other people see “Ask a workspace admin to connect Cloudflare.”
- Logpush is turned on for the Cloudflare account. If it isn’t, Slate tells you during the install. See Troubleshooting.
Step 1: Create an API Token
- Open Insights → AI Visibility, then select Bot Analytics under Website.
- Click Connect Cloudflare. The Connect Cloudflare dialog opens on API token.
- Click Open Cloudflare ↗. Cloudflare opens the page for creating a token. Under Zone Resources, pick your site’s zone.
- Give the token these permissions on the zone:
- Create the token in Cloudflare and copy it. Cloudflare shows it only once.
- Back in Slate, paste the token and click Check.
- Click Continue.
Step 2: Choose the Zone and Hostnames
- Under Zone, choose your site’s zone.
- Under Hostnames to count, select the hostnames whose bot visits Slate should count. Each shows its traffic a day over the last 7 days. Slate preselects your main domain and its
www.version when they have traffic. - Click Install.
Step 3: Install
Slate shows each step as it finishes:- Logpush job created: a job in your Cloudflare account that sends bot requests only, and skips static files such as images and scripts.
- Cloudflare reached Slate: Cloudflare sent its check file to Slate.
- Last 30 days imported: Slate brings in daily totals for the 30 days before you connected.
Check That Data Is Arriving
The status next to the page title shows the connection:
Click the status to see details: the hostnames, the last delivery, and the bot requests in the last 24 hours.
While the 30-day import runs, a banner says Importing your last 30 days from Cloudflare. Live bot visits are counted already. If the import fails, admins can click Retry importing.
About the imported days
The imported days are daily totals from Cloudflare Analytics. They’re approximate, and Slate can’t check them against each company’s IP addresses. From the moment you connect, Slate checks every request. The chart marks where live data starts.Troubleshooting
Cloudflare doesn’t recognise this token. Cloudflare shows a token only once. Create a new token and paste it. This token can’t see any zone. In Cloudflare, add your site’s zone under Zone Resources for the token. The token can’t send logs. In Cloudflare, edit the token, add Zone › Logs › Edit, then click Check again. Logpush isn’t turned on for this Cloudflare account. In Cloudflare, open the zone, then Analytics & Logs › Logpush, and turn it on. Then click Try again. Cloudflare wants billing turned on. Logpush on this account needs a payment method first. Add one in Cloudflare, then try again. Cloudflare refused a change. Check that the token has Logs › Edit on this zone, then try again. The status shows No data. Most often, the site’s DNS record in Cloudflare was switched to DNS only (grey cloud), so requests no longer pass through Cloudflare. Turn the proxy back on for the record.Your Website in Settings
Connecting Cloudflare also adds your website to Settings → Website, marked as yours. Admins find it in Workspace settings under Growth.Website Tracking
Some workspaces also have Website tracking in Workspace settings, under Growth. It is a separate tracker: a script you add to your site’s pages. Bot Analytics doesn’t use it. Bot Analytics counts only the visits Cloudflare sends. To add the script:- In Website tracking, click Add domain. Enter a domain like
example.comand click Add domain. Add each subdomain separately. - Copy the snippet in Install tracking on your domain, and add it to every page of the site, just before
</head>. - Publish your site, then click Check now.
What’s Next
- Bot Analytics: read the visits, pages, and errors
- Pages: the page list New pages uses