Google Analytics 4: what happens after the click

The event model, in one section

The single thing worth understanding before you open GA4 is that it records events, not sessions. Universal Analytics organised everything around pageviews grouped into visits; GA4 records each interaction as an event with parameters attached (page_view, scroll, click, file_download, form_submit) and builds the reports on top of that stream.

This is why familiar metrics moved or vanished. Bounce rate is gone, replaced by engagement rate, which counts the opposite: the share of sessions that lasted, scrolled or converted. Once you accept that everything is an event, the interface stops feeling arbitrary and starts feeling merely verbose.

Set these three things up on day one

1. Data retention to 14 months. Admin → Data settings → Data retention. It does not apply retroactively, so every day on the default is a day lost.
2. Link Search Console. Admin → Product links. Query data and behaviour data in one place.
3. Define one key event. A form submit, a booking, an outbound affiliate click. Without it, GA4 reports activity but never outcomes.

Those three take fifteen minutes and are the difference between a property that answers questions in a year and one that just accumulated numbers.

Why GA4 and Search Console will never agree

This confuses everyone at least once, so here is the mechanism. Search Console counts a click when someone clicks your result in Google, recorded on Google's side. GA4 counts a session when its tag fires successfully in the visitor's browser. Between those two moments a great deal can intervene.

• Ad blockers and privacy browsers prevent the tag from loading at all.
• Consent refusals stop measurement where a cookie banner requires opt-in.
• Fast exits can leave before the tag fires.
• Attribution differs: GA4 may class a returning visitor as direct where Search Console counted an organic click.

The practical rule: use Search Console for anything about the search results, and GA4 for anything about behaviour on the site. Do not attempt to reconcile the totals, and be sceptical of any report that presents GA4 sessions as an exact visitor count.

What to actually do with the data

The most useful habit is comparing landing pages by engagement rather than by traffic. A page bringing 800 visits with poor engagement time and no conversions is worth less than one bringing 80 that convert. And the traffic report alone will tell you the opposite. Sorting by engagement, then by key events, repeatedly surfaces the pages worth improving.

The second habit is checking channel mix monthly. If organic is flat while direct climbs, something is changing in how people find you: often brand awareness, sometimes attribution drift. Either way, that is a question worth asking early rather than noticing a year later.

Is GA4 worth the learning curve?

For most site owners, yes. But with a realistic scope. You do not need to master GA4. You need five reports, one conversion definition and a monthly habit. That is perhaps two hours of learning, and it is enough to answer the questions that actually change decisions.

If GA4 genuinely does not fit how you think, privacy-first alternatives exist and are simpler. But they cost money, they still get blocked, and they do not link to Search Console. For a free tool that answers the post-click half of the question, GA4 remains the default, awkwardness included.