TL;DR
Most marketing teams treat AI as a black box. Brand visibility is "improving" or "declining" in the aggregate, but no one can tell you how many ChatGPT users actually arrived at your site this week, which page they landed on, or which AI assistant sent them. The infrastructure to measure AI as a channel exists today — almost no one is wiring it up. There are three layers worth tracking (bot crawls, AI referral traffic, and citation share across models) and one layer (revenue attribution from AI-originated visits) that the industry has not solved yet. This piece explains each.
The blind spot
Walk into a marketing meeting and ask "how much pipeline did AI-sourced traffic generate this quarter?" You will get one of two answers: a number that nobody can verify, or an admission that nobody is tracking it. Both are bad answers when AI is increasingly where buyer research happens.
The reason is not laziness. The analytics stack built for the SEO and SEM era does not capture AI as a discrete source. Google Analytics buckets chat.openai.com referrers into "Direct" or "Other" by default. Your CMS does not know GPTBot from googlebot. Your dashboards were not designed for "answered in an AI response without a click." The channel is invisible until you measure it deliberately.
Layer 1: Bot crawl events
AI models cannot cite content they have not read. The first thing worth measuring is which AI crawlers are actually hitting your pages, how often, and which pages they prioritize.
The named crawlers to look for: GPTBot (OpenAI / ChatGPT), ClaudeBot (Anthropic), PerplexityBot (Perplexity), Google-Extended (Gemini), and Bingbot (Bing index, which feeds ChatGPT search). Each has a verifiable user-agent string, and in most cases published IP ranges.
A simple version of this: log every request with a known AI crawler user-agent to a separate events table. A better version: attach each event to the specific URL crawled, so you can see "GPTBot has read this page 47 times in the last 30 days, but ignored that one entirely." That is a signal about which content is worth doubling down on.
Most teams who actually look at this discover that their own robots.txt is blocking one or more AI crawlers — usually by accident, inherited from a default CDN config or a security tool. Fixing that alone often closes 20-40% of the gap.
Layer 2: AI referral traffic
When an AI assistant cites you and a real human clicks through, you can see it. The referrer header points back to the AI platform: chat.openai.com, claude.ai, perplexity.ai, you.com, phind.com, and a growing list. Tag those referrers explicitly. Do not let your analytics tool dump them into "Other" or "Direct."
What you want to know per visit:
- Which AI assistant sent them
- Which page they landed on
- What they did next (read, scroll depth, click)
- Whether they came back
This is where AI starts to look like a real channel: visits you can attribute, sessions you can analyze, pages you can rank by AI-source performance. It is also the moment you can answer the question your CFO actually wants answered, which is "is this real?"
Layer 3: Citation share across models
The hardest layer to measure, and the most strategically important. For a given buyer query — "best LMS for ServiceNow customers," "how to migrate off Cornerstone," whatever your category equivalent is — which AI models cite you? Which cite competitors? Which cite neither?
This requires actively scanning AI models against your target prompts, not just waiting for them to find you. Done right, it is not "run every prompt against every model every day," which is wasteful and expensive. It is tiered: high-priority prompts get checked weekly across multiple models, long-tail prompts get checked monthly against one. The goal is share-of-voice tracking, not exhaustive coverage.
The output is a table that tells you, for the queries that matter to your funnel, where you stand vs. competitors across the AI surfaces your buyers actually use.
The layer we cannot track yet
Revenue attribution from AI-originated visits is unsolved at the platform level. You can see GPTBot read your page. You can see a human arrive from chat.openai.com. You can see them book a demo. What you cannot see, reliably, is the chain in between: which prompt they asked ChatGPT, which response they saw, whether they followed your citation or someone else's, and how that influenced the eventual buying decision.
Anyone selling you a clean "AI-attributed revenue" number today is either guessing or counting last-touch only. The honest version: measure what you can (layers 1-3), build the leading indicators, and treat AI-influenced revenue the same way most teams treat brand or PR — directionally, with multi-touch logic, not as a single attributable line item.
This will get better. It is not better today.
What to do this week
If you do nothing else, do these four things in the next 60 minutes:
- Pull your
robots.txtand confirm it does not block GPTBot, ClaudeBot, PerplexityBot, or Google-Extended. If it does, fix it. - Filter your analytics for referrers from
chat.openai.com,claude.ai,perplexity.ai. Count them. That is your baseline. - Pick five buyer queries that should mention you. Run them in ChatGPT and Perplexity manually. Note whether you are cited, whether competitors are, and which sources the model used.
- Decide whether AI is worth instrumenting properly. If your
chat.openai.comreferrer count is already non-zero, the answer is yes.
None of these require a vendor. They are all things a marketer with a laptop can do today. The measurement gap most teams have is not a tooling gap. It is an attention gap.
How we approach this
At Context Memo, every memo on a customer subdomain automatically logs bot crawl events per URL and AI referral attribution per visit. Per-memo performance dashboards combine both signals. Visibility scans run tier-based against your target buyer prompts, not flat against everything. The point is not to give you a single "AI score." It is to give you the three layers a marketing team would otherwise have to build from scratch — so you can answer the "is this spend working" question with data, not vibes.