
How-to · Published October 18, 2026
How to set up events in Google Analytics 4
A practical GA4 event setup primer — enhanced measurement, custom events, key events (conversions), and common pitfalls — without dumping full vendor docs.
Updated
Quick answer
Quick answer
In GA4, start with enhanced measurement for automatic pageviews/scrolls, then add custom events only for decisions you care about. Mark critical ones as key events (conversions). Prefer a short, named taxonomy over dozens of noisy tags.
Start with enhanced measurement
After the GA4 tag is installed, turn on enhanced measurement for the basics (pageviews, outbound clicks, site search when configured). That covers many marketing sites without custom code.
Only add custom events when a dashboard or experiment depends on them — signup submit, pricing CTA, download, purchase.
Custom events that stay useful
Use stable names (signup_completed, not btn_click_hero_2). Attach a few parameters (plan, location, value) — not twenty.
Send events via gtag, GTM, or your framework’s analytics helper. QA in DebugView before you trust reports.
Mark conversions as key events
In GA4, mark the events that define success as key events. That powers conversion reporting and ads optimization when you link Google Ads.
If you do not run ads, you still want key events for cleaner exploration reports — just fewer of them.
Common pitfalls
- Duplicate tags (GTM + hard-coded gtag) double-counting
- Consent mode misconfiguration changing event volume overnight
- Autocapture-style GTM clutter with no owners
- Comparing GA4 counts to Plausible pageviews as if they were the same metric
For when GA4 is overkill, read GA4 vs Plausible. For product depth, see GA4 vs PostHog.