When AI Search Sends the Lead but Not the Credit: A Local Business Attribution Guide

A prospect may ask ChatGPT, Google AI Mode, Perplexity, or another answer engine for a recommendation. They may then search the recommended company by name, type the URL into a browser, call a number they saved, or ask a colleague to make the introduction. By the time the inquiry reaches the website or CRM, the visible source may be branded search, direct traffic, a phone call, or “unknown.”

That is not evidence that AI caused the conversion. It is evidence that the customer journey can outlast the referral data. The practical business problem is deciding what can be measured, what must be asked, and what remains uncertain before cutting content or investing more budget.

Google’s guidance says traffic from AI features is included in the overall Search Console Web performance report. That makes Search Console useful, but it is not a complete AI-to-revenue attribution layer. A business should not expect every AI-influenced journey to appear as a clean source/medium value beside a booked appointment.

Recent practitioner discussion has focused on conversational-looking queries appearing in ordinary Search Console data while dedicated generative-AI reporting does not expose equivalent query-level detail. The useful takeaway is not that every “yes” or follow-up query proves AI Mode. It is that reporting is evolving and some channel distinctions must be treated as hypotheses rather than facts.

Start with a fixed vocabulary in analytics and the CRM. “Directly observed AI referral” means a known AI assistant or answer tool appears in referral data. “Self-reported AI discovery” means the prospect selected an AI assistant or described one in an intake answer. “AI-assisted likely” is an analyst’s documented interpretation of multiple signals, such as a tested recommendation followed by a branded search increase. “Unattributed” means the origin is not known. These categories should not be collapsed into one impressive percentage.

Keep first-touch, last-touch, and assisted-conversion views separate. A customer can first discover a business through an answer engine, return through a branded search, and convert after a staff member follows up. Each view answers a different question: what introduced the business, what preceded the action, and what channels appeared along the path?

Choose a stable set of real buyer questions by service, location, urgency, and comparison intent. Test them on a repeatable schedule across the answer engines that matter to the audience. Log whether the business is named correctly, whether the service and location are accurate, which source is cited, whether a link is present, and whether the answer offers a plausible next step. Do not count a favorable screenshot as a conversion.

On the owned-property side, review analytics referrals, landing-page events, click-to-call events, form metadata, campaign parameters, and the handoff into the CRM. Add one short, neutral intake question such as “How did you first hear about us?” with options for search, referral, social, an AI assistant, and an open text field. This supplements automated attribution; it does not replace it.

Finally, join the signal to lead quality. Track qualified calls, submitted audits, booked consultations, appointments, signed work, or another outcome the business can define consistently. If the CRM cannot connect a source to an outcome, fix that operational gap before building a more elaborate AI dashboard.

A useful report can fit on one page when the definitions are clear. Include the date range, test conditions, data sources, changes from the prior period, and the evidence boundary. A simple table might contain:

ARCH3R can help establish a baseline across public entity information, priority service and location pages, answer-engine tests, analytics, call and form paths, CRM fields, and follow-up. The useful deliverable is a prioritized map of inconsistencies and measurement gaps: which public facts need an owner, which landing pages need a clearer next step, and which qualified outcomes should be reviewed next month.

No audit can prove that an AI answer caused a sale when the system did not record that connection. It cannot guarantee a citation, a recommendation, a ranking, or a particular volume of leads. Search features, models, location, personalization, and source availability change. A responsible report preserves those limits while still making the next decision easier.

If prospects mention ChatGPT or another AI assistant but your reports keep labeling those conversations as direct, branded, or unknown, request the free ARCH3R audit. We can help separate what your systems observe from what your customers report—and connect both to the qualified follow-up process.