Agent Analytics
Agent Analytics
Understand crawler evidence scopes, provider adapters, and reporting limits.
Agent Analytics records how supported AI crawlers request or receive website content. It is separate from human Site Analytics and uses explicit evidence labels.
Evidence scopes
| Scope | What Optimly observed |
|---|---|
| Exact request log | A hosting provider or server reported the request and response status |
| Exact response observation | A supported edge adapter inspected bounded response characteristics |
| Near-time match | Application evidence was associated with a likely request, but cache layers may bypass it |
| Simulation | Optimly fetched the page in a controlled preview; this is not a live crawler visit |
Supported handoffs
- Vercel can use a JSON Log Drain for exact request evidence.
- Cloudflare and Netlify can use downloadable response-observing edge adapters.
- WordPress can use an installable plugin, labeled near-time because CDN cache hits may bypass the app.
- Custom programmable hosts can use the provider-neutral adapter.
- Platforms without supported response middleware can use simulation without claiming live observation.
Adapters are fail-open: an Optimly failure must not alter the customer's website response. Optimly does not collect response bodies or raw visitor IP addresses for Agent Analytics reports.
Agent access to a goal-relevant destination may be reported as goal-relevant agent activity. It is not a human goal-reaching session and cannot match browser-only clicks or form submissions.