Traffic & conversions
Traffic & conversions — sessions, AI referrals and the gap between clicks and visits
GA4 or the first-party page beacon for sessions, engagement and conversions; AI referrals and crawler fetches from the probe; the same page row as search clicks and audit findings. Each source keeps its own window and limit.
Last reviewed 2026-11-17
Both plans include the Traffic tab; Pro adds daily AI sampling and the monitoring suite — see pricing.
What the Traffic tab answers
Page views, sessions, engaged sessions, average duration, bounce rate, top pages, sources and channels, and countries — from GA4 or the first-party beacon. GA4 conversions appear when a property is bound, and every page row joins the same path to Search Console clicks.
Each block names its own source and window before it shows a number.
| Block | Source | Window | Value |
|---|---|---|---|
| Traffic | Page beacon | Selected window | 2,340 sessions |
| Search | Search Console | 28d | 1,284 clicks |
| Crawlers | Server probe | 28d | 96 AI fetches |
| AI referrals | Beacon + probe | 28d | 31 visits · floor |
| Vitals | Field samples | 28d | LCP 1.9s · p75 |
Demo data. Every block names its source and window; a missing source is na.
GA4 or the first-party page beacon
GA4 contributes sessions, engagement and conversions under its own consent rules. The page beacon records page views, sessions, referrers and field vitals for the window you selected, and it fills the Traffic block when GA4 returns no rows.
The two sources are not blended. GA4 page detail is a 7-day snapshot of the top 20 organic landing pages; conversions always use GA4's last 7 days; a page outside the top 20 reads na. None of this is full-funnel attribution.
GA4 property
Sessions, engagement and conversions for the property you bound. Consent, thresholding and GA4's own session definition apply.
First-party page beacon
Page views, sessions, referrers and field vitals for the selected window. Same-origin and no third-party account; a visitor who blocks the script is not counted.
AI referrals and crawler fetches
AI referral sessions are counted by landing page from the beacon: a visit whose referrer host is an AI surface. Apps and privacy browsers strip referrers, so this is a floor, not a total. The server probe records what a page script cannot: AI crawler fetches, blocked paths, 404s, invalid crawls and machine-file reads.
The beacon cannot see AI crawlers because they do not run JavaScript. A crawler that never executes the page leaves no client event; the probe sees the request at the server.
Tracking gaps: clicks with no sessions
The console flags a page when its search clicks have no matching sessions: zero sessions after 20 clicks, a sessions/clicks ratio below 0.1, or a top-20 landing page with 5 or more clicks and zero sessions. Work through the tag and consent checks before changing the page:
- Confirm the GA4 tag loads on the page that earns the clicks, not only on the homepage.
- Check consent: before opt-in, analytics can be blocked, and consent mode can delay or drop the session.
- Follow redirects and host variants: a www or http hop can split the landing page or lose the referrer.
- Match the property and data stream to the site, then compare one raw page view with the Search Console clicks for the same URL.
A gap is a diagnostic, not a cause claim. It says two sources disagree; it does not say which one is wrong.
How it joins the page
The page dossier shows the Traffic block (beacon or GA4), the AI referrals block, and the same row in per-page opportunities. Search clicks, sessions, AI referrals, crawler fetches and open findings stay in one row, each with its own source and window.
| Signal | Source | Window | Limit |
|---|---|---|---|
| Traffic | Page beacon | Selected window (7, 28 or 30 days) | First-party sessions and page views; referrer stripping limits source attribution. |
| Conversions | GA4 | Last 7 days | Only when GA4 is bound; consent and thresholding reduce coverage. |
| AI referrals | Page beacon + server probe | 28 days | Referrer stripping makes visits a floor; fetches prove access, not a visit. |
| Crawlers | Server probe | 28 days | Records fetches, blocked paths, 404s and invalid crawls; not traffic. |
| Vitals | PageSpeed Insights or page beacon | 28 days | Field p75 needs 20 samples per page and metric; PSI is lab data and stays separate. |
| Page join | Read-time join | Mixed: beacon or GA4, Search Console 28d | Per page, never per query; a missing source reads na. |
A missing source reads na, never 0. Zero is a measurement; na means the source was not connected, had no rows in the window, or the page sat outside the GA4 top-20 snapshot.
Limits
The report stops where the evidence stops.
- No estimated traffic. The console reports observed sessions and page views, not modelled or extrapolated totals.
- No ad attribution. Visits are not connected to ad spend, campaigns or Google Ads.
- No cross-device identity. Sessions are first-party and anonymous; one person on two devices counts twice.
- No full-funnel revenue attribution. Conversions are GA4's numbers; the console does not claim which click, answer or page caused revenue.
- GA4 page coverage is a 7-day top-20 snapshot. Pages outside it read na.
- Consent and EU rules apply. Analytics can be blocked or reduced before either source records a visit.
Frequently asked questions
Sources & windows
What is the difference between GA4 and the first-party page beacon?
GA4 supplies sessions, engagement and conversions inside its consent and thresholding rules. The page beacon records page views, sessions, referrers and field vitals for the window you selected, and it fills the Traffic block when GA4 has no rows. The report names which one it used.
Why is GA4 page detail only a 7-day top-20 snapshot?
That is the shape of the stored GA4 digest: the top 20 organic landing pages over 7 days. Conversions always use GA4's last 7 days. A page outside the top 20 reads na, not zero, because the source has no row for it.
Does consent change the numbers?
Yes. Before consent, analytics can be blocked, and consent mode can delay or drop events before GA4 records them. The beacon has its own disclosure obligations. A difference between the two sources can be legitimate.
AI traffic
How are AI referral sessions counted?
The beacon records a session whose referrer host is an AI surface and keeps the landing page. Referrer stripping makes the count a floor; no missing visit is estimated.
Why do AI crawlers need the server probe?
AI crawlers do not run JavaScript, so a page beacon never sees them. The probe records the request at the server: agent, path, response status and blocked or invalid crawls.
Can I tell which AI answer sent a visit?
No. The report joins by landing page and session, not by answer or person, and it does not claim a citation caused a visit.
Diagnostics
What does a tracking gap mean?
The console flags clicks with no matching sessions: zero sessions after 20 clicks, a sessions/clicks ratio below 0.1, or a top-20 landing page with 5 or more clicks and zero sessions. It is a diagnostic, not a cause claim.
Why does a missing source read na instead of 0?
Zero is a measurement; na means the source was not connected, had no rows in the window, or the page was outside GA4's top 20. Rendering na as 0 would turn a missing source into a fake result.
Can this report attribute revenue to AI referrals?
No. There is no ad attribution, no cross-device identity and no full-funnel revenue attribution. The report shows observed sessions, conversions from GA4 and the source limits beside them.
Start with one source
Connect GA4 or install the beacon
Both plans; Pro adds daily AI sampling and the monitoring suite.