How do I measure traffic and leads coming from ChatGPT and other AI tools?

AI assistants send visitors two ways: people who click a link in an answer, and people who read an answer and later come to your site by another route. Analytics can count the first group reasonably well. Measuring it is the reporting side of AI SEO, or generative engine optimisation (GEO): it tells you whether being cited turns into visits and enquiries.

Can I track AI search referrals in Google Analytics 4?

Yes. GA4's default channel group includes an AI Assistant channel. When a visit's referrer matches Google's list of AI assistants (Google's examples include ChatGPT, Copilot, DeepSeek and Grok), GA4 sets the medium to ai-assistant and counts the session in that channel.

To see it, open Reports > Acquisition > Traffic acquisition and look for the AI Assistant row. Change the dimension to Session source / medium to see which assistant each visit came from.

Two limits to know:

• Google's own AI features aren't in it. Clicks from AI Overviews and AI Mode count as Organic Search, and GA4 can't separate them. Our guide to Google AI Overviews covers what Search Console shows instead.
• Google decides the list. If an assistant your buyers use isn't on it, its visits land in Referral instead.

How do I set up my own AI channel in GA4?

If you want to control the list, create a custom channel group. You need the Editor role on the property.

1. Go to Admin > Data display > Channel groups and choose Create new channel group.
2. Add a channel named, for example, "AI assistants", with the condition Source matches regex and a pattern such as the one below.
3. Move it above Referral. GA4 puts each visit in the first channel whose rule it matches, so a channel placed below Referral never receives anything.
4. Save the group. Custom channel groups apply to your reports retroactively, so you can see past months too.

.*(chatgpt\.com|openai\.com|perplexity\.ai|claude\.ai|copilot\.microsoft\.com|gemini\.google\.com|deepseek\.com).*

A property can have two custom channel groups (five on GA4 360). Review the pattern every few months, because assistants change domains and new ones appear.

How do I count leads, not just visits?

Visits say little on their own. To count enquiries by channel:

• Mark your enquiry as a key event. Use the form's submit event or the thank-you page view, then add the key events column in Traffic acquisition.
• Store the source with the lead. Many form tools can save the landing page, referrer and any utm_ tags in hidden fields, so each enquiry in your inbox or CRM shows where it started.
• Ask. A short optional "Where did you hear about us?" field catches the people who read an AI answer and then searched for your name, which no analytics tool can attribute.

Why is AI traffic undercounted?

• Most answers end without a click. If the answer names you and the reader searches for your brand later, the visit shows as organic search or direct.
• Some clicks arrive without a referrer, for example from some desktop and mobile apps, and land in Direct.
• Some visitors block analytics. Cloudflare, for example, notes that ad blockers and the Brave browser block its analytics beacon; the same applies to other analytics tags. Cloudflare Web Analytics also doesn't record query strings, so it can't show UTM tags.

Treat the AI Assistant channel as a floor, not a total. The trend over months tells you more than any single number.

What should I report each month?

Keep it to a few numbers you can compare month to month: AI-assistant sessions, the key events (enquiries) from them, the share of all enquiries they represent, and the landing pages they arrive on. The landing pages show which content is being cited and clicked.

Traffic only shows the visits. To find out whether AI assistants mention your brand at all, and who they name instead, request an AI visibility audit.