导航|地址|刷新
Detection IDs

Skip to contentDocumentation Index
Fetch the complete documentation index at: https://developers.cloudflare.com/bots/llms.txt
Use this file to discover all available pages before exploring further.

Docs Directory API SDKs Changelog

Search

Log in

Bots

/

Overview

Plans

Get started

Bot Fight Mode

Super Bot Fight Mode

Bot Management

Concepts

Bots

Overview

Verified bots

Bot scores

Bot tags

Bot Feedback Loop

Bot detection engines

Additional configurations

JA3/JA4 fingerprint

Overview

Signals Intelligence

Detection IDs

Overview

Account takeover detections

Scraping detections

Additional detections

JavaScript detections ↗

Sequence rules

AI LabyrinthBeta

Block AI Bots

Custom rules

robots.txt setting

Static resource protection

Bot Analytics

BotBase

Attribution Business Insights

Workers templates

Delay action

Account Abuse ProtectionEarly Access

Troubleshooting

Bot Management skips

Super Bot Fight Mode for WordPress

False positives

Reference

Bot verification methods

Web Bot Auth

IP validation

Bot Management variables

Machine Learning models

Bot Detection Alerts

Sample terms

Glossary

Changelog

Agent resources

Agent setup ↗

Cloudflare Skills ↗

Code Mode MCP Server ↗

Domain-specific MCP Servers ↗MCP

Bots llms.txt ↗

Bots llms-full.txt ↗

Cloudflare Docs llms.txt ↗

Cloudflare Docs llms-full.txt ↗

Home

/Bots

/Additional configurations

/Detection IDs

Detection IDs

Last updated May 6, 2026|Copy as Markdown|View as Markdown|Agent setup

OverviewDetection tagsCreate or edit an expressionUse cases Block requests that match a specific detection ID Run Bot Management without specific detection IDsBot Detection IDs via LogpushAvailability

Detection IDs are static rules that detect predictable bot behavior with no overlap with human traffic. Each ID maps to a specific detection method such as heuristics, verified bot detections, or anomaly detections. For example, a detection ID can identify when a client sends headers in a different order than what its claimed browser would use.

If you are having an issue with one of our heuristics, detection IDs allow you to decide which heuristics to enforce on your zones using customer configurable heuristics. You can choose unique actions for different bots, detected through Cloudflare’s heuristics engine. You can block, allow, or serve alternate content to specific bots to meet the unique needs of your site’s traffic.

Note

A request can trigger multiple detection IDs.

You can use cf.bot_management.detection_ids fields in tools such as:

Custom rules

Advanced Rate Limiting

Transform Rules

Workers (as request.cf.botManagement.detectionIds)

Bot Detection IDs and tags are also available in Bot Analytics and Security Analytics.

Beta detections

Cloudflare may occasionally try beta detections as we continuously improve our detections.

It is possible, but uncommon, for you to have beta detection IDs on the Cloudflare dashboard that are not actively collecting data on your zone.

------

Detection tags

Detection tags refer to the category associated with the detection ID at the time that Cloudflare has fingerprinted a bot. For example, if a detection tag is go, this means that Cloudflare has observed traffic from that detection ID from a Go programming language bot.

Note

Detection tags are available in Security Analytics, but not in the Security Events.

------

Create or edit an expression

In the Cloudflare dashboard, go to the Security Analytics page.
Go to Analytics ↗

Apply filters and select Create custom security rule to create a custom rule based on your filters.

Alternatively, if you have already created a custom rule, you can go to the existing rule in Security rules and edit the expression based on your filters.
Go to Security rules ↗

Use the cf.bot_management.detection_ids field in the rule expression.

Select Deploy.

Log in to the Cloudflare dashboard ↗, and select your account and domain.

Go to Security > Bots, apply filters and select Create custom rule to create a custom rule based on those filters. Alternatively, if you already created a custom rule, go to Security > WAF > Custom rules and edit the expression of an existing custom rule.

Use the cf.bot_management.detection_ids field in the rule expression.

Select Save.

------

Use cases

Block requests that match a specific detection ID

any(cf.bot_management.detection_ids[*] eq 3355446)and not cf.bot_management.verified_botand http.request.uri.path eq "/login"and http.request.method eq "POST"

Run Bot Management without specific detection IDs

cf.bot_management.score lt 30and not cf.bot_management.verified_botand http.request.uri.path eq "/login"and http.request.method eq "POST"and not any(cf.bot_management.detection_ids[*] in {3355446 12577893})
------

Bot Detection IDs via Logpush

You can create or edit existing Logpush jobs to include the new Bot Detection IDs field which will provide an array of IDs for each request that has heuristics match on it. The BotDetectionIDs field is available as part of the HTTP Requests dataset and you can add it to new or existing jobs via the Logpush API or on the Cloudflare dashboard. This is the primary method to discover Detection IDs.

In the Cloudflare dashboard, go to the Logpush page.
Go to Logpush ↗

Select Create a Logpush Job.

Select and enter the destination information.

Select HTTP Requests as the dataset.

Select BotDetectionIDs under the General data field category.

Prove the ownership.

Select Save.

Update your logpush job by adding BotDetectionIDs to the output_options: parameters.

------

Availability

Detection IDs are available for Enterprise Bot Management customers.

PreviousSignals Intelligence NextAccount takeover detections

Was this helpful?

YesNo

Edit page Report issue

On this page

Overview

Detection tags

Create or edit an expression

Use cases

Block requests that match a specific detection ID

Run Bot Management without specific detection IDs

Bot Detection IDs via Logpush

Availability

Edit page Report issue

Getting started
PlansContact salesPartnersFind a partnerStartupsUnder attack?Domain name search

Company
AboutCareersInvestorsPressPress kitGlobal network

Public interest
Project GalileoAthenian ProjectCloudflare for CampaignsProject FairshotImpact/ESG

Compliance
Compliance resourcesTrust HubData ProtectionResponsible AITransparency reportReport abuse

Resources
App innovation reportCloudflare RadarCase studiesStatusSupportEventsBlog

Developers
DocumentationLearning centerCommunity

Solutions
SSE and SASE platformCloudflare AI CloudAI SecurityFrontend Development PlatformMulti-Tenant Platform DevelopmentWeb Security Platform

Start BuildingLog In

© 2026 Cloudflare, Inc.

Privacy policy|Report security issues|Terms of use|Trademark
|
Your privacy choices

Docs

------
导航页打开网址