How events work in GA4
Older versions of Google Analytics recorded a pageview as one kind of hit and an interaction as another. GA4 dropped that distinction. Everything is an event: a page being viewed, a video starting, a file downloading, a form being sent, an order being placed. Each event carries a name and, usually, parameters that describe it — which page, which button, which value, which currency.
Events reach GA4 in three broad ways. Some are collected automatically as soon as the tag is on the site. Some are enhanced measurement events, switched on in the data stream settings, which watch for scrolls, outbound clicks, site searches and file downloads without any extra code. The rest you send deliberately, through Google Tag Manager or directly in the site’s code, and those are the ones that describe what actually matters to your business.
Why events matter
An event is the smallest unit of truth in the account. Every report, audience, funnel and export is built by counting and filtering events, so an action you never recorded simply does not exist in the data. No amount of clever analysis afterwards can recover it.
Events are also what advertising platforms consume. A key event is an ordinary event you have flagged as important, and conversions imported into Google Ads bidding depend on it. Sloppy event design upstream becomes unreliable bidding downstream, and the cost shows up as wasted spend rather than as a reporting complaint.
Common mistakes with GA4 events
Naming is the first. GA4 treats event names as literal text, so a click recorded under one name on desktop and a slightly different one on mobile becomes two unrelated rows that no report will reunite. Case, underscores and spelling all count.
The second is putting detail in the name instead of in parameters. Creating a separate event for every form on the site fills the property with near-duplicates, while one submission event carrying a parameter for which form it was stays tidy and stays reportable. The third is measuring pages instead of decisions. A thank-you page view fires whenever that page loads, including on a refresh or a bookmark, and is a weaker signal than the confirmation the form itself produced.
How to act on it
Write the list before building anything. Decide which actions represent value, agree one name and one set of parameters for each, and keep that document somewhere whoever edits the site can find it. Then implement, and check every event in DebugView and the realtime report before anyone reports on it.
Register any parameter you want to break data down by as a custom dimension or metric, because unregistered parameters are collected but stay invisible in standard reports. Revisit the list whenever the site changes: a redesigned checkout or a new booking flow will quietly break events nobody thought to re-test. A sound GA4 setup starts from that list of actions rather than from the tag.
