How much revenue has AI brought us?
We count the visits AI assistants send you, then follow them to leads and revenue. You see the totals, which assistant sends buyers, and which pages they land on.

- 1AI visits, leads and revenue, step by step
- 2Which AI assistant sent them
- 3Which of your pages they landed on
What you do with it
- Show your boss the leads and revenue AI brought in this quarter
- Spend your time on the AI assistants that send buyers, not just clicks
- Open any single AI visit to see where it landed and whether it converted
What it can't do
- Some AI visits arrive with no label. We can't count every one of them.
- Revenue shows when GA4 records a value for your conversions. If it doesn't, we say so.
- It counts visits that reached your site. A buyer who read an AI answer and never visited isn't counted.
- Revenue from deals needs a connected CRM. HubSpot is live; Pipedrive, Attio and Zoho are coming soon.
AI revenue attribution from your own GA4 data
When someone clicks a link in ChatGPT, analytics often files the visit as Direct. So the revenue AI brings in goes uncounted.
We read your GA4. Where your property has GA4's AI Assistant channel, we use it. Where it doesn't, we match the referrer. The page tells you which of the two you're looking at.
You see AI visits and conversions, with the change from last period. You see revenue from AI visits next to what you spend on AI visibility. And you see payback in months, and cost per customer from AI next to your usual cost.
Which AI assistant sends buyers
ChatGPT, Claude, Perplexity, Gemini, Copilot and Google AI Overviews don't send the same buyers. For each one you see visits, conversion rate and revenue per visit. The one with the highest conversion rate is named.
Below the totals is a list of single AI visits. Each shows the assistant, the landing page, and whether it converted. It also shows how sure we are it came from AI.
From Search Console, you also see searches that read like questions to an AI assistant. These are kept apart from the GA4 numbers, because they measure something different.
What AI earned you, and what it costs you
This page shows revenue that arrived. Revenue at risk estimates the revenue you miss when AI recommends someone else. One is measured and one is estimated, so we keep them on separate pages and never add them together.
How AI-sourced companies sync to HubSpot without duplicates
The sync is off until you turn it on. It finds the record your team already has, adds its own AI fields to it, and leaves every other field alone. Below are the matching rules, the fields it never writes, and one example record.
Matching rules
- Companies match on domain. Before writing, we search HubSpot for a company whose Company domain name equals the visiting company's domain. If one exists, we update it. We create a company only when none is found.
- After the first push we keep the HubSpot record ID, so later pushes update that same record. If the record was deleted or merged in HubSpot, we search by domain again before creating anything.
- Contacts match on email, which HubSpot keeps unique. An existing contact is updated, not copied. Contact push is a separate switch, and it needs the visitor's consent and a real email address.
- A company whose AI fields have not changed since the last push is skipped.
- A company whose lifecycle stage is Customer or Evangelist is left untouched by default.
- Deals are never created, moved or edited. Our access to deals is read-only.
Fields we never write
- Original source, its drill-downs, latest source and every other HubSpot analytics field.
- Campaign and UTM fields, including custom ones your team built.
- Lifecycle stage, lead status and owner. We read lifecycle stage and never set it.
- Name, industry, country and size on a company that already exists. We fill name, domain, industry and country only on a company we create.
- Any AI field we have no value for. A blank on our side never clears a value on yours.
- Labels you changed on our fields. Each field is created once per HubSpot portal and then left as it is.
One example record, before and after
Worked example. The company and its values are invented. The field names and the behaviour are the ones the product uses today.
Brightlane Logistics is already in HubSpot from a paid search campaign. Two people from its network then arrive from Perplexity and ChatGPT. The daily push finds the company by its domain and writes ten fields.
| HubSpot company field | Before the push | After the push |
|---|---|---|
| Company domain name | brightlane.example | Unchanged |
| Company name | Brightlane Logistics | Unchanged |
| Company owner | Your assigned rep | Unchanged |
| Lifecycle stage | Lead | Unchanged |
| Original traffic source | Paid search | Unchanged |
| Your campaign field | q3-logistics-webinar | Unchanged |
| Industry | Computer software | Unchanged |
| AI assistant that sent them | Empty | perplexity |
| AI buying intent | Empty | 72 |
| AI intent band | Empty | B |
| People researching you | Empty | 2 |
| Last seen from an AI answer | Empty | Date of the latest visit |
| Prompt they found you on | Empty | tools that tie AI traffic to HubSpot deals |
| Question topic they asked AI | Empty | AI attribution |
| Page AI sent them to | Empty | https://yoursite.example/features/ai-revenue-attribution |
| Prompt match confidence | Empty | 75 |
| Targetlytics account | Empty | Link to the evidence |
Result: one company record with the same record ID. Ten AI fields filled, seven existing fields untouched, no new company, no deal created.
Where your team still needs to look
- The domain match is exact. A company stored in HubSpot under a different domain may not be found, and a new company is then created for the visiting domain.
- If HubSpot already holds two companies with the same domain, we update one of them. We do not merge records.
- On an existing contact, first name, last name and job title are updated when we hold a value. Leave contact push off if your team maintains these by hand.
- Lead routing stays in HubSpot. We set no owner. Route with your own HubSpot workflow or view, filtered on "AI assistant that sent them" or "AI buying intent".
- On a company or contact we create, HubSpot sets its own source value for records made by an integration. We do not set it.
Frequently Asked Questions
Questions about AI revenue attribution
Many AI apps don't pass on where a visit came from. Analytics can't tell the source, so it files the visit as Direct.
Each visit carries a confidence score. GA4's AI Assistant channel and a clear referrer count as sure. Weaker signals are marked as less sure, so you can report either view.
No. We read from GA4, Search Console and your CRM. Your existing reports and workflows keep working as they do now.
Companies are matched on domain and contacts on email, so an existing record is updated instead of copied. On an existing company we write ten AI fields and nothing else. Original source, campaign fields, lifecycle stage and owner are never written. A company stored under a different domain can still end up as a second record.
HubSpot today. Pipedrive, Attio and Zoho are coming soon.
Ultimate, and the Agency plan per client workspace.
Related reading
- GuideHow to track AI referral trafficIdentify, tag and attribute ChatGPT, Perplexity and Gemini traffic in GA4.Read
- GuideChatGPT traffic showing as Direct in GA4?Why it happens, and the step-by-step fix.Read
- Free toolFree UTM builder for AI trafficTag links for every AI assistant at once, and get the GA4 channel rules.Read
See what AI has brought you
AI revenue attribution is part of the Ultimate plan, with a 7-day free trial.
Free AI visibility audit
Find out what ChatGPT tells your buyers about you.
Where you're named, what AI gets wrong, and the first three things to fix. Emailed within two hours.
- Within 2 hours
- No credit card needed
- Free