AI Search and Customer Inquiries: What Can You Measure?
Published
If an AI assistant recommends your business, the appearance may be worth recording. The next question is whether someone reached the website and made a suitable inquiry. A visibility screenshot cannot answer that by itself.
The business needs evidence that follows the relevant parts of the journey. Some parts can be observed closely. Others remain unknown, even when the report has a confident-looking channel label.
A possible journey needs evidence at each step
A prospect might discover the company through an AI answer, check its services and evidence, follow a link, and get in touch. They might also remember the name and return later through ordinary search. Some people will find their answer without visiting at all.
These are possible routes, not a guaranteed funnel. Evidence about the company gives a visitor something concrete to evaluate: what it does, where it works, what it can demonstrate and how to ask for help. Publishing that evidence does not establish which information an AI system used internally.
The diagram follows one observable route and marks where information can disappear. It explains the evidence available to the business, rather than reconstructing a private history of the customer.
One possible journey. Arrows show a route, not guaranteed conversion or proof of causation.
Diagram in words
From discovery to an inquiry with source context One possible route, with an evidence boundary at each step. 1 AI / search discovery A business appears in an answer or result. EVIDENCE BOUNDARY An appearance may end without a visit. 2 Business and site evidence Services, company facts and evidence can be evaluated. EVIDENCE BOUNDARY The site does not reveal the AI system’s internal reasoning. 3 Referral / website visit An identifiable arrival may reach a landing page. EVIDENCE BOUNDARY Missing arrival data leaves the source unknown. 4 Inquiry A request reaches the business for review. EVIDENCE BOUNDARY An accepted request still needs a fit decision. 5 Source context kept with the inquiry Available arrival context stays with the inquiry. EVIDENCE BOUNDARY Source context does not establish every influence or cause. Arrows show a possible journey, not guaranteed conversion.
Our guide to mentions, citations and referrals provides the durable definitions and observation method. The question here is how that evidence helps an owner judge inquiries and spending.
Google visibility and AI visits now have different report labels
Google's current Search Console documentation describes a Generative AI performance report for Search, covering impressions in AI Overviews and AI Mode. The insights rolled out worldwide on August 31, 2026; a site with insufficient impressions may still have no report to display. Its data is included in the wider Web performance report, so the two totals should not be added as separate audiences. [1]
That is visibility evidence. It does not establish how many qualified requests the company received. It also does not report every assistant or every AI-related interaction outside Google Search.
For the search experiences behind that report, our explanation of Google AI Overviews and AI Mode shows how sources can appear and what that visibility can mean for a business.
For website visits, Google Analytics now defines an AI Assistant channel for recognized sources such as ChatGPT, Gemini and Copilot. Google AI Overviews and AI Mode are excluded from that channel and remain in Organic Search. [2]
Consequently, “AI Assistant traffic” and “all traffic influenced by AI” are different claims. The channel label can identify a recognized arrival route. It cannot tell the full story of what persuaded the customer before that visit.
A useful report names the measure and its scope: visibility in a specified platform, a recorded website arrival, or an inquiry confirmed by the business. Those measures can inform the same decision without pretending they count the same thing.
Keep the arrival context with the inquiry
OpenAI documents utm_source=chatgpt.com in referral links from ChatGPT. When that parameter reaches the website, it can provide useful evidence of an identifiable arrival. It does not prove everything the visitor saw or establish that AI caused the eventual sale. [3]
The initial arrival and the page where a form is submitted may be different. Someone might land on a guide, read About and then use Contact. If the record keeps only the submission page, the useful source information can be lost inside an ordinary website journey.
Where available and permitted, first-party inquiry context can keep the external referrer, the landing page, campaign or referral parameters, and the page where the request was sent. This context belongs with the voluntarily submitted inquiry. It does not need to become an advertising profile or a record of independent visits.
There are real limits. A browser or referring page can restrict the referrer to a website origin or suppress it altogether. The full external path is not always available. [4] An absent referrer therefore leaves the source unknown; it is not proof that the visitor typed the address.
A missing source should remain unknown. A rise in branded searches, or the team's expectation that AI brought the customer, does not establish the discovery route for that inquiry.
Operational inquiry context and website Analytics have different purposes and limitations. Their records may not match exactly. A business can still evaluate the context of a particular request without treating that request as proof of every earlier touchpoint.
An accepted inquiry still needs a business decision
The inquiry record confirms that a request reached the business. The owner still needs to judge whether it fits the service and merits a next conversation. The Library guide to measuring website leads explains the wider distinction between an action, an accepted inquiry, a qualified lead and a customer. The Analytics & Conversion Library explains how to keep discovery, sessions and inquiries distinct.
For an AI-specific review, the important question is whether source evidence can be retained alongside that business judgment. A recognizable assistant referral attached to an unsuitable request is different from the same referral attached to an appropriate project inquiry.
Consider an illustrative example, not a SEOTEC client result. A prospect says they first encountered a company in an assistant, while the inquiry shows a later Google arrival. Both can be useful: one describes remembered discovery, the other the recorded route to the site.
Neither needs to overwrite the other, and the business has still received one inquiry. A sales conversation can add context without turning the contact form into a long questionnaire or assigning a causal percentage that the evidence cannot support.
What does the gap suggest doing next?
If the business is described inaccurately, the next priority may be clearer, confirmed service and company information. Google's guidance emphasizes useful original content and established Search foundations rather than a special AI markup shortcut. [5]
If relevant visitors arrive but the requests do not fit, the page may need to explain scope, evidence or the next step more clearly. Buying more visibility before understanding that mismatch can make the same problem larger.
If inquiries arrive but their source is frequently unknown, that is a reporting limit to investigate through the existing measurement process. It is not a reason to label those requests as AI-generated. Similarly, a month without identifiable AI inquiries does not prove there was no AI influence.
A provider should be able to connect the proposed work to one of those observed gaps. Our AI search work addresses discoverability and the evidence available about a business; Analytics and conversion work helps interpret what can be observed after arrival.
The report should make the unknowns visible
A useful AI search review can show discovery evidence, identifiable arrivals and suitable inquiries side by side, with the period and source of each measure. Missing attribution should remain visible rather than disappearing into an impressive total.
The owner can then ask a practical question: which part of this journey needs attention, and what evidence would show that the proposed work helped? That produces a clearer spending decision than assuming every citation is a lead, or every lead with an AI label is an AI-caused sale.
When the decision is whether SEO investment itself still makes sense, our analysis of SEO and AI Search addresses that separate budget question.
Sources
- Google: Generative AI performance report (Search):https://support.google.com/webmasters/answer/16984139?hl=en
- Google Analytics: Default channel group:https://support.google.com/analytics/answer/9756891?hl=en
- OpenAI: Publishers and Developers FAQ:https://help.openai.com/en/articles/12627856-publishers-and-developers-faq
- W3C: Referrer Policy:https://www.w3.org/TR/referrer-policy/
- Google: Optimizing for generative AI features:https://developers.google.com/search/docs/fundamentals/ai-optimization-guide
