Did that lead come from ChatGPT?
You can see AI assistants naming you. You cannot see whether any of it turned into a lead. Here is what GA4 already records, where the trail breaks, and the four fields that carry it into the CRM.
By Daria Dovzhikova · September 2026 · Updated October 2026
The short version
- GA4 has an AI Assistant channel. It needs no setup, and it undercounts, because some assistants drop the referrer.
- Without a key event on the action that makes a lead, no channel gets credit for anything. Check this first.
- Carry four fields into the CRM: first-touch channel, first-touch referrer, landing page, and what the buyer says when you ask.
- Crawler logs and citation counts measure exposure. They do not measure leads.
The question people are actually asking
A B2B marketer on r/SEO put it plainly: has anyone traced a real B2B lead back to ChatGPT or Perplexity recommending them? Their company pays for a tool that counts AI mentions and still cannot say whether the mentions produce pipeline. Another thread calls AI crawler traffic a useless KPI on its own, and a third asks whether 700 citations mean anything when the answer named the site five times.
The stakes are real. In a G2 survey of 1,076 B2B software buyers published in April 2026, 51% said they start software research in an AI chatbot more often than in Google, up from 29% a year earlier. If that is where the shortlist gets written, the measurement has to reach that far.
What GA4 already tells you
GA4's default channel group includes an AI Assistant channel: sessions that arrive from sources like ChatGPT, Gemini, Copilot, Deepseek or Grok. Open Reports, Acquisition, Traffic acquisition, and it is a row in the table. Nothing to install.
On this site, over the 28 days to 20 September 2026, AI Assistant was 48 of 405 sessions. The number that matters is next to it: 1 minute 28 seconds of average engagement, against 14 seconds for organic search and 9 seconds for direct. These are few visits from people who already asked a specific question and were sent to a specific page.
Where the trail breaks
Break one: the referrer. An assistant inside a mobile app, an in-app browser, or a link the buyer copied into a new tab arrives with no referrer. GA4 files it under Direct. You cannot get those sessions back, and you should not try to estimate them with a multiplier. Note it and move on.
This break is narrowing. ChatGPT adds UTM parameters to links in answers grounded in web sources, and on 1 October 2026 Search Engine Journal reported that Gemini has started doing the same. A parameter survives the in-app browser that strips a referrer, so more of these visits now arrive labelled. Google has not documented when Gemini adds it, so treat the count as a floor that is rising, not as complete. If you buy ads inside an assistant, tag them yourself, or the paid clicks land in the same row as the unpaid ones: ChatGPT ads conversion tracking covers that.
Break two: the key event. GA4 assigns credit to a channel only for events you have marked as key events. When I audited this site in September, the Key events column read zero for every channel. The booking link was an outbound click that GA4 recorded as a generic click and nobody had told it that click was the conversion. One custom event fixed it, with no code: event name equals click, link_url contains the booking domain, marked as a key event. If your Key events column is empty, nothing downstream of it can be true.
Break three: the form. The lead lands in the CRM as a name and an email. The session that produced it stays in GA4. Six weeks later nobody can join the two.
Four fields that carry it into the CRM
| Field | Where it comes from | Why |
|---|---|---|
first_touch_channel | GA4 session default channel group, or your own classifier on the first referrer | Survives the second and third visit, which usually arrive as Direct. |
first_touch_referrer | document.referrer on the first page view, stored in a first-party cookie | Keeps chatgpt.com, perplexity.ai or gemini.google.com as written, so you can re-classify later. |
landing_page | The first URL of the first session | Assistants deep-link. The landing page tells you which answer sent them. |
self_reported_source | A free-text field on the booking or contact form | The only record of influence without a click. Read it, do not dropdown it. |
Write the first three into hidden form fields from a first-party cookie set on the first page view. Keep the fourth as free text. A dropdown with "Search engine" and "Social media" cannot record "I asked Claude which agencies had worked on developer tools", and that sentence is the one you are looking for.
What each signal does and does not tell you
| Signal | Tells you | Does not tell you |
|---|---|---|
| AI crawler hits in server logs | A model's crawler fetched the page. | Whether the page was ever shown to a person, or in which answer. |
| Citations in a visibility tracker | On the prompts you chose, the engine linked or named you on the day it was asked. | Whether any buyer asked that prompt, or clicked. |
| Search Console generative AI reports | Search: AI Overviews and AI Mode impressions by page, country, device and date. Discover: separate AI-feature impressions by page, country and date, without a device dimension. | Clicks. As of October 2026 these reports count impressions only. |
| GA4 AI Assistant sessions | A person arrived from an assistant and the referrer survived. | The visits where the referrer was stripped, which land in Direct. |
| Key event on the conversion action | Which channel the session that converted belonged to. | Anything, if no key event is defined. Then every channel shows zero. |
| "How did you hear about us?" on the form | The influence that never produced a click: the buyer asked an assistant, then typed your name into a browser a week later. | An exact count. People forget, and they answer in their own words. |
Read them in that order. The first three are exposure. The fourth is traffic. Only the last two are about leads, and they are the two most teams have not set up.
Reading Search Console's AI reports
Google launched separate generative AI performance reports for Search and Discover in June 2026, and its launch post records the worldwide rollout on 31 August 2026. A report may be absent if the property has insufficient impressions.
The Search report covers AI Overviews and AI Mode, with page, country, device and date dimensions. The Discover report covers Discover's AI features separately, by page, country and date, without a device dimension. As of October 2026 both report impressions, not clicks.
In the Search report, the unfiltered chart aggregates by property; the Pages table aggregates by page. Multiple URLs from one property can count once in the chart but separately in page rows, so their sum need not equal the chart total. A URL filter changes chart aggregation to URL. Discover aggregates by page in both chart and table. Record the property, dates and filters, and retain both exports before comparing totals or calculating page shares.
Use the Pages table to review which content earns exposure and whether it offers a useful next step. GA4 landing-page activity can provide context, but it alone cannot identify visits from AI Overviews, AI Mode or Discover's AI features. These impressions do not establish traffic or leads; attribution needs separate session or conversion evidence.
A thirty-minute check
- GA4, Traffic acquisition, last 28 days. Find the AI Assistant row. Write down sessions and average engagement time.
- Same table, Key events column. If it is zero everywhere, stop and define the key event before anything else.
- Click your own booking or contact button with the network tab open and filter for
collect. Wait ten seconds: GA4 batches hits, and a four-second look will tell you nothing fired when it did. - Submit your own form. Open the CRM record. Count how many of the four fields arrived.
- Ask the last five people who booked how they found you. Compare with what the CRM says.
The visibility side of this, where the engines name you and where they name a competitor, is a separate measurement. The free visibility check covers it, and how ChatGPT citations work explains what gets cited. When both sides need fixing, that is week one of the Growth Pilot: attribution and AI visibility read together before the two experiment cards are written.
Questions
Does GA4 show traffic from ChatGPT?
Yes. GA4's default channel group has an AI Assistant channel for sessions that arrive from sources such as ChatGPT, Gemini, Copilot, Deepseek or Grok. It appears in the Traffic acquisition report with no setup. It only counts visits where the referrer reached your site.
Why is my AI-assistant traffic lower than I expect?
Some assistants open links in ways that drop the referrer: in-app browsers, copied links, mobile apps. Those sessions are recorded as Direct. A Direct share that grows while your brand searches do not is one sign of it. You cannot recover those sessions in GA4; you can only ask the buyer. The gap is narrowing: ChatGPT adds UTM parameters to links in web-grounded answers, and Gemini started adding them in October 2026, and a parameter survives where a referrer does not.
How do I attribute a lead to an AI assistant?
Define a key event on the action that makes a lead (form submit, booking click), so GA4 can assign it to a channel. Store the first referrer and landing page in a first-party cookie and write them into hidden form fields, so the CRM record carries them. Add a free-text 'How did you hear about us?' field for the influence that never clicked.
Are AI crawler logs a useful KPI?
On their own, no. A crawler fetching forty pages does not tell you whether any of them reached a person. Logs are useful for one narrow question: can the crawler reach the pages you want cited at all.
Is an AI citation worth anything if the answer does not name the brand?
Less than a named recommendation, more than nothing. A linked citation can still send a session, which GA4 will show. An unnamed, unlinked use of your content sends nothing you can measure. Track the two separately: citation share and named-recommendation share.
Does Search Console show traffic from Google's AI Overviews?
The generative AI Search report shows impressions for AI Overviews and AI Mode by page, country, device and date. Discover has a separate report without a device dimension. Google completed the worldwide rollout on 31 August 2026, although a report may be absent with insufficient impressions. As of October 2026 these reports do not show clicks. GA4 landing-page activity alone cannot attribute visits to these AI features.
How many leads should I expect from AI assistants?
Expect small numbers and long sessions. On this site over 28 days, AI Assistant was 48 of 405 sessions, with 1 minute 28 seconds of average engagement against 14 seconds for organic search. Volume is low; intent is high. Judge the channel on key events per session, not on sessions.
Related guides
Cannot tell which channel your leads come from?
Thirty minutes to find where the trail breaks. If it does not break, the call says so.