AI traffic shows the visitors that ChatGPT, Perplexity, Gemini, Claude, Copilot and other AI assistants send to your site. Open Dashboard → Analytics → AI traffic.
It needs a Google Analytics 4 connection. Until you connect one, the page shows an example behind a short setup guide. To connect, open Settings → Integrations → Google Analytics and choose Connect. Stride reads the last 90 days on its next sync, which runs every six hours. Access is read-only: Stride never changes your Google Analytics setup.
What the page shows
-
The briefing: a dark card at the top that says what changed in the period you pick (7, 28 or 90 days) and the few things that matter most, with links to the detail.
-
The headline numbers: AI visits, what they were worth, and visits from the leading assistants, each compared with the same number of days before and with a daily trend line.
-
By assistant: visits from each assistant, with the change from the previous period.
-
Daily AI visits: a chart of this period against the previous one.
-
From AI answer to visit: each page on your site with the tracked prompts whose AI answers cite it, how often AI assistants fetched it (if you've connected crawler logs), AI visits, and visits that converted.
-
Value of AI visits: what those visits were worth in the period, with a daily trend line and how it compares with your Stride plan's monthly price. See How the value is worked out.
-
Do AI visitors convert?: the share of AI visitors who completed one of your Google Analytics key events, next to everyone else.
-
Where the gaps are: four lists, each ranked by what's at stake on the page (conversions, then AI visits):
- pages where AI visitors converted that none of your tracked prompts cite,
- pages AI assistants send visitors to that none of your tracked prompts cite,
- pages your tracked prompts cite that got no AI visits, with a link to improve the page,
- pages AI crawlers read that no answer cites and no AI visitor reaches (needs crawler logs).
For uncited pages, Stride suggests your own Google Search Console searches whose words match the page, and you can track one as a prompt in one click. These are word matches, not a measured link between a search and the page.
How the value is worked out
Stride uses the strongest reading it has, in this order:
- Purchase revenue. If Google Analytics records purchase revenue from AI visits, that's the value. It's measured, not estimated.
- A range from your own conversions. Otherwise Stride uses what you've said one conversion is worth in Settings → Site setup (for example your lead value or average job value). One end values AI visits at your site's average conversion rate. The other is the AI visits that actually converted × that value. This is an estimate: a key event isn't always a sale.
- A research-based range. With no conversion data, the page shows the same per-month range as the Dashboard. Published research finds AI visitors convert 3–7× a site's average rate.
The plan comparison scales the value to a month and divides it by your plan's list price, using the lower end of a range. It's shown only for the first two readings, never for the research-based range. The Dashboard's revenue box uses the same value for the last 28 days, and falls back to the research-based range.
How to read the numbers
- They're a floor, not the full count. AI apps often hide where a visitor came from, so visits from the ChatGPT, Claude or Gemini mobile apps, and from links people copy and paste, show up in Google Analytics as Direct.
- Google AI Overviews and AI Mode count as Google Search. Google doesn't tell websites which of its features sent a visitor, so these can't be separated from regular search.
- Only complete days count. The period ends yesterday, and the last two days can still change while Google Analytics finishes processing them.
- One count everywhere. The Dashboard's Visitors From AI box shows this same count for the last 28 days, and Analytics shows it for the period you pick. Until the first daily read finishes, both show the last full calendar month against the month before.
- Comparisons wait for complete data. If Stride hasn't read the whole earlier period yet, for example right after you connect, the page says so instead of showing a drop.
- Conversions are your key events. Stride counts a visit as converted when it included at least one event you've marked as a key event in Google Analytics. With no key events marked, the page asks you to add them rather than showing 0%.
- Citations and visits are separate readings. Citations come from your latest completed full scan; visits come from Google Analytics for the period you picked. Seeing both on the same page shows they're associated, not that one caused the other.
- Small or private sources may be missing. When Google withholds low-volume rows to protect visitor privacy, or groups rare ones into "(other)", the page notes it.
Which assistants are recognized
ChatGPT, Perplexity, Claude, Gemini (including NotebookLM), Microsoft Copilot,
Grok, Meta AI, DeepSeek, Mistral Le Chat, You.com, Phind, Duck.ai, Qwen, Poe
and iAsk. Stride matches the site a visitor came from, and the utm_source
tag ChatGPT adds to links it cites. Copilot inside Bing and Grok inside X can't
be told apart from Bing search and X, so they count there.