New format
What changed in Google Analytics 4: from sessions to events
Google Analytics 4 replaced Universal Analytics’ familiar logic: instead of hits and sessions as the main axis — events and parameters. Site and app can live in one data scheme.
Below: the essence of the shift and what to check in practice. UI and report names change; the measurement model matters more than widget layout from the 2020 beta. Ecommerce behavior in GA is a separate piece; goals/key events are in the conversions guide.
Main model shifts
One scheme for web and app: you can see the user path across surfaces if streams and identity are set correctly. Before, web and app often lived in different report universes.
Sessions are no longer the center of the universe. Analytics builds around events: what the user did, with which parameters, in which context. That’s more flexible for SPAs, video, clicks, and micro-conversions — and harder for people used only to bounce as in UA.
Enhanced measurements remove some routine: basic interactions can be turned on in stream settings. That doesn’t replace a thoughtful ecommerce and CRM scheme — it’s a start without dozens of tiny tags.
Before/after on one chart without caveats misleads: different session model, cookie consent, blockers, and sampling in explorations. Compare trends inside GA4 — not yesterday’s UA bounce with today’s engagement.
Reports, audiences, and migration practice
In the UI — engagement overviews, events, audiences, funnels, and Explorations. Pathing, cohorts, and realtime help, but tab names drift: learn the meaning (events, audience, funnel), don’t memorize a 2020 screenshot.
The audience builder replaces part of UA segments: conditions at event, session, and user level can combine (e.g. desktop + completed a purchase). Audiences also help in Google Ads if accounts are linked.
Funnels are built from event sequences; skipping a step usually drops the user from the chain — normal for an open funnel, but needs careful checkout-step tagging.
Migration practice: install GA4 in parallel with old tracking (if not yet), check DebugView/realtime, mark key events, set ecommerce or at least purchase, align consent mode/cookie policy. GTM makes tag upkeep easier.
Bottom line: GA4 isn’t a new UA skin — it’s another model. Master events and parameters — reports and explorations become a hypothesis tool, not a widget museum.
Checklist after creating a GA4 property:
- tag on all templates, no duplicate
- enhanced measurements as needed
- key events/conversions
- ecommerce or purchase equivalent
- check in realtime / DebugView
- internal traffic filter
FAQ
Does Universal Analytics still work?
As a foundation — no. Build tracking in GA4. Historical UA data won’t migrate one-to-one — plan parallel collection early.
What is the event model?
Almost everything is an event with parameters (page_view, scroll, purchase…). Sessions are counted differently; you can’t compare UA and GA4 figures directly.
Is Firebase required?
For apps, GA4 has historically been close to Firebase Analytics. Web can run without a separate “app world,” but cross-platform is a GA4 strength.
What are enhanced measurements?
Built-in collection of typical actions (views, scroll, outbound clicks, site search, and more) without hand-coding every click. Check the current help for the list and names.
Where did UA goals go?
In GA4 — key events (conversions) based on events. Full breakdown — in the goals/conversions setup article.
Still reading UA bounce next to GA4 engagement on one chart?
We’ll set the event model, key events, and DebugView so reports become a hypothesis tool — not a widget museum.
Discuss the task
