Skip to content
Lunor Medya

22 Sep 2026 · 4 min read · Lunor Medya · Updated 20 Nov 2026

Measuring with Google Analytics 4: the event model and core concepts

Events, parameters, key events, engaged sessions, source dimensions and consent mode: the concepts you need to read GA4 reports correctly, in plain language.

Google Analytics 4 event model and report concepts

Many people open Google Analytics 4 (GA4) looking for familiar numbers and cannot find them: bounce rate is not what it used to be, there are no “goals”, and session counts do not match the old tool. That is because GA4 collects data with a different logic. This article does not cover setup steps; it explains the concepts you need to read the reports correctly.

Everything is an event

In GA4 the basic unit of measurement is the event. A page view, a scroll, a file download, a form submission, a purchase: each is an event. Events fall into four groups:

  • Automatically collected events: such as first visit and session start, which come with the installation.
  • Enhanced measurement events: switchable in settings, covering page views, scrolls, outbound clicks, site search, video engagement, file downloads and form interactions.
  • Recommended events: events whose names and parameters Google defines, such as generate_lead, add_to_cart and purchase. Using these names lets related reports fill in automatically.
  • Custom events: business-specific actions the others do not cover.

Parameters and user properties

Each event carries parameters that describe it: the form name for a submission, the value and currency for a purchase. User properties are persistent facts about the person, such as member or guest. To use a parameter as a breakdown in reports, you must register it as a custom dimension or metric in the GA4 interface.

Key events

Events that matter to the business are marked as key events. GA4 used to call these “conversions”. Quote form submissions, phone clicks and purchases are typical key events. Marking everything as a key event makes the report meaningless; choose only those close to a business outcome. Conversions used for bidding in Google Ads are defined on the Google Ads side or imported from GA4.

Sessions, engagement and bounce

In GA4 an engaged session is one that lasts longer than 10 seconds, includes a key event, or has at least two page views. Engagement rate is the share of sessions that were engaged. Bounce rate is now the inverse of engagement rate, i.e. the share of sessions that were not engaged, so it cannot be compared directly with the old tool’s bounce rate.

Users and source dimensions

By default GA4 identifies users through a browser identifier, a user ID if you send one, and Google signals. Dimensions that show where traffic came from work at two levels:

  • First user source: the channel through which the person first found your site, used in user acquisition reports.
  • Session source: the channel a particular visit came from, used in the traffic acquisition report.

The same person may arrive first via organic search and return later through an ad, so the two reports paint different pictures. Knowing which one you are looking at prevents misreadings.

Attribution

The attribution model decides which channel gets credit for a key event. GA4’s default is data-driven, distributing credit across touchpoints based on historical data; last click can also be selected. Changing the model changes the split across channels, while the total number of key events stays the same.

Consent mode and data gaps

When visitors do not consent to cookies, measurement is limited. Google’s consent mode passes consent status to the tags; without consent, tags can send limited cookieless signals, and GA4 can model the missing part when certain conditions are met. Report figures are therefore “observed plus modelled”, not an exact count. Processing personal data is also subject to regulations such as Turkey’s KVKK, so the cookie policy and consent text should be prepared with legal advice.

Data retention and thresholds

In standard GA4 properties, the retention period for user-level data is set in the admin settings (2 or 14 months). It affects explorations rather than standard reports, so it makes sense to choose the longer period from the start. Some reports apply data thresholds to prevent identifying individuals, which can hide small numbers.

To put these concepts into practice, follow our GA4 setup and audit checklist. To see how measurement feeds advertising and SEO decisions, read which digital marketing metric should decide, and for measurement and analysis support, see the SEO and digital marketing consulting package.