AAEOsrcStart with AEO →

Measurement

How to Measure Traffic and Customer Discovery From AI Assistants

7 min read · Reviewed July 26, 2026

Stock market chart displayed on a laptop screen
Photo by Markus Winkler on Unsplash

AI assistants can influence how someone discovers a company long before that person reaches its website. Some of that activity appears as referral traffic in analytics. Much of it does not. Measuring the channel well requires combining click-based analytics with direct feedback from customers, clients, and leads.

Direct answer

Traffic labeled AI Assistant represents visits that arrived through a recognized link from an AI assistant. It does not represent every time an assistant mentioned or recommended the business. A customer may discover a company through ChatGPT, Claude, Gemini, Perplexity, Copilot, or another assistant, then arrive later through Google, a typed URL, email, a phone call, or another device. Analytics and customer-reported discovery therefore measure different parts of the same journey.

What AI Assistant traffic measures

Google Analytics introduced a dedicated AI Assistant channel in May 2026. When the referrer matches a recognized AI assistant, Google Analytics can assign the medium ai-assistant, place the session in the AI Assistant default channel, and use (ai-assistant) as the campaign name.

Google’s default channel documentation currently describes AI Assistants as visits from sources such as ChatGPT, Gemini, DeepSeek, Copilot, or Grok. It excludes traffic from Google AI Overviews and AI Mode, which means the channel should not be interpreted as a complete record of all AI-influenced search activity.

The key word is visits. An analytics platform can normally classify an AI referral only after a person clicks a link and reaches the website with referral information that the analytics system recognizes.

Trackable journey

ChatGPT includes a source link → the user clicks it → the website loads → analytics recognizes the referrer → the session appears under AI Assistant.

What the channel does not measure

The AI Assistant channel is useful, but its name can suggest broader coverage than it provides. It does not show every appearance of a brand, page, product, or professional inside an AI-generated response.

It generally cannot tell you:

  • How often an assistant mentioned or recommended the organization without producing a click.
  • The exact prompt that led to the recommendation.
  • The full wording or context of the generated answer.
  • Whether the user copied the company name and searched for it elsewhere.
  • Whether the user returned later by typing the URL or using a bookmark.
  • Whether the person changed devices before visiting.
  • Whether an AI recommendation contributed to a phone call, email, store visit, or offline conversation.

This is not a defect unique to AI traffic. Web analytics has always had difficulty measuring discovery that occurs before the final click. AI assistants make the gap more visible because they can provide a recommendation inside a conversation without requiring the user to visit the cited source immediately.

AI influence can appear under another channel

One of the most important measurement problems is that the assistant may create the interest while another channel receives the credit.

01

Search later

An assistant names a business. The user later searches for that name, so analytics records Organic Search.

02

Visit directly

The user remembers or copies the address and returns later, so the visit may appear as Direct.

03

Contact offline

The user calls, visits, or emails without clicking a tracked link. Website analytics may record nothing.

04

Switch devices

The recommendation occurs on one device and the visit or conversion occurs on another, breaking the visible path.

A 2026 observational study linked opt-in conversations from ChatGPT, Claude, and Gemini with subsequent web activity. When an assistant recommended a brand to someone with no recent observed engagement, later same-name Google searches and visits to the brand’s website increased. The study did not observe completed transactions and should not be treated as proof that every mention creates a sale. It does, however, demonstrate why last-click and referrer-based measurement can assign assistant-influenced behavior to another channel.

When customers say an AI assistant mentioned you

Businesses should treat comments such as “ChatGPT recommended you” or “I found you through an AI assistant” as meaningful first-party attribution data. The comment identifies an influence that a normal acquisition report may never reveal.

Broader consumer and B2B research supports the idea that this behavior is becoming part of real decision-making. Adobe has reported substantial growth in traffic from generative AI sources and found consumers using generative AI for research and product recommendations. Accenture describes generative AI as moving from a utility toward a guide in consumer-brand relationships. Gartner reported in 2026 that 45% of surveyed B2B buyers had used AI during a recent purchase, while a later survey found many buyers wanted sales representatives to validate AI-generated information.

These findings do not tell us how often a particular company is recommended. They do show why customer statements about AI discovery should not be dismissed as an unusual edge case.

How to find AI Assistant traffic in Google Analytics

In Google Analytics, begin with an acquisition report that uses the Session default channel group dimension. Look for AI Assistant, then break the traffic down using dimensions such as session source, landing page, device category, country, or new versus returning user.

Useful questions include:

  • Which assistants are sending recognizable visits?
  • Which pages receive those visits?
  • Are visitors arriving on articles, product pages, service pages, or the homepage?
  • Do they engage differently from visitors from Organic Search or Referral?
  • Do they complete key events, submit forms, start trials, purchase, call, or subscribe?
  • Are a few valuable sessions being hidden by a very small overall traffic total?

Because channel definitions and recognized referrers can change, use the source and medium dimensions alongside the default channel rather than relying only on the channel label. Historical traffic may also have been classified differently before the dedicated channel existed.

Evaluate quality, not only volume

AI referral traffic is often much smaller than mature channels such as organic search. Comparing raw session totals alone can make it look insignificant. The better comparison examines what visitors do after arrival.

MetricWhat it can reveal
Landing pageThe subjects, products, or services assistants are connecting to the site.
Engagement rate and timeWhether the visitor found the landing page relevant enough to continue.
Key-event rateWhether AI-referred visits lead to meaningful actions.
Revenue or lead valueWhether a small number of visits contributes disproportionate value.
New-user shareWhether assistants are introducing the organization to unfamiliar audiences.
Assisted outcomesWhether the visit participates in a longer path before conversion.

Adobe’s analyses have found AI-referred visitors showing strong engagement in several industries and periods. Those results are useful evidence that the channel can contain qualified visitors, but they should not be treated as a universal conversion benchmark. A publisher should compare its own AI Assistant traffic with its own baseline.

Ask customers how they first discovered you

Analytics should be paired with a simple customer-reported attribution question. The wording should ask about the beginning of the discovery process, not merely the final click.

Recommended question

How did you first hear about us?

  • Search engine
  • AI assistant, such as ChatGPT, Claude, Gemini, or Perplexity
  • Social media
  • Recommendation from a person
  • Article, video, or podcast
  • Advertisement
  • Other

If the person selects AI assistant, an optional follow-up can produce information unavailable in analytics:

Optional follow-up

Which AI assistant did you use, and what were you asking it?

The answer can reveal the assistant, the customer’s original language, the need that started the search, and the subject the assistant associates with the business. It can also reveal whether the assistant supplied a link, named the organization without a link, compared it with competitors, or encouraged the customer to verify the recommendation elsewhere.

The question can appear in a lead form, checkout survey, onboarding flow, intake call, sales conversation, or post-purchase survey. It should remain optional when requiring it would add unnecessary friction.

Build a combined measurement view

No single report fully measures AI-driven discovery. A practical system combines several signals.

  1. Track recognizable referrals. Monitor AI Assistant sessions, sources, landing pages, engagement, and conversions.
  2. Record customer-reported discovery. Add AI assistant as an attribution choice and preserve useful follow-up responses.
  3. Monitor branded demand. Watch for changes in branded search, direct visits, calls, and other paths that may follow recommendations.
  4. Review citation visibility separately. Test important prompts and record where the brand or pages appear, recognizing that visibility is variable.
  5. Connect evidence carefully. Treat correlations as clues rather than proof that one assistant mention caused a conversion.

The goal is not to force every customer into one perfect attribution path. It is to understand enough of the journey to make better decisions about content, visibility, and customer acquisition.

Common interpretation mistakes

  • Assuming AI Assistant equals every AI mention. It measures recognized referral visits, not total recommendation visibility.
  • Assuming Direct means no prior influence. Direct traffic can include journeys whose earlier source is unavailable.
  • Expecting analytics to reveal the prompt. Standard referral data does not expose the user’s conversation.
  • Confusing human referrals with crawler activity. AI crawling and a person clicking from an assistant are different events.
  • Comparing only session volume. A small channel may still produce valuable leads or introduce new audiences.
  • Generalizing industry benchmarks. Retail or travel findings may not describe a B2B service, publisher, or local business.
  • Ignoring what customers say. Direct customer feedback may be the only evidence that an assistant influenced the decision.

Key takeaways

  • AI Assistant traffic represents recognizable clicks from supported assistants, not every AI-generated mention.
  • AI recommendations can lead to later organic searches, direct visits, calls, emails, and other paths credited elsewhere.
  • Customer-reported attribution is necessary to understand discovery that analytics cannot observe.
  • Measure landing pages, engagement, lead quality, and conversions rather than focusing only on session totals.
  • Combine analytics, customer feedback, branded demand, and citation testing without pretending the result is perfect causal attribution.

Research

Sources

Documentation, survey findings, and published research used to prepare this article. Platform definitions and channel rules can change.

  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7
  8. 8