Skip to content

Guides

GA4: sessions, conversions and the seven-day page snapshot

Bind a property, read sessions, engagement and conversions, understand the 7-day top-20 page snapshot, and diagnose clicks with no sessions.

Guide · GA4

Open in ChatGPTAsk questions about this pageOpen in ClaudeAsk questions about this page

GA4 answers a different question from Search Console: not what Google sent, but what happened after the click. Bind one property per site, then read sessions, engagement and conversions beside search clicks — and get a straight answer when clicks arrive and sessions do not. The binding is read-only; the console never changes your GA4 configuration.

Bind a GA4 property

  1. Connect Google with Analytics access

    One Google grant covers Search Console and Analytics scopes. If the grant exists but lacks Analytics, the console says so and offers Reconnect Google — approving the consent screen again adds the scope without touching the Search Console binding.

    Console → Search → Traffic → Connect

  2. Pick the property for this site

    Only properties your Google account can see are listed, and the binding is per site. A property can serve one site; a second site needs its own binding. Connect, then give the history import a moment — it starts on its own.

    Console → Search → Traffic → Connect → select property

  3. Read the diagnosis before trusting numbers

    The check reports the number of web data streams and whether enhanced measurement is on. No stream means the property has nothing to receive events; multiple streams mean you must confirm the site sends to the intended one. A failed history import does not undo the binding — open Tracking check and retry.

    Console → Search → Traffic → Tracking check

  4. Disconnect or rebind

    Disconnect clears the binding for this site. Rebinding starts from the property list again and re-runs the same checks, so a wrong property is one click away from being fixed — and one click away from being the wrong one, so read the property name.

    Console → Search → Traffic → Connect → Disconnect

The seven-day page snapshot

The page row, the opportunities table and the dossier read a stored GA4 digest: the top 20 organic landing pages over the last 7 days, with sessions, engaged sessions, engagement rate, conversions and views. That shape does not stretch to the selected window. Choose 28 or 30 days and the page row still shows the 7-day GA4 numbers, and the console says so in the header rather than quietly mixing windows.

In that join, conversions always use GA4's last 7 days, whatever window the report is set to. A page outside the top 20 reads na, not zero — the digest simply has no row for it. That is also why a low-traffic page can look empty here while it still has clicks in Search Console: the source is missing, not the traffic.

The GA4 tab itself is a report and follows the Traffic window. Pages shows organic landing pages for that window, Content shows top pages by views across all traffic, and Sources shows the search and AI referral split behind sessions. Use the tab for the wider view, and the page row for the per-page join.

Clicks with no sessions

Tracking check compares Search Console clicks with GA4 sessions over the last 7 days. It flags a gap under one of three conditions: zero sessions after at least 20 clicks, a sessions-per-click ratio below 0.1, or a top-20 landing page with 5 or more clicks and zero sessions. Below 20 clicks the card says there is not enough data instead of guessing.

When a gap fires, work the four usual causes in order:

  1. Tag placement. Confirm the GA4 tag loads on the page that earns the clicks, not only on the homepage.
  2. Consent. Before opt-in, analytics can be blocked; consent mode can delay or drop the session entirely.
  3. Redirects and host variants. A www or http hop can split the landing page or lose the referrer.
  4. Property and stream. Match the property and its web data stream to the site, then compare one raw page view with the Search Console clicks for the same URL.

The one-page Search Console + GA4 audit walks the same comparison end to end when clicks and sessions disagree.

The gap is a diagnostic, not a cause claim. Fix the tracking, then re-check the 7-day window. The first-party telemetry guide covers the beacon that fills the Traffic block when GA4 has no rows, and the Search Console guide covers the click side.

Limits and non-goals

  • Page detail is a 7-day snapshot of the top 20 organic landing pages; conversions in the page join are always last 7 days. Pages outside the top 20 read na.
  • No full-funnel attribution: the console does not claim which click, answer or page caused revenue.
  • No ad attribution and no cross-device identity: visits are not joined to ad spend, campaigns or one person across devices.
  • No estimated traffic: only observed sessions and page views. A missing source reads na instead of a modelled total.
  • No AI advice: the console reports the gap and the checks behind it; it does not rewrite your tag or consent banner.

Plan and retention differences are on pricing; return to the console to bind the property.

Was this page helpful?