Google Analytics 4 reports
The GA4 reports show what visitors do after they arrive, beside the Search Console data that shows how they found you. This page covers connecting, how a GA4 property is matched to a site, the reports, how LLM traffic is grouped and the blended view.
✓ Checked in the workspace code · 7 October 2026
GA4 beside Search Console
The Google Analytics group in the property sidebar shows what visitors do after they arrive, using your GA4 data, next to the Search Console data that shows how they found you. The sessions, key events, e-commerce and revenue figures remain GA4 figures; the workspace does not turn them into Search Console metrics. Reading both side by side is the point, and the differences between them are explained in the glossary entry on clicks.
Connecting GA4
- Allow GA4 access. The workspace asks for read-only Analytics access only when you connect GA4. Without it, GA4 pages answer that the Google login lacks the analytics.readonly permission and ask you to reconnect.
- Pick the GA4 property. The list comes from the Google account you signed in with.
- Check it is the right one. See the warning below.
How a GA4 property is matched to a site
The workspace tries to pair the Search Console property with a GA4 property by comparing the site’s host, and its first label, with the GA4 property name and account name. When one matches, it is selected. When nothing matches, it falls back to the first property in alphabetical order and leaves the selector visible so that you can correct it.
Always confirm the property. A wrong pair does not produce an error, it produces plausible numbers for another site.
The GA4 reports
| Report | What it shows |
|---|---|
| Channels, Sources | sessions by channel group and by source and medium |
| Pages, Landing Pages | engagement by page and by the page where sessions start |
| Error Pages | pages that served errors to visitors |
| Countries | sessions by country |
| E-commerce, Key Events | purchases and revenue, and the events you mark as key |
| LLM Traffic | sessions that came from AI assistants |
| Blended (GSC + GA4) | Search Console clicks and GA4 sessions in one chart |
Periods, comparison modes and weekday matching work as in dates and comparisons, and the currency and time zone are taken from the GA4 property.
LLM Traffic: how sources are grouped
The report looks at the source of each session and groups those that contain a known marker: ChatGPT, Google Gemini, Microsoft Copilot, Perplexity, Claude, You.com and Phind. A session counts as AI traffic only when its source text matches, so visits that arrive without a referrer are not attributed. Treat the figures as a lower bound, not as the full effect of AI assistants.
Blended: clicks and sessions together
The blended view draws Search Console clicks and GA4 sessions by day, week or month from the two Google APIs. The two lines rarely match, for the reasons listed under clicks: privacy filtering, processing, time zone and JavaScript. Look at the direction and the timing of changes in both rather than at their ratio.
If something looks wrong
| Symptom | Cause and fix |
|---|---|
| “Google login is missing the GA4 permission” | reconnect Google and allow GA4 access |
| “No GA4 properties are available” | the signed-in Google account has no GA4 property; sign in with the right account |
| Numbers do not fit the site | the automatic match chose another property; select the correct one |
| An Analytics API “has not been used” error | the Google API is disabled for the project; it must be enabled by the administrator |
| Numbers are 10 minutes old | responses are cached for 10 minutes |
GA4 reports, answered
Are GA4 numbers converted into Search Console numbers?
No. Sessions, key events and revenue stay GA4 figures.
Why do clicks and sessions differ?
They are measured by different tools with different rules.
Does LLM Traffic count every AI visit?
No. Only sessions whose source text matches a known assistant.
Continue
Next, see workspace and properties and team access, where GA4 can be switched on per teammate.