Connect Your Akamai DataStream 2
Henneth receives AI bot traffic data from your Akamai CDN via DataStream 2 webhooks. This guide walks you through configuring your Akamai DataStream 2 stream to push log data to Henneth's ingestion endpoint. Setup takes about 10 minutes.
Prerequisites
- An active Akamai account with DataStream 2 enabled
- Permission to create or modify DataStream 2 configurations in Akamai Control Center
- Your property (domain) configured in Akamai
- Access to your Henneth dashboard (Enterprise plan)
Get your webhook credentials from Henneth
Log in to your Henneth dashboard and navigate to Settings → Integrations.
Locate the Akamai card. You'll see the description: "Receive AI bot traffic data via Akamai DataStream 2."
Henneth provides three credentials you'll need for the Akamai configuration:
Credentials are pre-generated
Unlike other integrations, your Akamai webhook credentials are generated by Henneth when your account is provisioned. You don't need to create tokens or API keys — just copy and paste.
Configure DataStream 2 in Akamai
Log in to Akamai Control Center and navigate to DataStream 2.
Create a new stream or edit an existing one, and configure it with these settings:
Custom HTTPSPaste the Webhook URL from Step 1Basic AuthPaste the username from Step 1Paste the password from Step 1JSON30 secondsData fields — include the following datasets:
- Log Info — Timestamps, request IDs, and log metadata
- Message Exchange — Request and response headers, status codes, and body sizes
- Request Header — User-Agent strings, Accept headers, and other request metadata Henneth uses to identify AI agents
- Network — Client IP, edge server location, and connection details
Activate the stream configuration after saving.
Verify data is flowing
After activating your DataStream 2 configuration, return to your Henneth dashboard. The Akamai card will show a Waiting for data status badge (yellow) until the first data payload arrives.
Once Henneth receives and processes the first batch of log data, the status will change to Connected (green). This typically takes 1–5 minutes after activation, depending on your traffic volume.
If the status remains at "Waiting for data" for more than 15 minutes, check the Troubleshooting guide.
What Henneth does with your Akamai data
Once connected, Henneth processes your DataStream 2 logs to:
- Identify AI agent traffic — Detect requests from ChatGPT, Gemini, Perplexity, and other AI crawlers by analyzing User-Agent strings and request patterns
- Measure crawl volume — Track how often AI agents visit your site and which pages they access
- Enrich visibility scores — Combine crawl data with AI platform response data for a complete picture of your brand's AI visibility
- Power audit reports — Surface technical issues that may affect how AI agents access and interpret your content
Initial historical data processing may take up to 24 hours. Real-time data will appear in your dashboard within minutes of each 30-second push.
Security and credentials
Basic Auth over HTTPS
All data is transmitted over TLS-encrypted HTTPS. The Basic Auth credentials authenticate each request to ensure only your Akamai stream can push data to your endpoint.
Credential storage
Your webhook username and password are encrypted at rest using AES-256 encryption. They are never logged in plaintext, and the password is masked in the Henneth UI after initial setup.
Credential rotation
If you need to rotate your credentials (e.g., after a team member leaves), contact [email protected] to generate new webhook credentials. After receiving new credentials:
- 1.Update the username and password in your Akamai DataStream 2 configuration
- 2.Activate the updated configuration
- 3.Verify data is still flowing in your Henneth dashboard
Disconnecting
Click the Disconnect link at the bottom of the Akamai card to stop processing incoming data. Note that Akamai may continue sending data to the webhook URL until you also deactivate the stream in Akamai Control Center.
Deactivate in both places
To fully disconnect, deactivate the DataStream 2 stream in Akamai Control Center and click Disconnect in Henneth. Doing only one will result in either failed deliveries (Akamai side) or ignored data (Henneth side).
Next steps
- Permissions — understand exactly what Henneth can and cannot access
- Troubleshooting — fix common issues with data delivery and processing