--- title: "How to measure AI assistant traffic: layers, limits and procedure" description: "Part of the traffic from AI assistants can be measured. Four layers, their limits and a validation procedure to know how much to trust each number." url: "https://cookingmetrics.com/blog/como-medir-trafico-asistentes-ia/" markdown_url: "https://cookingmetrics.com/blog/como-medir-trafico-asistentes-ia.md" lang: "en" date_published: "2026-11-12" author: "Martín Garay" author_url: "https://cookingmetrics.com/about-martin-garay/" publisher: "CookingMetrics" publisher_url: "https://cookingmetrics.com/" keywords: ["SEO for AI (GEO)", "Technical SEO"] citation_apa7: "Garay, M. (2026, November 12). *How to measure AI assistant traffic: layers, limits and procedure*. CookingMetrics. https://cookingmetrics.com/blog/como-medir-trafico-asistentes-ia/" references_apa7: - "Google Analytics Help. (n.d.). *Default channel group*. https://support.google.com/analytics/answer/9756891" - "Google Search Central. (n.d.). *AI features and your website*. https://developers.google.com/search/docs/appearance/ai-features" - "Microsoft Bing Webmaster Blog. (n.d.). *Introducing AI Performance in Bing Webmaster Tools Public Preview*. https://blogs.bing.com/webmaster/2026/2/Introducing-AI-Performance-in-Bing-Webmaster-Tools-Public-Preview/" - "Microsoft Learn (Clarity). (n.d.). *Bot Activity overview*. https://learn.microsoft.com/en-us/clarity/ai-visibility/bot-activity-overview" - "OpenAI. (n.d.). *Overview of OpenAI crawlers*. https://developers.openai.com/api/docs/bots" - "Google for Developers. (n.d.). *Google Analytics Data API schema*. https://developers.google.com/analytics/devguides/reporting/data/v1/api-schema" - "Google Search Central. (n.d.). *Verifying Google crawler requests*. https://developers.google.com/crawling/docs/crawlers-fetchers/verify-google-requests" - "Google Search Central. (n.d.). *AI features in Google Search*. https://support.google.com/webmasters/answer/16984139" --- # How to measure AI assistant traffic: layers, limits and procedure > Part of the traffic from AI assistants can be measured. Four layers, their limits and a validation procedure to know how much to trust each number. - **Author:** [Martín Garay](https://cookingmetrics.com/about-martin-garay/) · Founder of CookingMetrics - **Published:** November 12, 2026 - **Topics:** SEO for AI (GEO), Technical SEO - **Web version:** https://cookingmetrics.com/blog/como-medir-trafico-asistentes-ia/ ## How to cite this article (APA, 7th edition) Garay, M. (2026, November 12). *How to measure AI assistant traffic: layers, limits and procedure*. CookingMetrics. https://cookingmetrics.com/blog/como-medir-trafico-asistentes-ia/ In-text citation: (Garay, 2026) ## References - Google Analytics Help. (n.d.). *Default channel group*. https://support.google.com/analytics/answer/9756891 In-text citation: (Google Analytics Help, n.d.) - Google Search Central. (n.d.). *AI features and your website*. https://developers.google.com/search/docs/appearance/ai-features In-text citation: (Google Search Central, n.d.) - Microsoft Bing Webmaster Blog. (n.d.). *Introducing AI Performance in Bing Webmaster Tools Public Preview*. https://blogs.bing.com/webmaster/2026/2/Introducing-AI-Performance-in-Bing-Webmaster-Tools-Public-Preview/ In-text citation: (Microsoft Bing Webmaster Blog, n.d.) - Microsoft Learn (Clarity). (n.d.). *Bot Activity overview*. https://learn.microsoft.com/en-us/clarity/ai-visibility/bot-activity-overview In-text citation: (Microsoft Learn (Clarity), n.d.) - OpenAI. (n.d.). *Overview of OpenAI crawlers*. https://developers.openai.com/api/docs/bots In-text citation: (OpenAI, n.d.) - Google for Developers. (n.d.). *Google Analytics Data API schema*. https://developers.google.com/analytics/devguides/reporting/data/v1/api-schema In-text citation: (Google for Developers, n.d.) - Google Search Central. (n.d.). *Verifying Google crawler requests*. https://developers.google.com/crawling/docs/crawlers-fetchers/verify-google-requests In-text citation: (Google Search Central, n.d.) - Google Search Central. (n.d.). *AI features in Google Search*. https://support.google.com/webmasters/answer/16984139 In-text citation: (Google Search Central, n.d.) --- **Part of the traffic that arrives from AI assistants can be measured, but not all of it.** It is best to combine four layers: the Google Analytics report, the server logs, the Google Search Console and Bing Webmaster Tools consoles, and Microsoft Clarity. Each one answers a different question and has limits that need to be understood before drawing conclusions. This guide is written for those who must decide what to measure and how to interpret what they see, not only for those who configure the tools. Technical terms are explained in plain words and the detail appears under the label "For the technical team". [CookingMetrics](https://cookingmetrics.com/) does not sell AI visibility tools; it offers measurement audits and develops its own applications, and this guide only uses tools that measure the site itself. ## In summary - Three different things are often called "AI traffic": visits from people who arrive from an assistant, the activity of the robots that read the site, and citations of the site within answers. They are measured with different tools and are not added together. - Google Analytics has a default channel, "AI Assistant", that groups visits from assistants such as ChatGPT, Gemini, Deepseek, Copilot or Grok and excludes AI Overviews and AI Mode. Google's page does not explain how it maintains the list of assistants and states that the definitions may change. - Search Console includes AI features in Web performance and has a specific impressions report. That report is not a breakdown of clicks or sessions. Bing reports citations and Clarity bot activity, each with its own scope. - Part of the traffic may not appear as AI traffic; the most likely reasons are hypotheses of this guide, not findings. This guide contains no figures for share or conversion of AI traffic. - A simple validation procedure (manually reviewing a sample, cross-checking with the server logs and recording the date and the configuration) makes it possible to know how much to trust each number. ## Three different questions: visits, crawling and citations Before measuring, it is worth deciding which question you want to answer. - **Visits:** how many people arrived at the site from an AI assistant? This is what is called referral traffic. It is measured with web analytics. - **Crawling:** which robots from AI companies read the site and how often? This is machine activity, not people. It is measured with the server logs or the content delivery network (CDN) logs. - **Citations:** how many times does the site appear as a source in an assistant's answers, whether or not there is a click? Only the platforms that offer it report it. A citation without a click is not a visit, and a request from a robot is not a visit. Mixing them leads to false conclusions, for example, believing that AI traffic grew when only crawling increased. ## Layer 1: Google Analytics Google Analytics groups visits into channels according to their origin. Google's documentation states that there is a default channel called "AI Assistant": it groups visits from sources such as ChatGPT, Gemini, Deepseek, Copilot or Grok, and excludes Google's AI Overviews and AI Mode ([Default channel group](https://support.google.com/analytics/answer/9756891), consulted on November 12, 2026; the page shows no update date). A visit is assigned to that channel in two cases: if the medium is exactly `ai-assistant`, or if the medium is defined as `ai-assistant` because the referrer (the site from which the person arrived) matches a list of AI assistants. The page does not explain how that list is maintained and warns that the definitions may change. - **What it answers:** how many visits with an identifiable origin arrived from assistants that Google recognizes, how many sessions and on which pages. - **What it does not answer:** visits with no identifiable origin, those from assistants that are not on Google's list and those that Google classifies in another channel. - **For the technical team:** if you need to cover other assistants or group them differently, you can create a custom channel group with a regular expression on the session source. The step-by-step configuration is in the guide by Martín Garay, founder of CookingMetrics, published on his personal site, which belongs to a different brand: [how to measure ChatGPT traffic in GA4](https://www.martingaray.com.ar/google-analytics/como-medir-el-trafico-de-chatgpt-en-ga4/) (published on April 4, 2025 and updated on June 16, 2026). That guide uses a broad regular expression, and the following section explains why its results should be reviewed. ### A risk of broad regular expressions A regular expression that looks for text fragments, such as "gpt" or "gemini", captures any source that contains those letters, even if it is not an assistant. This is a logical possibility, not an error demonstrated in any guide. That is why the validation procedure below includes manually reviewing the sources that the filter captures. [Section for signed-in readers, level C: https://cookingmetrics.com/blog/como-medir-trafico-asistentes-ia/#bloque-1] ## Layer 2: server and CDN logs Server logs record every request the site receives, with the name of the program that made it (the user agent). They are the most complete source for knowing which robots read the site. OpenAI documents three user agents: `OAI-SearchBot`, for search; `GPTBot`, for its models; and `ChatGPT-User`, for certain user actions in ChatGPT. For the first two, `robots.txt` controls access; for `ChatGPT-User`, the documentation states that `robots.txt` rules may not apply ([Overview of OpenAI crawlers](https://developers.openai.com/api/docs/bots), consulted on November 12, 2026; the page shows no update date). - **What it answers:** which robots read the site, how often and which pages; whether the firewall or the CDN blocks them. - **What it does not answer:** it does not say whether a person visited the site. A request from a user agent is not a human visit. - **For the technical team:** filter the logs by user agent and by date range; for the method of checking each robot's access, see [the bot accessibility test](https://cookingmetrics.com/blog/test-accesibilidad-bots-ia/). The [Cloudflare technical guide for SEO and GEO](https://cookingmetrics.com/blog/cloudflare-seo-geo-guia-tecnica/) explains the CDN configuration. - **Privacy:** the logs contain visitor data (for example, IP addresses). Their handling must be reviewed against the site's privacy policy. [Section for signed-in readers, level C: https://cookingmetrics.com/blog/como-medir-trafico-asistentes-ia/#bloque-2] ## Layer 3: Google Search Console and Bing Webmaster Tools ### Google Search Console Google states that its AI features, AI Overviews and AI Mode, are counted in the Search Console performance report under the "Web" search type ([AI features and your website](https://developers.google.com/search/docs/appearance/ai-features), consulted on November 12, 2026). According to the help page on impressions, position and clicks, a click on an external link within AI Overviews or AI Mode counts as a click, and all the links in an AI Overview receive the same position ([What are impressions, position, and clicks?](https://support.google.com/webmasters/answer/7042828), consulted on November 12, 2026). - **What it answers:** Google performance and, in the [specific generative AI report](https://support.google.com/webmasters/answer/16984139), impressions for covered features. Google reports a global rollout; a property may not show it if data is insufficient. - **What not to infer:** an impressions view does not prove a separate breakdown of clicks or equal sessions. ### Bing Webmaster Tools Microsoft introduced AI Performance in Bing Webmaster Tools in public preview on February 10, 2026 and added "Topics Portfolio" (beta version) on October 13, 2026. The report measures citations, that is, the times the site appears as a source in AI-generated answers, in Microsoft Copilot, in Bing's AI summaries and in some partner integrations ([Introducing AI Performance in Bing Webmaster Tools Public Preview](https://blogs.bing.com/webmaster/2026/2/Introducing-AI-Performance-in-Bing-Webmaster-Tools-Public-Preview/), consulted on November 12, 2026). - **What it answers:** how many citations the site receives and which pages are cited, on Microsoft's surfaces. - **Limits that Microsoft states:** the total number of citations does not indicate placement within an answer; the average of cited pages does not indicate position or authority; and grounding queries are a sample of the total activity. - **What it does not answer:** it does not measure clicks or visits, and it does not cover ChatGPT, Gemini or Perplexity. ## Layer 4: Microsoft Clarity Microsoft Clarity offers a robot activity dashboard ("Bot activity") that shows how automated systems access content. Its metrics are the robot operator, the share of AI requests, robot activity and requests by path. It is based on server logs collected through integrations with compatible CDNs or servers, which are connected from Clarity's settings and may have costs depending on the provider ([Bot Activity overview](https://learn.microsoft.com/en-us/clarity/ai-visibility/bot-activity-overview), consulted on November 12, 2026). - **What it answers:** which robots visit the site and which paths they request, without having to analyze the logs by hand. - **Limits that Microsoft states:** a robot's activity does not indicate that the content was retrieved, grounded or cited in an AI answer, and the metrics may not translate into traffic, attribution or downstream outcomes. - **For the technical team:** it requires connecting a compatible CDN or server. The documentation consulted does not name Cloudflare on that page; it is worth confirming the compatibility of the CDN the site uses before planning it. [Section for signed-in readers, level C: https://cookingmetrics.com/blog/como-medir-trafico-asistentes-ia/#bloque-3] ## What cannot be measured These are the most likely blind spots. Except for the first one, they are reasonable hypotheses of this guide and not documented findings. - **Assistants that Google does not recognize.** The list of assistants in the "AI Assistant" channel is maintained by Google and the page does not explain how it is updated. - **Visits with no identifiable origin.** It is plausible that part of the AI traffic arrives without origin information and is classified as "Direct", which according to Google groups those who arrive through a saved link or by typing the address. It is not possible to know how much. - **Copied links and applications.** A person who copies a link from an assistant and pastes it elsewhere, or who opens it from an application, may leave no trace of the origin. This is a hypothesis. - **Exposure without a click.** An appearance may not generate a visit. Search Console reports impressions for its covered features and Bing reports citations for its own. They are different units and neither is an inventory of every AI answer. - **Broad captures.** An overly broad regular expression may add visits that do not come from assistants (see Layer 1). ## A validation procedure This procedure is a CookingMetrics method, **not yet tested on its own data**. It is useful for knowing how much to trust a number before using it. 1. **Define the question.** Decide whether you want to measure visits, crawling or citations (see above). 2. **Record the configuration and the date.** Note which channel or filter is used, which period is measured and which version of each tool was consulted. 3. **Manually review the captured sources.** In Google Analytics, list the distinct source values that the channel or filter captured in a period, and check one by one that they are AI assistants. Note how many are not. 4. **Cross-check with the logs.** If the server or the CDN keeps logs, check whether the AI robots that appear there match what Clarity shows and the visit peaks. 5. **Look at Search Console and Bing Webmaster Tools separately.** Do not add their figures to those of Google Analytics: they measure different things. 6. **Compare the same site with the same configuration over time.** A configuration change invalidates the comparison. 7. **Write down what could not be measured.** Record the blind spots alongside the report. [Section for signed-in readers, level C: https://cookingmetrics.com/blog/como-medir-trafico-asistentes-ia/#bloque-4] ## What not to conclude - That AI traffic converts better or worse than other traffic: this guide has no data of its own with its denominator, and it does not claim this. - That a measured number of visits represents all AI traffic: it is, at most, the identifiable minimum. - That more robot activity means more citations, more visits or more sales: Microsoft says so explicitly about its dashboard. - That a citation in Copilot is a citation in ChatGPT: they are different platforms. ## Limits of this guide - **Scope of the sources.** Each statement describes the platform that publishes it, with its consultation date. Definitions and reports change. - **No share or conversion figures.** No figure was verified in a primary source, and none are used. - **Procedure not executed.** CookingMetrics has not applied it to its own data; it is presented as a method. - **Not legal advice.** The handling of logs and the consent configuration should be reviewed against the privacy policy and with legal counsel. ## What to do next The next step is to take a baseline measurement: note which channel or filter the site uses today, manually review a sample of the captured sources and check what each console shows. From there, repeat it with the same configuration every month and record the changes. If you would like us to review your site's measurement, you can learn about our [SEO for AI search service](https://cookingmetrics.com/services/seo-ai-geo/). We review the configuration and support your team; we do not sell visibility tools. For the general framework, see [what GEO is](https://cookingmetrics.com/blog/que-es-geo-generative-engine-optimization/). ## Frequently asked questions ### Does Google Analytics measure ChatGPT traffic? It measures the visits that arrive with an origin that Google recognizes as an AI assistant; ChatGPT is among the examples of the "AI Assistant" channel. It does not measure visits with no identifiable origin or citations without a click. ### Do AI Overviews clicks appear in Google Analytics as AI traffic? No. Google documentation says the AI Assistant channel excludes AI Overviews and AI Mode. Search Console includes those features in search performance and offers a specific impressions view. Do not assume that this view also separates all their clicks. ### Is a custom regular expression needed? Not necessarily. The default channel may be enough. If you need to cover other assistants, a custom regular expression is an option; it is worth manually reviewing what it captures. ### What is the difference between a visit, a robot request and a citation? A visit is a person who arrives at the site. A robot request is a machine reading a page. A citation is an appearance of the site as a source in an answer, whether or not there is a click. They are measured with different tools. ### Is a visibility tool useful for measuring this? This guide does not use third-party visibility tools and does not recommend them for measuring your own traffic. The layers described measure the site itself. What those tools measure and why caution is advisable is explained in [AI visibility reports](https://cookingmetrics.com/blog/reportes-visibilidad-ia-que-miden-cuando-pagar/). --- ## About the author **[Martín Garay](https://cookingmetrics.com/about-martin-garay/)** — Founder of CookingMetrics I'm Martín Garay, founder and Martech Advisor at CookingMetrics and Chair of the Technology Committee at CACE, Argentina's ecommerce chamber. For more than 20 years I've worked in Analytics, development, technical SEO and ecommerce: I implement measurement, find where it breaks and turn it into information you can act on. ### My work at CACE, Argentina's ecommerce chamber - **Chair of the Technology Committee** (SINCE AUGUST 2025): I set the committee's agenda together with Gabriel Topola, vice-chair. We look at the platforms and tools an online business needs to grow: CMS, integrations, customer service and omnichannel operations. - **Curating the technical forum** (IT CAMP · ECOMMERCE DAY ARGENTINA): With CACE's Events team I put together the IT Camp programme: talks for engineering and development teams on platform architecture, code and good practice, given by speakers who do the implementation work. - **Marketing and Data Analytics committees** (SINCE 2016): I started in the Marketing committee and helped create the Data Analytics committee. I gave Google Analytics webinars, including the migration to GA4, and worked on the Google Analytics implementation for Hot Sale and Cyber Monday. - **Ecommerce metrics dashboard** (FOR MEMBERS): With the Data Analytics committee and the CACE Community team we built a dashboard in Google Analytics and Looker Studio so each member can check the key indicators of their own store. ### Talks - [From SEO to GEO: what it takes for a brand to be cited by an answer engine](https://www.youtube.com/watch?v=mlyjuSBdMzI) — ECOMMERCE DAY ARGENTINA 2026 · IT CAMP · AUGUST 27, 2026 · BUENOS AIRES CONVENTION CENTER - [SEO for AI: how to prepare a brand to show up in ChatGPT and Google's AI overviews](https://www.youtube.com/watch?v=4dI7jqnLg-M) — AI IN LATAM 2025 · BUENOS AIRES · OVER 3,500 ATTENDEES AND 100 SPEAKERS, PER THE ORGANIZERS ### Profiles and links - [Full profile](https://cookingmetrics.com/about-martin-garay/) - [LinkedIn](https://www.linkedin.com/in/seospecialistmartingaray/) - [Instagram](https://www.instagram.com/garaymartin/) - [YouTube](https://www.youtube.com/@MartinGaray) - [martingaray.com.ar](https://www.martingaray.com.ar/) - [Chair of the Technology Committee at CACE, Argentina's ecommerce chamber](https://cace.org.ar/pages/comision-de-tecnologia?utm_source=cookingmetrics.com&utm_medium=referral&utm_campaign=perfil-martin&utm_content=caja-autor) - [Ecommerce metrics dashboard, free for CACE members](https://cace.org.ar/pages/dashboard-de-metricas?utm_source=cookingmetrics.com&utm_medium=referral&utm_campaign=perfil-martin&utm_content=caja-autor) --- ## About CookingMetrics CookingMetrics provides Google Analytics consulting, measurement implementation and SEO. Founder Martín Garay brings more than 20 years of experience in Analytics, development and ecommerce. The work connects data with business decisions. ### Services - **[Google Analytics audit](https://cookingmetrics.com/data-analytics-consulting/)**: Do purchases or revenue differ from your store? We review your measurement and deliver a correction plan in 10 business days. [See the audit scope](https://cookingmetrics.com/data-analytics-consulting/). - **[Google Tag Manager](https://cookingmetrics.com/services/gtm/)**: Did events stop being tracked after a website change? We review tags, triggers and versions to find duplicates or missing data. [Ask about Google Tag Manager audits and implementation](https://cookingmetrics.com/services/gtm/). - **[Server-side measurement](https://cookingmetrics.com/services/cookieless-tracking/)**: We assess how to send data from your server, respect consent and prevent duplication. [What's included in server-side measurement](https://cookingmetrics.com/services/cookieless-tracking/). - **[Technical SEO](https://cookingmetrics.com/services/technical-seo/)**: Have you migrated your site, or are pages missing from Google? We review crawling, indexing, structure and performance. [How we approach technical SEO](https://cookingmetrics.com/services/technical-seo/). - **[SEO for AI search (GEO)](https://cookingmetrics.com/services/seo-ai-geo/)**: We review whether search engines and assistants can access your pages and understand their content. [What we can improve for AI search](https://cookingmetrics.com/services/seo-ai-geo/). ### Solutions - **[Google Analytics self-check](https://cookingmetrics.com/google-analytics-self-check/)** (Status: Available) - **[GA4 Report Generator](https://cookingmetrics.com/product/ga4-report-generator/)** (Status: Beta): A tool in beta that already generates Google Analytics reports. Ask about available features and the scope for your project. [Explore GA4 Report Generator](https://cookingmetrics.com/product/ga4-report-generator/). - **[IndexNow Connect](https://cookingmetrics.com/product/indexnow-connect/)** (Status: Available for Tiendanube): Notifies search engines participating in IndexNow of new, updated or deleted URLs. [How IndexNow Connect works](https://cookingmetrics.com/product/indexnow-connect/). - **[AI SEO Analysis](https://cookingmetrics.com/product/ai-seo-analysis/)** (Status: In development): *Coming soon.* An automated audit of how AI assistants and search engines access and use your content. [Learn about AI SEO Analysis](https://cookingmetrics.com/product/ai-seo-analysis/). **Let's talk about your measurement:** [Book a call](https://cookingmetrics.com/about-martin-garay/) · [CookingMetrics](https://cookingmetrics.com/)