Google Analytics
Answer Share says how often the answers name you. Analytics says what that earned: the sessions and conversions that ChatGPT, Perplexity, Gemini, Copilot, Claude and the others sent, day by day, page by page, next to organic search and direct for scale. Connect it and the site’s Traffic and visits view (under Crawlers & access) gains its AI assistants view, and the figure follows the site into Results, the board brief, the quarterly review and the monthly brief. It comes with Growth, Portfolio and Enterprise.
Connecting
Section titled “Connecting”On the site’s Setup tab, under Google Analytics, Connect Google Analytics opens Google’s consent screen for the account that can read the property. Vercatus asks for the Analytics read-only scope and your email address, nothing else; the Search Console connection is separate and keeps its own scope. The property whose web stream is on the site’s host is chosen; if none matches, Setup lists the properties the account can read and asks. The first sync reads the last three days and the newest weeks at once, and the rest of thirteen months fills in over the day; from then on the last three days are re-read daily, because Analytics restates recent days.
An admin can disconnect at any time; the token and the stored rows are removed.
What is read and kept
Section titled “What is read and kept”Three reports a day from the Analytics Data API: sessions, engaged sessions, key events and users by day and traffic source; the same by landing page for AI assistants and organic search; and the key events by name. What is kept is aggregates by day, source and landing page, for thirteen months. Nothing about a person is read or stored.
What the AI assistants view shows
Section titled “What the AI assistants view shows”- One sentence: how many sessions AI assistants sent in the last 28 days against the 28 before, which assistant sent most, how many key events came from them, and what organic search sent for scale.
- Four figures: AI-referred sessions, the engaged share, key events from AI, and AI’s share of all sessions.
- The chart: sessions from AI assistants by day, stacked by assistant, over 90 days, with each completed run and each recorded fix marked on the axis so a change can be read against what followed. Organic search can be switched on in the legend.
- By assistant: sessions, change, engaged share, key events.
- Landing pages AI sends people to, with which assistants sent them.
Read it as a floor
Section titled “Read it as a floor”These figures undercount, and the tab says so. In-app browsers and some assistants strip the referrer,
so part of the AI-referred traffic arrives as direct. Google’s AI Overviews and AI Mode arrive as
google / organic and cannot be told apart from classic search in Analytics. Treat the AI figures as
“at least”, and the direction over time as the thing to watch.
Where the figure appears
Section titled “Where the figure appears”- Results: an outcome, the sessions AI assistants sent in the window against your starting point; see Results. An outcome, not proof: a verdict is what says whether a play worked.
- The board brief and the quarterly review: the same figure, site by site.
- Monthly brief: the same figure, against last month.
- AI demand: the sessions are shown beside a topic’s demand estimate as a floor. They never scale it; see Topics and AI demand.
- Goals: two figures to aim at, the sessions and the key events AI assistants sent in the last 28 days, summed over the goal’s sites.
- Alerts: a weekly check for a drop of more than 30% against the four weeks before; see Alerts.
How it fits
Section titled “How it fits”A topic’s answers show which pages the engines cite; the AI assistants view shows which pages they send people to. Together they tell a page that is cited but not visited from one that is visited but not cited.