Tracking visits and sales that come from AI assistants
When someone asks ChatGPT, Perplexity or Gemini for a recommendation and clicks a link in the answer, they land on your site as a visitor like any other. Those visits can be measured in the analytics you already have, and they're often worth separating out. This guide shows how to spot them, how to report on them, and what the numbers can't tell you.
Two different things to measure
AI shows up in your data in two ways, and it helps to keep them apart:
- AI agents visiting your site. Crawlers and assistants that read your pages, mostly without running your analytics tag. These only show up in server or CDN logs. See how to measure AI agent traffic.
- People arriving from AI assistants. A person reads an AI answer, clicks a link to your site, and browses in their own browser. Your analytics tag runs normally. This is AI referral traffic, and it's what this guide covers.
The first tells you whether AI can read and use your site. The second tells you whether that's turning into visits and sales.
How AI referrals show up
Analytics tools work out where a visit came from in two main ways: the referrer, which the browser sends to say which site the person came from, and campaign tags (UTM parameters) on the link itself.
Referrers
When someone clicks a link in a web-based assistant, the browser often sends that assistant's domain as the referrer. Domains you're likely to see include:
| Assistant | Referrer domains you may see |
|---|---|
| ChatGPT | chatgpt.com (older visits may show chat.openai.com) |
| Perplexity | perplexity.ai, www.perplexity.ai |
| Google Gemini | gemini.google.com |
| Microsoft Copilot | copilot.microsoft.com |
| Claude | claude.ai |
Treat this list as a starting point rather than a complete map. Assistants change domains, launch new apps and change how they link out, so check your own referral report for new sources every month or so.
Campaign tags
Some assistants add their own tag to outbound links. ChatGPT, for example, has been adding utm_source=chatgpt.com to many links in its answers. In your analytics that shows as the source chatgpt.com, sometimes with no medium, or alongside the referrer. Other assistants may do the same, or nothing at all.
Visits that arrive with no label
Not every AI referral announces itself. Mobile and desktop apps often open links without sending a referrer, privacy settings and browsers can strip it, and a person who copies a URL from an answer and pastes it into a new tab arrives as "direct". Some of your direct traffic is AI referral traffic you can't see. Treat any AI referral number as a floor, not a total.
Reporting on it in Google Analytics 4
Analytics tools have been changing how they group this traffic. In GA4's default channel grouping, AI assistants have typically ended up under Referral, mixed in with every other website that links to you. Check what your property shows today, because default channel definitions get updated. If AI referrals aren't already separated, two approaches work:
- A quick view. In the Traffic acquisition report, change the dimension to "Session source" and filter for the domains above. Good for a one-off look.
- A custom channel group. In Admin, under Data display, create a channel group with an "AI assistants" channel whose rule matches the session source against a pattern, and place it above Referral so it wins. Custom channel groups apply to your reports going back in time, so you see history too.
A source pattern to start from:
(^|\.)(chatgpt\.com|chat\.openai\.com|perplexity\.ai|gemini\.google\.com|copilot\.microsoft\.com|claude\.ai)$Use a "matches regex" condition on session source. Keep the pattern in one place, such as a shared doc, and add new assistants as they appear in your referral report. Other analytics tools work the same way: a rule on referrer or source that puts these visits in their own channel.
Google's own AI features are harder. Clicks from AI Overviews and AI Mode in Google Search generally arrive as ordinary Google organic traffic, and analytics can't separate them from classic search results. Search Console reports them as part of overall Search performance. Don't expect your "AI assistants" channel to include them.
What to measure
- Sessions and trend. AI referral sessions by assistant, week over week. The direction matters more than the size today.
- Landing pages. Which pages assistants send people to. Often it's product pages, comparison content or policy pages rather than the home page. Those pages now act as front doors, so make sure they convert.
- Engagement and conversion. Conversion rate, revenue and leads from the AI channel compared with search and other referrals. People arriving from an AI answer have often already been given a recommendation, so watch how their behavior compares.
- Assisted conversions. Someone may first hear about you from an assistant and buy a week later through a branded search. In GA4, compare attribution models or look at conversion paths to see where AI sources appear early in the journey.
The limits of attribution
Be honest with stakeholders about what this data can and can't show:
- It undercounts. App traffic and copied links arrive as direct. The real number is higher than what you see.
- It only counts clicks. Many AI answers mention a brand without a click. Someone who reads "Northwind has the best return policy" and later types your address directly is AI-influenced but won't appear here.
- It doesn't count agent purchases. When an assistant buys through an agentic commerce protocol, there may be no web session at all. Those orders show up in your commerce platform, so ask your platform how they're tagged.
- Browser agents blur the line. An agent browsing on someone's behalf may run your tag and look like a normal visitor. Some of what looks like human traffic may be agents.
Getting more AI referral traffic
Assistants recommend and link to sites they can read and trust. The groundwork is the same as for agent readiness: let AI search and assistant agents in through robots.txt, put key content in the HTML, describe products and prices with structured data, and make policy pages easy to quote. If you block OAI-SearchBot or PerplexityBot, don't expect referrals from ChatGPT search or Perplexity.
Then make sure the visits convert. The person arriving from an AI answer, or the agent acting for them, needs a page that works. AgentScore shows how your site looks to AI agents, and Ghost Agents test the journeys that turn a referral into a sale.