ChatGPT referral traffic is the set of visits that reach your website when someone clicks a link inside a ChatGPT answer. For a practice, those visits are the closest thing to proof that being named by an assistant does anything. Searches for this are small but specific: "chatgpt referral" draws 170 searches a month, "chatgpt traffic" and "chatgpt analytics" 90 each, "ai traffic analytics" 40 and "ga4 ai traffic" 20 (Google Ads Keyword Planner data via DataForSEO, US, 12-month average to Sep 2026). This guide shows how to find these visits in Google Analytics 4 (GA4), group them with visits from other assistants, and connect them to calls, forms and bookings.
Why AI assistant visits are hard to see
Three things hide them.
First, they're scattered. A patient may click through from ChatGPT, Perplexity, Gemini, Copilot or Claude, and each arrives under a different source name. Unless you group them, each looks like a minor referrer.
Second, some arrive with no label at all. A link copied out of a chat and pasted into a browser carries no referrer, so GA4 counts it as Direct, which Google defines as arriving "via a saved link or by entering your URL" (Google Analytics Help (opens in a new tab)).
Third, Google's own AI features are counted as search. GA4 describes Organic Search as including "Google's AI Overviews and AI Mode," and its newer AI Assistant channel explicitly "excludes Google's AI Overviews and AI Mode." A patient who clicks a link in an AI Overview shows up as a normal Google visit.
The referrers to look for
When a referrer is passed, the session source in GA4 is the site the visitor came from. For the major assistants, that is the assistant's own web address:
| Assistant | Source value to look for |
|---|---|
| ChatGPT | chatgpt.com |
| Perplexity | perplexity.ai |
| Google Gemini | gemini.google.com |
| Microsoft Copilot | copilot.microsoft.com |
| Claude | claude.ai |
Check these against your own data before building anything: open Reports > Acquisition > Traffic acquisition, change the dimension to Session source, and search for each name. New assistants and new domains appear over time, so review the list every few months.
GA4 has started doing part of this for you. Its default channel group now includes an AI Assistant channel, which Google describes as "the channel by which users arrive at your site from sources like ChatGPT, Gemini, Deepseek, Copilot, or Grok." It works by setting the medium to "ai-assistant" when "the referrer matches a list of AI Assistants" (Google Analytics Help (opens in a new tab)). Google doesn't publish that list, so you can't confirm whether Perplexity or Claude visits are included. A custom channel group removes the guesswork.
Building an AI assistants channel group in GA4
You need Editor access or above on the property. Standard GA4 properties allow two custom channel groups with up to 50 channels each (Google Analytics Help (opens in a new tab)).
In GA4, go to Admin > Data display > Channel groups.
Click Create new channel group. GA4 starts you from a copy of the default group, so every existing channel is already there.
Name it something plain, such as "Channels with AI assistants".
Click Add new channel and name it "AI assistants".
Add a condition: Source · matches regex · and paste:
.*(chatgpt|openai|perplexity|gemini|copilot|claude).*The leading and trailing
.*let the pattern match the term anywhere in the source value, the same style Google uses in its own AI assistants example. Because it matches "chatgpt" anywhere, it also catches a link whose UTM source contains that word.Move the new channel above Referral (and above the built-in AI Assistant channel). Google's rule is that "traffic is included in the first channel whose definition it matches given the current order of channels in the group."
Save. Google says custom channel groups "can be applied to your reports retroactively," so past months fill in too.
Open Acquisition > Traffic acquisition and choose your new group as the primary dimension. "AI assistants" now appears as its own row.
For links you control, such as the website button on your Google Business Profile, add UTM parameters so those visits aren't confused with anything else.
Reading landing pages and conversions from AI traffic
Sessions alone don't tell you much. The useful questions are which pages AI assistants send people to, and whether those people then call, submit a form or click to book.
Mark the actions that matter as key events. In Admin > Data display > Events, click the star next to each event that represents a patient action, such as a contact form submission, a click on your phone number or a click on your booking link. Standard properties can mark up to 30 key events, and Google notes a new key event can take up to 24 hours to appear in standard reports (Google Analytics Help (opens in a new tab)).
Build a free-form exploration. Click Explore in the left navigation, start a blank exploration and choose the free-form technique (Google Analytics Help (opens in a new tab)). Google says custom channel groups are available as dimensions in explorations. Add:
- Dimensions: your AI assistants channel group, Session source, Landing page
- Metrics: Sessions, Key events
- A filter limited to the AI assistants channel
Illustrative example (fictional practice, made-up numbers): Northside Pediatrics in Raleigh sees 41 AI-assistant sessions in September. 22 land on the "sick visits" page, 11 on the home page and 8 on "newborn care". Four of those sessions include a click on the phone number. The team now knows which pages assistants are pointing to and checks that those pages show hours and a phone number above the fold.
Read the landing pages as clues about the questions being asked. If AI visitors keep landing on an old blog post rather than your service page, that post is what assistants are citing.
What GA4 misses, and why
Treat the AI channel as a floor, not a total.
- Visits with no referrer fall into Direct: pasted links, and possibly some in-app browsers.
- Google AI Overviews and AI Mode are counted in Organic Search. Search Console reports them in the Performance report, "within the 'Web' search type," mixed with ordinary results (Google Search Central (opens in a new tab)).
- Answers that never produce a click. A patient reads that you're open Saturdays, then calls or searches your name. That shows up as a call or a branded search, not as AI traffic.
- Crawlers and fetchers. OpenAI's ChatGPT-User, for example, visits pages for "certain user actions in ChatGPT" (OpenAI (opens in a new tab)). Those requests appear in server logs, not as patient visits in GA4. Keep the two counts separate.
- Consent and blockers. Visitors who decline analytics or block scripts aren't counted at all.
A HIPAA caution before you add tags
GA4 is not a place for patient information. Google says it "does not offer Business Associate Agreements in connection with this service" and that HIPAA-regulated entities "must refrain from exposing to Google any data that may be considered Protected Health Information (PHI)" (Google Analytics Help (opens in a new tab)). Tags on patient portals, intake forms or pages that tie a visitor to a specific condition need careful review. Our guide to Google Analytics and HIPAA covers which pages to keep tags off. This is general information, not legal advice. Confirm how it applies to your practice with a qualified advisor.
Reporting AI traffic next to search and ads
AI visits only make sense in context. A monthly view like this keeps them honest:
| Channel | Where the number comes from | What to compare |
|---|---|---|
| Organic Search | GA4, plus Search Console clicks (includes AI Overviews and AI Mode) | Sessions, key events |
| AI assistants | Your custom GA4 channel | Sessions, key events, top landing pages |
| Paid Search | GA4 and Google Ads | Key events, cost per key event |
| Direct | GA4 | Watch for growth after AI mentions rise |
| Referral | GA4 (now without AI assistants) | Directories and partner sites |
Compare key event rates rather than raw sessions: 40 AI visits with 4 calls may matter more than 400 search visits with 6. Pair this with weekly checks of what assistants say, explained in our guide to the AI visibility score, so you can see whether mentions and visits move together. For a broader GA4 setup, see GA4 for practices.
Medfy's first-party website analytics counts visits from AI assistants alongside calls, forms, bookings and directions, so the AI row sits next to the actions it led to. If you want to know whether assistants can read your site before you measure anything, the free marketing audit checks crawler access and asks Claude and Gemini whether they name your practice. For other ways to track what assistants say, see our overview of AI visibility tools.
Common mistakes
- Leaving the AI channel below Referral. It will stay at zero because Referral catches the traffic first.
- Expecting AI Overviews in the AI channel. GA4 counts them as Organic Search.
- Reading weekly swings in small numbers. Ten visits one week and four the next is noise. Look at months.
- Adding server-log bot hits to GA4 visits. Crawler requests aren't patients.
- Tagging intake or portal pages to "see everything." That trades a reporting convenience for a privacy problem.
Frequently asked questions
Can I see ChatGPT traffic in Google Analytics?
Yes, for visits that carry a referrer. GA4's default channel group includes an AI Assistant channel that Google says covers sources like ChatGPT, Gemini, Deepseek, Copilot and Grok. For full control, create a custom channel group with a regex that matches ChatGPT, Perplexity, Gemini, Copilot and Claude, and place it above Referral. Visits without a referrer still land in Direct.
Does ChatGPT pass a referrer?
It can. Google's AI Assistant channel in GA4 identifies visits by matching the referrer against a list of AI assistants, and Google names ChatGPT among them, so ChatGPT clicks that carry a referrer are recognized. A link copied out of a chat and pasted into a browser carries no referrer, and that visit is counted as Direct, with no trace of ChatGPT.
How much traffic do AI assistants send to practice websites?
There is no reliable benchmark for medical practices, and we don't quote one. It depends on specialty, city, how often assistants name you and whether their answers link to your site. Measure your own: build the AI assistants channel in GA4, compare its sessions and key events with Organic Search month by month, and remember that some patients read an answer and call without clicking.
Is AI referral traffic counted as direct traffic?
Only when the referrer is missing. GA4 assigns sessions with a recognized AI assistant referrer to its AI Assistant channel. Sessions with no referrer, such as a pasted link, fall into Direct, which Google defines as arriving via a saved link or by entering your URL. Some AI-assisted visits will always hide there, so treat your AI channel as a floor, not a total.