Machines on the server. Humans in GA4. One picture.
Server-side logging sees every crawler but can't follow a human through a purchase. GA4 follows humans but is blind to every bot. Connect them and you finally get the full loop: what the machines read, and what that reading sends back.
AI traffic happens in two places. You're measuring one.
When ChatGPT answers a question with your content, two measurable events occur. First, a crawler fetched your page - visible only at the server. Later, maybe, a human clicks through to you - visible only in browser analytics. Most sites measure neither; the rest measure one and call it the whole story. The interesting number is the ratio between the two: how much crawling does one real visitor cost you? That ratio is the economics of your content in the AI era, and computing it requires both halves.
Machines read
GPTBot, ClaudeBot, and PerplexityBot fetch your pages. Viz logs and classifies every one of those requests inside WordPress - browse the bot directory to see who they are.
Answers get given
Somewhere on another company's servers, your content becomes part of an answer. Some answers cite you. Paid plans track how the major engines describe you - see AI Visibility.
Humans (sometimes) arrive
A reader clicks the citation. That session lands in GA4 with an AI referrer, and Viz pulls it into the same dashboard as the crawl that started the chain.
The AI Traffic view.
AI-referred sessions
Sessions that arrived from ChatGPT, Perplexity, Gemini, and other assistants, pulled from your GA4 property and shown next to the crawl data that earned them.
Engagement, not just arrivals
AI referrals are often high-intent - the assistant already answered the easy part. See engagement and conversions for these sessions, not just a count.
Search Console context
Classic search impressions and clicks alongside AI crawl volume, so you can watch whether AI answers are eating into queries you used to win in blue links.
One view, both halves
Machines on one side, humans on the other, in the same wp-admin dashboard. No more stitching a GA4 exploration to a hosting log by hand.
AI referrals undercount. Read them accordingly.
The web's referrer mechanism predates AI assistants, and it shows. A click from a browser tab on chatgpt.com usually announces itself; the same recommendation followed from a mobile app, a voice interface, or a copy-pasted link arrives with no referrer at all and books as direct traffic. Different assistants, different surfaces, different leakage - and none of it under your control. Any tool that hands you an “AI traffic” number without saying this is rounding a floor up to a total.
The honest reading treats attributed AI sessions as a sample, not a census: solid for direction and quality, soft on absolute volume. In practice that means watching three things together - attributed sessions trending in GA4, the engagement of those sessions against your site average, and retrieval-bot crawl volume on the server side as the channel's leading indicator. When crawls rise and attributed quality holds, the channel is growing even while part of it hides inside direct.
Read-only, aggregate, and reversible.
The integration reads reporting aggregates from Google's APIs - it does not add tracking to your pages, does not send your visitors' data anywhere, and can be disconnected at any time. Viz's own measurement stays where it always was: in your database, on your server, under your retention rules.
Integration FAQ.
Why do I need GA4 if Viz already logs every request?
They measure different halves. Viz sees every machine that touches your server, but a server log cannot follow a human through a session, an engagement, or a conversion - that is what GA4 is built for. Joined together, they answer the question neither can alone: does being crawled by AI ever turn into humans who buy, subscribe, or read?
What access does Viz get to my Google account?
Read-only API access to the GA4 property and Search Console site you choose. Viz reads aggregate reporting data; it does not write to your Google account, and Google OAuth tokens never touch your WordPress server.
How does Viz know a session came from an AI assistant?
By referrer. When someone clicks a link in ChatGPT or Perplexity, the browser typically reports chatgpt.com or perplexity.ai as the referring site, and Viz segments those sessions out of your GA4 data. Some AI surfaces strip the referrer, so treat the number as a floor, not a ceiling - a limitation of the web platform, not of any one tool.
Is the integration required to use Viz?
No. All server-side analytics - classification, dashboards, the request log, and AI Control blocking - work with the plugin alone. The integration adds the human half of the picture when you want it.
My AI-referred session count looks tiny. Is the channel not working?
Check the quality before judging the quantity. AI referral counts systematically undercount - apps and some assistant surfaces open links without a referrer, so a share of the channel books as direct. The sessions that do carry a referrer are your sample: if their engagement and conversion beat your site average, the channel is working and the true volume is higher than the chart shows. Compare the trend against your retrieval-bot crawl volume to see whether the pipeline that produces those referrals is growing.