# Read agent activity and AI referrals

> Separate agent fetches, customer-domain tool calls, and visits from AI answers in the Traffic view.

- Section: Guides
- Updated: 2026-10-07
- Canonical: https://knitknot.ai/docs/read-ai-traffic/
- Publisher: KnitKnot, the AI competitive positioning platform (https://knitknot.ai)

---

## At a glance

1. **Check agent activity**: See which agents requested your pages and whether their identity was verified.
2. **Check referrals**: Read visits from AI answers through your connected analytics source.
3. **Keep the counts separate**: A fetch, a tool call, and a visit measure different events.

Open **Traffic** in the [console](https://app.knitknot.ai/traffic/agents). It has separate views for requests from AI agents and visits by people coming from AI answers. Workspaces with customer-domain agent delivery enabled can also see tool calls. Keep the three counts separate when reporting results.

## Check which agents requested a page

1. Open **Traffic → Agent activity**.
2. Choose a time window and inspect the chart and page table.
3. Filter by operator or category, or search for a page path. Open a row to see that page's record.

The page table separates **verified** agent identity from a request that only claims an agent name in its user-agent string. Read the evidence label before attributing a request to an operator. This view counts requests to your pages; a request does not show that an AI answer cited the page or that a person visited it.

Agent activity comes from a connected Cloudflare zone. If it has not been connected, use [Connect workspace integrations](/docs/connect-workspace-integrations/). If a connection later needs attention, retained history can still be read, but new collection may stop until it is reconnected.

If an agent cannot fetch a page, use [Content → Access](/docs/check-agent-access/) to inspect crawler rules and page failures. A passing access check and an observed request are separate signals.

## Check visits from AI answers

1. Open **Traffic → AI referrals**.
2. Choose a time window and read the visit total, change from the prior window, and landing-page list.
3. Open a landing page to inspect its page record. If more than one analytics source is available, select the source you want to read.

AI referrals use the connected Google Analytics or Cloudflare data source. The view shows which source supplied the number and when it last synced. Google Analytics sessions and Cloudflare edge requests have different collection methods, so their totals are separate views of traffic. Do not add them together. If the view asks you to connect analytics or shows an import in progress, use [Connect workspace integrations](/docs/connect-workspace-integrations/) and wait for the first sync.

## If your workspace has Agent tool calls

**Traffic → Agent tool calls** appears when customer-domain agent delivery is enabled. It shows estimated calls to read-only tools such as `get_page`, `search_content`, and `get_facts`. Protocol handshakes are shown separately from tool usage. These counts are sample-weighted estimates; a tool call does not establish that an assistant used the returned text in an answer.

For the window controls, per-tool table, and missing-data states, follow [Read Agent tool calls](/docs/read-agent-tool-calls/).

To evaluate whether representation changed, use a later [benchmark](/docs/run-and-schedule-benchmarks/) and read the captured answers. Traffic helps explain reach, while benchmarks record what the AI actually said.

For an example of how these signals differ, read [Do AI crawler visits mean your page was cited?](/learn/do-ai-crawler-visits-mean-citations/).