Last updated: Nov 14, 2025
Agent Traffic shows which AI crawlers are visiting your site, which pages they hit, and why they came. Scrunch reads logs directly from supported CDN providers. This article outlines all supported integrations and what to do if your CMS or hosting platform does not expose logs directly.
Supported Integrations
Scrunch supports the following CDN and hosting environments. Each option delivers accurate AI crawler logs so Scrunch can classify retrieval, training, and indexing traffic.
Provider / Option | Best For | Cost | Notes | Documentation |
Cloudflare Workers (Free Plan) | Small sites and simple setups | Free | Runs on Cloudflare Free plan. Good for low to moderate traffic. | |
Cloudflare Workers (Paid Plan) | Mid-sized sites or higher Worker execution needs | $5/mo plus $0.30 per million requests after first 10M/mo | Strong fit for growing sites and agencies with multiple brands | |
Cloudflare Logpush (Enterprise Plan) | Enterprise teams; customers with existing CF Enterprise plan | Enterprise contract | Most reliable setup. No incremental log cost once on Enterprise | |
WordPress | WordPress sites | Free | Via WordPress plugin. May alternatively use CDN integration if preferred. | |
Vercel | Sites deployed on Vercel | Requires Vercel Pro or higher plan; $0.50 per GB of log data. | Direct integration. Vercel Log Drain provides required data. | |
Akamai DataStream 2 | Enterprise sites on Akamai | Enterprise contract | Real time logs for precise AI crawler classification | |
Akamai Cloud Monitor | Existing Akamai customers using Cloud Monitor | Enterprise contract | Alternative Akamai-based path if DataStream is not enabled |
Workarounds for Unsupported CMS and Hosting Platforms
Some CMS platforms do not provide raw CDN logs. Scrunch offers clear workarounds so you can still enable Agent Traffic without changing your CMS.
In most cases, the recommended pattern is simple.
Put Cloudflare in front of your site, then use Cloudflare Workers or Cloudflare Enterprise Logpush.
Platform | Why Native Integration Is Not Possible | O2O Support | How To Enable | Key Notes |
Webflow | No access to CDN or origin logs | Yes | Create a proxied CNAME | Uses your Cloudflare zone first, then Webflow’s. Works on any Cloudflare plan. Supports WAF, Bot Management, caching, Rules. Cloudflare docs: Webflow O2O, How O2O works. |
Shopify | Shopify does not expose request logs | Yes | Create a proxied CNAME | Checkout path disables Workers and Snippets. Shopify zones receive optimized Cloudflare configs. Works on any plan. Cloudflare docs: Shopify O2O, Product compatibility. |
BigCommerce | No log access from BigCommerce origin | Yes | Create a proxied CNAME | Full Cloudflare feature set applies before traffic reaches BigCommerce. Any Cloudflare plan works. Cloudflare docs: BigCommerce O2O, Product compatibility. |
Squarespace | No server logs available | Partial (Proxy) | Move DNS to Cloudflare and set record to Proxied | Not an official O2O partner, but Cloudflare proxying enables Workers and Logpush. |
Wix | No raw request logs | Partial (Proxy) | Move DNS to Cloudflare and enable Proxied mode | Enables Worker based integration. Good reliability for AI bot detection. |
HubSpot CMS | HubSpot does not provide request logs | Partial (Proxy) | Proxy traffic through Cloudflare | Gives Scrunch the logs required for Agent Traffic. |
Uberflip | Uberflip hosted hubs do not surface logs | Partial (Proxy for subdomains) | Proxy the Uberflip subdomain through Cloudflare | Common pattern for |