Overview
The Agent Traffic tool in Scrunch lets you monitor how much access your site is getting from LLM bots — including ChatGPT, Perplexity, Gemini, Grok, and others. Akamai Cloud Monitor broadcasts your traffic logs (via the push API) so you can feed them into Scrunch in near-real-time.
If your website is proxied by Akamai, then Cloud Monitor is a viable solution (even though it is legacy) to stream traffic and get actionable metrics from LLM bots.
What You’ll See
Once your Akamai Cloud Monitor feed is connected, the Agent Traffic dashboard in Scrunch will show:
Total Bot Traffic in the last period
Bot traffic over time
Traffic distribution between Retrieval, Indexer, and Training LLM Bots
Comparison between the current period and the last period (%)
Top bot agents and when they were last seen
Top content pages accessed by LLM bots
Recent bot requests
A date filter to see data from the last 24 hours, last 7 days, or last 30 days
Scrunch AI's Agent Traffic feature allows customers to granularly track which AI platforms are consuming their content (and for what purpose) to enable better understanding of how their content:
will be surfaced in AI platforms like ChatGPT
drives AI responses to relevant questions
and ultimately how it influences AI to describe and recommend their brand, products and services and click through to their site(s).
Before You Get Started
Verify that your Akamai property is proxied and supports the Cloud Monitor instrumentation behavior. If your setup already uses DataStream 2 or newer streaming logs, you may consider migrating instead.
Ensure you have permissions to edit the property in Akamai’s Control Center (Property Manager) and activate new versions.
Adding Your Website
Open the Scrunch app.
Navigate to the Agent Traffic menu.
You’ll see the list of websites already connected to Agent Traffic.
Click + Connect Site at the top.
Select Akamai CloudMonitor as your CDN platform.
A dedicated instructions page will appear, showing your Webhook URL and API Key.
Your page will look like this one:
ℹ️ Each site has its own endpoint and key. Don’t reuse them across different sites or integrations.
Integrating Akamai CloudMonitor
1. Enable Cloud Monitor Instrumentation
In Akamai Control Center → locate your property → go to Property Manager:
Click “Create new version” of the property.
Under the Policies section, select Add Rule → choose Cloud Management (or equivalent legacy rule category).
Under the new rule, select the behavior Cloud Monitor Instrumentation.
Configure the fields:
Enable: turn instrumentation ON
Connector Type: Default
Data Sets to Include: HTTP and GEO
Save the version but do not activate yet.
2. Configure Cloud Monitor Data Delivery
While still editing your property version:
Add another rule (or within the same Cloud Management rule) for Cloud Monitor Data Delivery.
Fill out:
Delivery Hostname: this is the host to which Akamai will push logs (e.g., an endpoint provided by Scrunch or your own HTTP listener).
Delivery URL Path: the HTTP path Akamai should use (for example
/ingest/your-endpoint).If your ingestion endpoint uses HTTPS, ensure your property is configured with HTTPS as required by Akamai.
Save.
3. Activate the Property Version
Review the changes and then Activate the new version
Once validated, activate on Production.
Ensure logs are flowing to your endpoint and data is arriving without errors.
4. Verify Traffic
Wait up to 5 minutes for your site to show as “Active” in Scrunch.
If you don’t see traffic, test with:
curl -v -H "User-Agent: ScrunchAI-Testbot" https://yourdomain.com
This will send a sample request to confirm logs are flowing.
👉 Once configured, your site will continuously stream traffic logs to Scrunch, giving you real-time visibility into how LLM bots interact with your content.
Maintain & Troubleshoot
Because Cloud Monitor is legacy, monitor for deprecation notices from Akamai.
Periodically review whether migrating to DataStream 2 or newer may offer better performance or additional fields.
If logs stop flowing, check Akamai property version status, endpoint certificate validity, delivery hostname routing, and token/auth parameters.
Repeat these steps for every new website