Someone asks ChatGPT to compare web analytics platforms. They read the answer, close the chat and come back a day later by searching for one of the vendors by name. After reading a few pages, they book a demo.
Web analytics can capture the organic search visit, the pages viewed and the conversion. What it can’t show is whether an AI assistant influenced the decision before the visitor ever reached the site. That missing context creates an AI visibility gap: part of AI’s influence never becomes visible in the analytics data.
Here, visibility refers to measurement visibility, not how often a brand appears in AI-generated answers.
In Matomo’s Future of Web Analytics report, based on a survey of 300 web analytics experts in the United States, Germany and France, 92.7% say traffic from AI platforms such as ChatGPT and Perplexity is important to their business. Another 85.7% say AI-generated traffic has a strong or moderate impact on analytics data.
Visibility is uneven. 53.7% report clear visibility into AI traffic, while 40.7% say their visibility is partial. AI is also changing how teams approach measurement: 42.7% say it is forcing them to rethink how they measure performance, and 41% say it is increasing uncertainty in their data.
What the AI visibility gap means for analytics
AI search tracking covers identifiable visits from AI assistants. AI traffic attribution looks at how those recorded AI touchpoints contributed to a conversion.
The AI visibility gap begins where that evidence stops. If someone researches a product in ChatGPT and later arrives through organic search or Direct, analytics can measure the visit and the conversion. It can’t connect the earlier AI interaction to that person unless another measurable signal links the two.
That distinction affects how channel performance should be interpreted. An organic search visit is still an organic search visit, and Direct traffic shouldn’t be reclassified as AI simply because AI may have influenced an earlier stage of the journey.
Other sources can add context. CRM data can show whether a lead became revenue. Branded search trends can show changes in demand. Customer surveys can capture how people remember discovering a brand. AI citation monitoring tools can show where a brand appears in AI-generated answers. Each source contributes a different piece of evidence, and none should be treated as proof of an interaction it did not actually record.
Use each source for what it actually records, and don’t treat supporting data as proof of an AI interaction that wasn’t measured.
AI search tracking captures the visible part
When someone clicks a source link from an AI assistant and referrer information is available, analytics can identify the visit. Teams can then compare AI-referred visits with other acquisition channels and analyse landing pages, visit behaviour, goal conversions and other on-site outcomes.
An AI-influenced conversion may still belong to another channel
Traffic source and AI influence aren’t always the same thing. Consider three common journeys:
- A person compares vendors in ChatGPT, later searches for one brand and converts through organic search.
- A person sees a recommendation in Perplexity, returns later by typing the domain and converts during a Direct visit.
- A person discovers a product through an AI assistant, then clicks a paid campaign while continuing their research and eventually converts.
In each case, the visible acquisition channel describes the visit that actually reached the website. Reclassifying organic search, Direct or paid traffic as AI without evidence would create false precision and make the channel report less reliable.
The same limit applies to attribution models. Multi-touch attribution can distribute credit across touchpoints that were recorded, but it can’t create a touchpoint that was never observed.
More AI referrals improve visibility into measurable visits. They still don’t explain AI influence that happened off-site, so teams need to separate recorded evidence from supporting context and inference.
What the data can and can’t tell you
A practical way to work with the gap is to look at each journey in layers. Start with what web analytics actually recorded, then add other evidence without presenting it as direct attribution.
| Journey | What web analytics can see | What remains unknown | Other context |
|---|---|---|---|
| AI referral, then conversion | AI referrer, landing page, on-site behaviour and conversion. | Any earlier research or AI exposure before the click. | CRM data can add pipeline or revenue after the conversion. |
| AI research, then branded search and conversion | Organic visit, on-site behaviour and conversion. | Whether AI caused or influenced the organic search. | Self-reported discovery, search demand, CRM and AI citation monitoring can add context. |
| AI answer, no website visit | No on-site signal from that interaction. | The whole AI interaction and whether it influenced a later decision. | AI citation monitoring can show that the brand or page appeared in AI-generated answers, while brand-search trends can add further context. Neither provides direct attribution. |
| AI referral, then lead and closed deal in a multi-step enterprise sales process | AI referral and the on-site lead conversion. | The commercial outcome after the lead leaves the website. | CRM opportunity and revenue data connect the measurable visit to downstream value. |
The final column helps you interpret the signals you already have. You probably won’t be able to reconstruct every journey end to end. Comparing data across systems can still show whether different parts of the journey support the same interpretation, without turning that context into a measured touchpoint. Self-reported discovery data can help too, with the limitation that it reflects what people remember and choose to report.
AI attribution needs context from more than one system
Different systems record different parts of the customer journey. Web analytics shows what happened on the website, while CRM data shows what happened to a lead or account afterwards. Search and campaign tools can show changes in demand and acquisition. AI citation monitoring can show whether, for example, a product page appears in ChatGPT or Perplexity responses. On its own, though, it doesn’t tell you whether those appearances led to a website visit or conversion. Web analytics provides the separate on-site view of identifiable visits and conversions. BI or a data warehouse can then bring several of those signals together under shared definitions.
The Future of Web Analytics report found that 49% of respondents expect hybrid approaches combining multiple systems to define the future of web analytics. Another 38% see foundational data layers connected to BI tools as part of that future, while 41% select integration with existing tools as a buying factor.
To connect AI-referred visits with pipeline or revenue, teams need a way to use analytics data alongside CRM, BI or other business data. Analysts also need ways to retrieve the data without being confined to one dashboard.
APIs and structured exports are established routes for that work. As AI becomes part of analysis itself, protocols such as MCP provide another option for compatible AI applications to retrieve analytics context. Matomo’s MCP Server, for example, can connect authorised tools such as ChatGPT, Claude and Codex to Matomo data. If the AI application is also connected to other systems, it can use Matomo data alongside that context without teams having to assemble everything manually first.
What to look for in an analytics setup
When assessing an analytics setup for AI attribution, look at whether it can support the following:
| What to check | Why this matters |
|---|---|
| Can you identify human visits referred by recognised AI assistants and analyse their conversions separately? | This lets you compare AI-referred visits with other acquisition sources and see how those visitors behave and convert once they reach the website. |
| Can you separate automated AI agent or chatbot activity from human behaviour where the available signals allow it? | Automated activity can affect traffic and engagement figures. Keeping it separate makes human behaviour easier to interpret and allows AI optimisation as well. |
| Can analysts retrieve data through APIs or structured exports? | APIs and structured exports let teams use analytics data alongside CRM, BI or other datasets to analyse performance beyond the dashboard. |
| Can ecommerce teams compare AI-referred visitors with other human visitors across the on-site conversion funnel, while keeping automated AI activity separate? | This shows whether people arriving from AI tools behave differently across product, cart and checkout steps, without automated requests distorting conversion rates or drop-off analysis. |
| Can analytics data move into CRM, BI, warehouse and reporting workflows? | Conversion data becomes more useful when teams can connect on-site behaviour with leads, pipeline, revenue and other business outcomes. |
| Can authorised AI tools work with analytics data under clear access controls? | This keeps AI-assisted analysis within the access boundaries set for the underlying analytics data. |
| Can teams assess the quality of the underlying data, and is it unsampled and auditable? | AI tools work from the data they receive. Teams need to understand its limitations and trace how the numbers were collected and reported. |
| Can the team trace how sources are classified and how attribution logic is applied? | When a channel suddenly gains or loses conversions, analysts need to understand whether the change came from visitor behaviour, source classification or reporting logic. |
These checks show whether teams can trace AI-referred visits, understand how they were classified and connect them with downstream business outcomes.
How Matomo helps with the measurable part
Matomo separates human visits referred by AI assistants from automated AI activity, so teams can analyse each on its own terms. The AI Assistant acquisition channel identifies human visits from recognised AI assistants when referrer information is available. Those visits can be compared with other acquisition channels and analysed across landing pages, behaviour, goal conversions and other on-site outcomes.
Dedicated AI reports cover activity that doesn’t represent a human referral. The AI Agent Overview compares recognised agent visits with human traffic, while AI Chatbots reports show how supported chatbots retrieve website content through server-side tracking. Content Requests reports can also show which pages and documents chatbots request, including content they favour or fail to retrieve. AI Chatbot requests themselves are processed separately from visits, so they don’t create visit or attribution data.
Teams can also work with Matomo data through AI-assisted workflows. The Matomo MCP Server gives authorised tools such as ChatGPT, Claude and Codex structured access to Matomo analytics data, so analysts can query it in natural language. If the AI application is also connected to other systems, it can use Matomo data alongside that context.
Ask Matomo, scheduled for the second half of October 2026, will bring that type of natural-language analysis into Matomo itself. Signed-in users will be able to ask questions about supported reports, analytics data and configuration, subject to their existing permissions.
Build AI attribution around the evidence you have
AI can influence research before a visitor reaches your website, but attribution still needs to follow the touchpoints you actually record.
If a recognised AI referral is recorded, you can analyse the visit and include that touchpoint in attribution. If someone arrives through organic search and there’s no measurable AI touchpoint, keep the visit under organic search. Customer surveys and AI citation monitoring can add context about earlier discovery, while CRM data can connect the recorded visit or conversion with downstream outcomes. None of those sources turns an unrecorded AI interaction into a measured touchpoint.
Use directly measured interactions for attribution and bring in other data where it adds useful context. When a connection is inferred rather than recorded, make that clear.
Explore the wider findings on AI, trust and connected analytics in The Future of Web Analytics.
See how Matomo handles AI traffic in practice
Separate AI referrals, agents and chatbots, then connect analytics data to the wider workflows your team uses.
