# [See the ChatGPT traffic your analytics may miss](https://rebilder.com/solutions/chatgpt-traffic)

- **Updated:** 2026-09-10
- **Description:** Measure ChatGPT requests and referred visitors with server-side reporting and the Rebilder Tag. See what was requested and what visitors did next.

See both the agents requesting information and the people arriving from ChatGPT. Server-side reporting and the Rebilder Tag cover different parts of that journey.



## What you get

- Both kinds of AI traffic, separated and counted
- Agent fetches by platform, from your own server logs
- Referred human sessions, and how they convert
- The answer rate: what you served against what you missed

## Two kinds of traffic, one name

When people say ChatGPT traffic they usually mean one of two things, and the distinction is not pedantic: they arrive by different mechanisms, are recorded by different systems, and are worth different amounts.

|  | Agent fetches | Referred humans |
| --- | --- | --- |
| What it is | The assistant requesting your page | A person clicking a link in an answer |
| Runs JavaScript | No | Yes |
| Browser analytics records | Direct fetches do not run its script | Yes, as a referrer |
| Where it is visible | Your server logs | Your analytics |
| Typical volume | Higher | Lower |
| What it is worth | It supplies information for evaluation | Direct conversion |

> **How the two reporting sources work together** Combine server-side request reporting with browser analytics. The gateway observes requests it handles; the Rebilder Tag records AI-referred visits and supported browser activity.

## Seeing the agent half

Use requests observed by your reporting integration. Review the configured routes and collection window so the report has a clear scope.

- **Requester classification.** Review observed headers and distinguish claimed identity from verified requests.
- **What you served each one**: the format, the size and the render time.
- **Your answer rate**: how many of those requests produced something useful.
- **The miss log**: the URLs they asked for and did not get, ranked by frequency.

The miss log is the one worth acting on first. It is a list of things the market asked you for, in the order it asked, which is a rarer artefact than it sounds.

## The referred half, and why it converts

Track visits referred by AI assistants alongside completed orders to understand how that traffic performs for your business. Keep those referrals separate from agent requests to your server.

Requests show which information agents retrieve; referrals show subsequent visits. Track both to connect information gaps with customer discovery.

## How much traffic does ChatGPT send?

It depends entirely on your category, and any single published figure is describing somebody else’s site. The measurable version is your own: count agent fetches in your server logs and referred sessions in your analytics, and treat them as two separate numbers.

## Why does my analytics show no ChatGPT traffic?

Combine server-side request reporting with browser analytics. The gateway observes requests it handles; the Rebilder Tag records AI-referred visits and supported browser activity.

## Is AI traffic worth having?

Track visits referred by AI assistants alongside completed orders to understand how that traffic performs for your business. Keep those referrals separate from agent requests to your server.

## Should I block AI crawlers?

Choose access settings for the agents and uses you want to support. Review existing bot rules and test their effect before changing them.

## Related

- [GPTBot](https://rebilder.com/solutions/gptbot)
- [ChatGPT SEO](https://rebilder.com/solutions/chatgpt-seo)
- [AI visibility tracking](https://rebilder.com/solutions/ai-visibility-tracking)
- [AI agent user agents in your logs](https://rebilder.com/learn/ai-agent-user-agents)
- [How the gateway classifies agent traffic](https://rebilder.com/docs/classification)
- [The Rebilder Tag](https://rebilder.com/docs/tag)