Updated 2 October 2026.
Two kinds of AI Overview tracking: who gets cited, and who gets the click
When people say “AI Overview tracking” they usually mean one of two different questions. The first is visibility: which of my keywords now show a Google AI Overview, and is my site one of the sources it cites? The second is impact: when an AI Overview does appear, what happens to the clicks my page used to get — and when it cites me, how many people actually click through?
Most tracker tools answer the first question. This one answers the second. If you need the visibility half, the free AI Overview citation checker tells you whether a page is being cited for a query right now, and the Prompt Observatory re-asks Perplexity and Claude every week and records who gets named. Use those to learn whether you appear. Use this page to learn what appearing is worth.
Why AI Overview clicks are invisible in GA4 by default
Google does not give AI Overview clicks their own source or medium. A visitor who clicks your page from inside an AI Overview arrives as google / organic, indistinguishable from someone who clicked a classic blue link. Search Console is no help either: AI Overview impressions and clicks are folded into ordinary web search performance with no filter to separate them. So the biggest change to search since mobile shows up in your analytics as a line that reads exactly as it did before.
There is one tell. When Google links to a source from an AI Overview or a featured snippet, it appends a scroll-to-text fragment to the URL — the #:~:text= suffix that makes your browser jump to and highlight the quoted passage. That fragment is the fingerprint of an AI Overview click, and it is what this tracker listens for.
How the tracker works
The tool has two parts, and you can use either without the other.
1. AI-engine traffic from your GA4 property
Connect your Google Analytics 4 property and the tool surfaces the sessions that arrived from AI engines — ChatGPT, Perplexity, Gemini, Copilot and others — which GA4 records but buries among dozens of referral sources. You see them as one view: which engines send you people, to which pages, and how that is trending. Nothing is installed for this part; it is a read of data you already have.
2. The short tracker snippet for AI Overview clicks
For Google’s own AI Overviews and featured snippets, the tool gives you a small script to place before </body> on your site. It sends the event through GA4’s gtag when that is present, and otherwise pushes it to the dataLayer for Google Tag Manager to forward (see setup). On every page load it reads the landing URL for the #:~:text= fragment; if it is there, it records a GA4 event for that landing. The fragment does not say whether the click came from an AI Overview or a featured snippet, and a link shared via Chrome’s “Copy link to highlight” carries it too, so the count is AI Overview plus featured-snippet clicks, with the occasional shared highlight link mixed in; none of them can be separated from the fragment alone. The same snippet also tags landings whose referrer is an AI engine as ai_referral, so the two parts cross-check each other. From that point on, AI Overview clicks are a countable thing in your own analytics — by page, by day, alongside everything else you already measure.
Setting it up
- Have GA4 running. If gtag.js is loaded directly, the snippet calls
gtag()itself. If you use Google Tag Manager,gtagis usually not a global function; the snippet then pushesai_overview_referralto the dataLayer, and you must add a Custom Event trigger forai_overview_referralwired to a GA4 Event tag, or the event never reaches GA4. - Connect the property in the tool above to see AI-engine referral traffic. This needs read access only.
- Paste the tracker snippet immediately before the closing
</body>tag, site-wide. In WordPress that is a footer-scripts field, a header/footer plugin, or your theme’s footer template. - Verify the event. Open one of your pages in Chrome with
#:~:text=anythingadded to the URL, then look for anai_overview_referralevent in GA4’s DebugView or Realtime report (allow up to a minute). That proves the plumbing before you wait for real traffic. If the event does not appear in Chrome, re-copy the snippet from this page; an earlier version read the fragment in a way Chrome hides. - Leave it running. AI Overview clicks are low-frequency per page; the signal is in the trend over weeks, not the count on day one.
Finding it in GA4
The snippet sends one event, ai_overview_referral, with two parameters: ai_source, which is google_ai_overview when the text fragment was present and ai_referral when the referrer was an AI engine, and page_path, the page that received the click. To report on it, register ai_source as an event-scoped custom dimension in GA4 (Admin → Custom definitions); until you do, the parameter is collected but not available in standard reports. Once registered, an exploration filtered to the ai_overview_referral event, with the built-in Page path and screen class dimension as rows and ai_source as columns, gives you the per-page view the next section assumes.
Reading the numbers once they arrive
The useful comparison is not AI Overview clicks on their own but AI Overview clicks against the organic clicks the same page used to get. Three patterns are common.
- Organic down, AI Overview clicks near zero. The likeliest reading is that an AI Overview now answers the query above your listing without citing you — but a plain ranking drop looks identical here, so confirm with the citation checker before acting. If it is displacement, the fix is on the content side: the AI visibility checker will tell you why the engine cannot quote you.
- Organic down, AI Overview clicks rising. You are cited, and the citation is now how people reach you. Fewer total clicks, but plausibly higher intent: these visitors arrive having already read a summary that named you.
- Organic flat, AI Overview clicks appearing. The best case — the Overview is additive. Protect whatever the cited passage is; it is doing work.
The zero-click toolkit goes deeper on sizing what displaced clicks cost in revenue.
What this tool does not do
It does not tell you which keywords trigger AI Overviews, or whether a given page is cited for a given query — that is the visibility question, answered by the citation checker. It does not ask the answer engines who they recommend — that is share of model, and the Observatory does it weekly against Perplexity and Claude. And it only counts what Google marks: a click that arrives without the text fragment is counted as ordinary organic, because that is all the evidence there is. Treat the AI Overview number as a floor, not a ceiling.
Free, and what the paid tier adds
Connecting GA4 and using the tracker snippet is free — no card, not a trial, alongside 77 other free tools that do not expire. Pro at $49 a month adds the Observatory: weekly share-of-model tracking against named competitors, so that once you can measure what AI Overview clicks are worth, you can also watch whether you keep earning them.
Frequently asked questions
How does it detect AI Overview clicks?
When a user clicks a source inside a Google AI Overview or featured snippet, Google appends a scroll-to-text fragment (#:~:text=) to your URL. The tracker snippet detects that on landing and records a GA4 event, making those clicks measurable.
Do I need anything installed?
You need Google Analytics 4 on your site and to connect it here. AI-engine referral traffic then appears automatically; AI Overview capture needs the short tracker snippet this tool provides.
Doesn’t Google Search Console already show AI Overview clicks?
No, as of October 2026. Search Console includes AI Overview impressions and clicks in its web search totals but offers no way to separate them from classic results. You can see your overall clicks fall; you cannot see from Search Console alone that an AI Overview is the reason.
Will the snippet slow my site down?
No measurable amount. It is a short script that reads the landing URL once on load and, only when the fragment or an AI referrer is present, sends a single event through the GA4 library you already run.
Is the text fragment on every AI Overview click?
Google adds it when it links to a specific cited passage, which is the normal case for AI Overview and featured-snippet sources. It is not a documented guarantee, so a click that arrives without it is simply counted as organic. The number you get is therefore conservative.
Does it count featured-snippet clicks too?
Yes, unavoidably. Google uses the same text fragment for featured-snippet source links, and the fragment carries no marker saying which surface produced it. The event therefore counts AI Overview and featured-snippet clicks together. If you need the two separated, the citation checker tells you which of your keywords show an Overview, which lets you reason about the split per page.
Does it work with Google Tag Manager?
Yes, with one extra step. On a GTM-only site gtag is normally not a global function, so the snippet pushes ai_overview_referral to the dataLayer instead of calling GA4 directly. Add a Custom Event trigger for ai_overview_referral and attach it to a GA4 Event tag with two Data Layer Variables, ai_source and page_path, mapped as event parameters. Without that trigger the push lands in the dataLayer and goes no further.
Can I see competitors’ AI Overview presence with this?
Not here — this tool reads your own analytics, which only know about your own visitors. Which pages Google’s AI Overview cites for a query is what the citation checker is for; the Observatory does the same weekly for Perplexity and Claude.
What is a good number of AI Overview clicks?
There is no universal benchmark; it depends entirely on how many of your queries show an Overview. Compare against yourself: the share of a page’s traffic arriving with the fragment, tracked week over week, is the figure that tells you whether AI search is becoming a channel for you or taking one away.
Does it work without GA4?
No. Both parts depend on Google Analytics 4 — the traffic view reads your property, and the tracker snippet sends its event through gtag, or to the dataLayer for Google Tag Manager to forward to GA4. Sites on other analytics platforms can adapt the detection idea (read the landing URL for #:~:text=) but this tool is built for GA4.