A ledger of AI tools and building sites for overseas traffic.

Home / Workflows & MCP / GA4's data model: why events matter more than pages

GA4's data model: why events matter more than pages

GA4 replaced pageviews with events plus parameters. Without learning that language, your reports will never reconcile.

Oct 18, 2026 3 min read naket.top Updated 2026-10-24
GA4's data model: why events matter more than pages

After migrating from UA to GA4, the most common confusion is "the same number never matches anywhere else". The reason is that the data model changed: everything revolves around events.

Basic structure

LayerMeaningExample
EventWhat happenedpage_view, scroll, click
ParameterExtra information attached to the eventpage_location, link_url
User propertyInformation about the persondevice, region, first source
SessionThe container for one visitends after 30 minutes of inactivity

UA had two axes, "session + page"; GA4 has one axis, "event", and a page is just a parameter of an event. So in GA4, "views of a certain page" is really "the number of page_view events where page_location equals that page".

Three places things tend not to match

  1. Sessions are not users: one user can have multiple sessions
  2. Engaged sessions: only counts as "engaged" if it lasts over 10 seconds / has a conversion / includes two or more pages — this is a new concept
  3. Sampling and thresholds: under heavy traffic reports are sampled, under light traffic thresholds are applied, and neither shows an exact value

The minimal set of self-defined events

A content site really only needs to watch four:

  • page_view (default)
  • scroll to 90% (default enhanced measurement)
  • outbound_click (outbound link clicks)
  • file_download (if applicable)

Add one custom event that marks "read to the end of the article" — it is more accurate than any time-on-page metric.

How to set up reports

  • Acquisition: look at source and landing page
  • Engagement: look at event counts, not just visits
  • Retention: new users vs returning users
  • Explorations: free-form reports, pull dimensions as needed

Explorations are the most useful, because the dimension combinations in standard reports are fixed, while your questions usually need a custom combination.

One caveat

GA4's realtime report and standard reports don't use the same definitions — don't check standard report numbers against realtime numbers. Use standard reports for trends, realtime for debugging a single hit.

Design principles for events and parameters

  • Event names describe "what was done": subscribe_click, report_download, not event1.
  • Parameters describe "the context": plan, source, article_slug, at most 3–5; more than that and nobody looks at them.
  • Don't rename events that are already live: renaming breaks historical data — add a new event to replace the old one.

GA4 custom dimensions must be registered in advance; unregistered parameters are only visible in Explorations and cannot be used for audiences. This is the step most easily missed.

A real lesson

Using page_location as a business parameter pollutes the page dimension in the default reports. To distinguish page types, use a separate page_type parameter.

In one sentence

GA4's data model can be summed up as "the event is everything". Translate business actions into events and parameters and the reports follow naturally; if you instead start from the reports you want and bolt on events afterwards, you will never fill the gaps.

GA4eventsreporting

Further reading

GA4 event documentation ↗ GA4 dimensions and metrics ↗