ThriveStack citedbyAI search attribution learning guideIntroductionLive demoBook a demoStart free
Lesson 4.6 · Agentic and AI browser traffic

AI browser and agent traffic:
how to tell people from bots

Three kinds of AI visit reach your site: a person clicking from an answer, a person browsing in an AI browser such as Comet or ChatGPT Atlas, and an AI agent fetching a page for a user. Only the first is reliably counted. Report the three separately so agent fetches do not inflate human numbers.

Direct

where ChatGPT Atlas visits often land, or (not set)

MarTech, Nov 2025, via the ThriveStack engine guide
perplexity.ai

the referrer the Comet browser passes

MarTech, Nov 2025, via the ThriveStack engine guide
ThriveStack citedby

Three kinds of AI visit reach your site, and only the first is reliably counted

Diagram of AI visit types and where each one shows. Not measured data.

KIND OF AI VISITWHAT HAPPENSWHERE IT SHOWSClick from an AI answerA person taps a link in ChatGPT, Gemini orPerplexityReferrer or utm_source, or direct if strippedAI browser visitA person browses in Atlas or CometComet passes perplexity.ai. Atlas often lands asdirect or (not set)Agent fetchAn AI agent reads your page for a user requestServer logs, as a user-query bot. Often no analyticsevent

Diagram. Atlas and Comet behaviour from MarTech (Nov 2025) and the ThriveStack engine guide.

How to read it. Treat the second and third as separate lines in your report. Count person-driven visits and agent fetches together and the numbers will mislead.

In ThriveStack citedby Human visits and bot hits are shown side by side, split by bot type, so agent fetches do not inflate the human numbers. See it for your site →

AI browsers send people, and agents send themselves.

Comet passes a perplexity.ai referrer. Atlas often strips it and lands as direct or (not set), per MarTech (Nov 2025). An agent fetch may leave no analytics event at all.

ThriveStack citedbyResearch table

How AI browsers pass a source

How AI browsers pass a source
BrowserWhat your analytics sees
Comet (Perplexity)perplexity.ai referrer
ChatGPT Atlas logoChatGPT AtlasOften direct or (not set)
Source: see sources belowthrivestack.ai/citedby · Nov 2026

Server logs show agent fetches, so read user query bots separately.

User query bots fetch a page when a person asks a question. They appear in logs, not in analytics. In the demo workspace, user query bots made 2,034 visits in a week (sample data).

Where each signal lives
  • Human visits: GA4
  • Agent and bot fetches: server logs
  • Citations: prompt panel

Segment human and agent visits so one cannot inflate the other.

Mixing them makes AI traffic look larger than it is, or hides human visits inside bot counts.

  1. 1

    Tag human AI browser visits

    Use referrers and UTMs on people.

  2. 2

    Tag AI agent and bot visits

    Use user agent in logs.

  3. 3

    Report human and agent visits apart

    Two lines, never one blended number.

Expect AI browser behavior to change, because these products are new.

Behaviour as of Nov 2025 and Oct 2026 may change with each release. Date every finding.

Date every finding

Write "as of" and the date next to any claim about a browser. Test after each release.

How ThriveStack citedby helps

ThriveStack citedby runs your prompt panel across 10+ AI engines, reads server-log crawler hits, matches human visits to signups and reports AI-sourced and AI-influenced pipeline.

Build my AI attribution report →

AI browser traffic, answered.

How does ChatGPT Atlas traffic appear in analytics?

Often as direct or (not set), because the referrer is stripped.

Does Comet pass a referrer?

Yes, a perplexity.ai referrer.

How do I count agent traffic?

Read user query bots in server logs and keep them separate from human visits.

Sources for this lesson

  1. ThriveStack citedby research: Which AI engines send utm_source (Oct 2026), citing MarTech (Nov 2025)

Figures were checked against each page in Nov 2026. Vendor studies are marked by their sample. Charts marked sample data are illustrations.

All 10 questions this lesson answers

How to track ChatGPT Atlas traffic

Atlas is built on Chromium and its user agent matches Chrome, so it looks like a normal visitor. Referrers are often stripped, so its visits tend to land in Direct. You can only see it indirectly, through direct visits to deep pages and a source question on forms.

Track Comet browser visits

Comet usually passes a referrer, so clicks often show as perplexity.ai and referral in GA4. Its user agent also looks like Chrome. In agent mode it acts inside the user's own session, so it appears as ordinary human traffic.

AI agent traffic vs human traffic

A human clicks a link and reads. An agent acts for a human, by comparing, filling forms or buying. Cloud agents such as ChatGPT agent sign their requests. In-browser agents such as Atlas and Comet run scripts like a person and give no clear identity.

How to identify AI agent visits in analytics

Use layers. Verify signed requests where agents offer them, match known crawler user agents in server logs, and watch behavior such as very fast page sequences. In-browser agents cannot be reliably detected today, so report them as a range, not an exact count.

ChatGPT agent mode traffic tracking

ChatGPT agent signs each outbound request with HTTP Message Signatures (RFC 9421). Requests carry Signature, Signature-Input and a Signature-Agent header set to https://chatgpt.com. Check them against the public keys at chatgpt.com/.well-known/http-message-signatures-directory. Cloudflare verifies them for you.

AI shopping agent attribution

An agent may read your product pages while the buyer never visits. Analytics then sees a quick bounce, or nothing at all. Attribute at the order level instead. Ask how the buyer found you, and log agent fetches in server logs. ThriveStack citedby tracks AI visits alongside the pages involved.

Agentic commerce attribution

The Agentic Commerce Protocol, built by OpenAI and Stripe, defines how a purchase completes. It does not cover discovery or attribution, so you add your own measurement. Store the order source on every order. ThriveStack Revenue Intelligence links Stripe billing events with other account signals.

AI browser referrer missing

The ChatGPT mobile app hands links to the system browser, which drops the referrer. Atlas also suppresses it, and links with noreferrer send none. Add UTMs where you control the link, and use a short How did you hear about us question to catch the rest.

AI agent conversions tracking

An agent that runs your scripts fires conversion tags like any browser, so the conversion counts as human. Flag conversions that look unusually fast or scripted, and check them in the CRM before you count them as pipeline. Server side confirmation of orders helps.

MCP traffic tracking

Model Context Protocol (MCP) lets AI apps call tools on your server. It is not page traffic, so pageview tools do not see it. Log each tool call, the client, the session, latency and errors at the server. ThriveStack citedby also offers an MCP server so assistants can read its data.

Sources, checked November 2026: HUMAN Security: ChatGPT Atlas · HUMAN Security: Atlas vs Comet · MarTech: GA4 and Comet, Atlas · OpenAI: ChatGPT agent allowlisting · Stripe: Agentic Commerce Protocol · Sentry: MCP observability.

Go deeper
MapHover to open