How does Cloudflare AI Crawl Control compare with Agent Tracking?

What edge analytics does well

Cloudflare AI Crawl Control sees requests handled by Cloudflare, including cache hits that never reach an origin log. It provides crawler controls, request metrics and, on supported plans, referral analytics. Its free-plan crawler identification uses user-agent strings; advanced detection requires Bot Management. Check the current plan details before comparing specific features.

What still needs browser or server events

Assistant referrals can appear in edge or browser analytics. A WebMCP call inside the browser needs on-page instrumentation; a confirmed booking needs a separate site-server receipt. Cloudflare's edge view requires its proxy; Agent Tracking can run with other hosting arrangements.

What Agent Tracking covers

Identifiable assistant referrals, origin-log fetches with supported verification and burst grouping, instrumented tool technical outcomes, browser goal attempts and distinct site-server receipts. The browser script alone cannot observe remote tools or crawler requests.

Compare the datasets

If both are installed, compare the same time window and HTML paths. Counts can differ because the edge sees cache hits and blocks, while an origin log sees only requests that reach the server. Use Agent Tracking for on-page tool and goal events if those matter. The full measurement guide shows how to keep the signals separate.

In short