Skip to content

Track Leads and Customers From AI Tools Such as ChatGPT, Claude and Gemini

AI assistants increasingly send people to websites, yet most teams cannot say whether that traffic produces enquiries, paying customers or revenue. This guide explains how to label AI-originated visits at the point of arrival, carry that label through a form submission into a CRM, and report on the commercial result by tool, channel and landing page.

The gap between AI visibility and AI revenue

Visibility metrics answer a different question from revenue metrics. A brand can be cited often in AI answers and still generate few enquiries, or be cited rarely and still win high-value customers. The missing link is lead-level attribution: knowing, for each enquiry, whether the visitor arrived via an AI assistant, which assistant it was, and which page they landed on. Once that information travels with the lead into the CRM, downstream reporting can follow the same lead through conversion to customer and revenue.

What gets captured on an AI-referred visit

On arrival, technical signals are examined to determine where a visitor came from, using broadly the same kinds of signals web analytics tools rely on. The visitor is then assigned to a channel such as AI Referral, Organic Search, Paid Search or Paid Social, and that result is stored in the browser. When the visitor later submits a form, the stored channel details are written into hidden fields on that form, so they are captured alongside the name, email address and other details the visitor entered.

A worked example: a small-business owner asks an AI assistant for an accountant recommendation, follows a link to an accounting firm's site, and submits an enquiry form. The submission can carry:

  • Channel set to AI Referral
  • Channel Drilldown 1 set to the assistant name, for example ChatGPT
  • Channel Drilldown 2 set to the assistant domain, for example chatgpt.com
  • Channel Drilldown 3 set to None where no further detail applies
  • Landing Page showing the exact page first visited, such as a small-business accounting services page
  • Landing Page Group showing the parent section, such as /services

That combination lets a report separate AI-originated leads from other channels, split them by individual assistant, and connect revenue back to the content that attracted the visitor.

Which assistants are recognised

Thirteen assistants are currently recognised: ChatGPT, Perplexity, Gemini, Copilot, Claude, Meta AI, Grok, DeepSeek, Mistral, Poe, You.com, Duck.ai and Phind. Recognition depends on the domains and link tags associated with each assistant, so the recognised list should be checked as assistants change their properties. If a visitor arrives from an unrecognised assistant or a new domain, they may be categorised elsewhere, which is a reason to review the list periodically rather than assume coverage is permanent.

Setup checklist

Setup follows four steps:

  • Install the tracking code on the website using the instructions provided when the account is created or accessed.
  • Add four hidden fields to each lead-capture form: Channel, Channel Drilldown 1, Channel Drilldown 2 and Channel Drilldown 3. Most form builders allow this by dragging in a hidden field type or hiding an existing field in its settings.
  • Confirm that the tracking writes the channel details into those fields when a visitor who arrived from an AI assistant submits the form.
  • Pass the captured fields onward to the CRM or spreadsheet. Where the form builder and CRM are the same product, the data can appear directly on the contact record. Where they differ, built-in integrations, a connector such as Zapier, or an update to an existing integration can carry the new fields with each lead.

More than 50 form builders, scheduling tools and chat products are supported, including Gravity Forms, Calendly, Contact Form 7, Wix Forms, Webflow Forms, Typeform, Jotform and Zoho Forms. Before starting, check that your exact form tool is supported and that your CRM can accept custom fields for the drilldown values.

Four reports to run once data is flowing

With channel data stored on each lead, four reports provide a practical starting point:

  • Leads by channel: monthly lead volume split across AI Referral, Organic Search, Paid Search, Paid Social and other channels, showing whether AI is growing as a share of total enquiries.
  • Customers by AI tool: new customers per month split by assistant, showing which tools produce paying customers rather than only mentions or visits. If most customers arrive through one assistant, that is evidence about which audience behaviour to prioritise.
  • Close rate by channel: the proportion of leads that become customers, split by originating channel. AI-referred leads are often more researched before they enquire, so their close rate can be materially higher; one illustrative pattern in the underlying material showed 35% for AI Referral against 10% for Organic Search and 7% for Paid Search. Treat those figures as an example of how to read the report, not as a benchmark for your business. If your data shows a similar gap, an AI lead is worth more than a paid-search lead and resourcing should reflect that.
  • Revenue from AI referral by landing page: customers and revenue attributed to each page that AI assistants sent buyers to. Pages that repeatedly produce revenue are candidates for improvement or for further content in the same topic.

Run these reports monthly, compare AI Referral against your other channels, and use the landing-page view to decide which content to expand.

Getting started

Start by installing the tracking code and adding the four hidden fields to your main enquiry form, then submit a test enquiry from an AI assistant referral and confirm the channel, drilldown and landing page values appear on the resulting lead record. Once that test passes, extend the fields to remaining forms and build the four reports above. If you want to evaluate a paid plan, check the current plan options and any trial terms on the signup page before committing, since availability and conditions can change.

Frequently asked questions

Why are AI mentions and website visits not enough?

Mentions and citations show visibility, while visitor counts show traffic. Neither connects a visit to a submitted enquiry, a closed deal, or the money that deal produced. Recording the originating channel on the lead itself closes that gap.

Which AI assistants are recognised?

ChatGPT, Perplexity, Gemini, Copilot, Claude, Meta AI, Grok, DeepSeek, Mistral, Poe, You.com, Duck.ai and Phind are listed as recognised. Domains and link tags for each are held in a separate recognised-assistants list.

What fields need to be on the form?

Channel, Channel Drilldown 1, Channel Drilldown 2 and Channel Drilldown 3. Landing page and landing page group can also be captured alongside the lead's contact details.

Will this work with my form tool?

More than 50 form builders, scheduling tools and chat products are supported, including Gravity Forms, Calendly, Contact Form 7, Wix Forms, Webflow Forms, Typeform, Jotform and Zoho Forms. Check your specific tool before committing.