AI attribution in your CRM:
carry the source from visit to deal
To tie AI search to revenue, capture the source when a visitor first arrives, store it on the contact at signup, and copy it to the deal. Use hidden form fields for referrer, utm_source and landing page. Add a self-reported field. Then report AI-sourced and AI-influenced deals as separate lines.
sources the average B2B buyer used in a recent purchase
Gartner, 645 buyers, Aug to Sep 2025larger buying group when the purchase includes generative AI features
Forrester, State of Business Buying 2026of B2B buyers want to check AI insights with a sales rep
Gartner, May 2026of B2B buyers prefer a fully digital, self service experience
Gartner, May 2026Of 100 AI visits, only the 14 that give an email can reach the CRM, and 10 keep their source
Sample path from an AI visit to pipeline, and where the source field is lost.
Sample data for illustration. Your own numbers will differ.
How to read it. The source has to be captured on the first visit and written to the contact. Where it is lost, a real AI deal looks unattributed.
In ThriveStack citedby The first-visit source is matched to the person who signs up, and then to deals, so AI pipeline stays attributed. See it for your site →
Capture the source on the first visit, because later pages lose it.
A buyer may browse for days before signing up. If you only read the source at signup, you record the last page, not the first. Store the first referrer, utm_source and landing page in a first-party cookie, then write them to hidden form fields.
Five CRM fields are enough to report AI attribution.
Create them on the contact and copy them to the deal when it is created.
| Field | Example value | Why it matters |
|---|---|---|
| First referrer | chatgpt.com | Shows the first recorded source |
| First utm_source | chatgpt.com | Confirms a tagged link |
| First landing page | /research/ga4-ai-traffic | Shows which page earned the visit |
| Self-reported source | ChatGPT | Catches buyers who never clicked |
| AI flag | AI-sourced, AI-influenced or none | Drives the revenue report |
Match people across devices with the email you already collect.
Match the visitor to the contact by email when they sign up or book. Do not buy a data match to fill gaps. Leave the field blank when you do not know.
- Match the visitor to the contact by the email they give you
- Never buy a data match to fill gaps
- Leave the field blank when you do not know
Report two lines and keep the estimate labelled.
AI-sourced is a count. AI-influenced is an estimate. Show them side by side, and let sales correct the self-reported field after a call.
- A count
- Based on a recorded referrer or tag
- Safe to put in front of finance
- An estimate
- Based on a survey answer or another signal
- Always labelled as an estimate
Buying groups are bigger, so a CRM needs the source on the account and on each contact.
Forrester reports that purchases involving generative AI features roughly double the size of the buying group. Gartner found buyers use an average of seven sources. More people and more sources mean more places where an AI answer can enter the deal.
Record the source on the contact and roll it up to the account. If the first person who read your AI answer is not the person who fills out the demo form, the account still carries the AI touch.
larger buying groups when a purchase involves generative AI features
Forrester, via Digital Commerce 360, Jan 22, 2026sources used on average in one purchase
Gartner, 645 B2B buyers, Aug to Sep 2025Sales notes are a data source, so give reps one field and one sentence.
Add a required "How did you hear about us?" picklist at the first call, and one free text field for what the buyer said. Gartner reports 69% of buyers still validate AI insights with a sales rep, so the rep conversation is where the AI mention comes out.
Review the free text monthly and recode "ChatGPT told me" to your AI-influenced value.
Add a required "How did you hear about us?" picklist on the first call, plus one free text field for what the buyer said, in their words.
ThriveStack citedby matches human visits to signups and reports AI-sourced and AI-influenced pipeline, so the CRM fields have a report on top.
AI attribution in your CRM, answered.
How do I track AI traffic in HubSpot or Salesforce?
Pass referrer, utm_source and landing page into hidden form fields, then map them to contact properties.
What is the difference between AI-sourced and AI-influenced?
AI-sourced means the first recorded touch was an AI referral. AI-influenced adds deals where a survey or another signal shows AI played a part.
Do I need to identify every visitor?
No. Match by email when you have it and leave the rest blank.
Sources for this lesson
- Gartner survey on B2B buyers and AI-generated insights, via Business Wire (May 20, 2026) 645 buyers
- Digital Commerce 360: Forrester on B2B buying groups and AI (Jan 22, 2026) 2025 Buyers Journey Survey
Figures were checked against each page in Nov 2026. Vendor studies are marked by their sample. Charts marked sample data are illustrations.
All 10 questions this lesson answers
Connect AI referrals to HubSpot contacts
HubSpot has a native AI Referrals traffic source for visits from platforms such as ChatGPT, Claude, Perplexity and Gemini. It only fires when a referrer or UTM survives, and ChatGPT adds utm_source=chatgpt.com to many links. Check Original Traffic Source on new contacts to see it. Visits that arrive with no referrer land in Direct.
Salesforce AI search lead attribution
Salesforce does not capture UTM values by itself. Add hidden fields for source, medium and campaign to your Web-to-Lead form, then create matching custom fields on the Lead. Web-to-Lead only sends the fields on the form, so an unmapped field means no attribution.
AI referral identity resolution
An AI referral tells you where a visit came from, not who the person is. Identity comes from something you own, such as a form email or a first-party cookie ID. Save the AI source when the visitor lands, then write it to the record when they fill in a form.
Anonymous AI traffic to known account
The visitor stays anonymous until they give you an email or sign in. If your first-party cookie lives on, the earlier AI visit can be attached to that person afterward. Company level matching from IP data is an estimate, so label it that way in reports.
AI traffic account-based attribution
Roll AI-sourced contacts up to their account, then count accounts with any AI touch, not only contacts. Be aware that tools differ. HubSpot credits the first known source and GA4 credits the last non-direct click, so the same visit can be counted differently.
AI referral to CRM opportunity mapping
Copy the AI source from the contact to the opportunity when the deal is created. Add an AI influenced flag rather than a new channel, because a flag on records you already trust holds up better in an audit. ThriveStack Revenue Intelligence links CRM stages, including HubSpot, with billing events such as Stripe.
How to store AI source on lead records
Create dedicated fields, such as AI platform, landing page and first AI touch date. Do not overwrite Lead Source with them, because Lead Source works best as a broad category. Keep raw UTM fields too, so you can re-check the logic later.
AI-assisted lead journey stitching
Keep both a first touch and a latest touch. HubSpot stores Original and Latest Traffic Source separately for this reason. A buyer who researched in AI and later typed your URL shows up as Direct, so add a How did you hear about us field with ChatGPT, Perplexity and Gemini as choices.
AI referral enrichment for RevOps
Add the AI platform, the landing page and any self-reported answer to each lead. RevOps can then score AI-sourced leads and compare their win rate and cycle time with other channels. Review the field values every quarter, because new AI tools keep appearing.
AI search CRM attribution architecture
Think in four layers. Capture the source on the page, carry it into the form with hidden fields, store it in CRM fields, then report on it. Add server logs and a self-reported field as backup for visits that lose their referrer. ThriveStack citedby covers the capture and traffic layers.
Sources, checked November 2026: HubSpot AI referral traffic glossary · HubSpot vs GA4 ChatGPT sessions (Smith Digital) · Salesforce UTM tracking (Salesforce Ben) · ThriveStack docs.