An event is the basic record in modern analytics. It has a name (such as sign_up or file_download) and optional parameters that describe it (such as method or file_name). GA4 is built entirely on events: page views, sessions starting and purchases are all events. Product analytics tools use the same model, which makes events the common language for tracking plans.
Types of events in GA4
GA4 groups events into four kinds. Knowing which kind you need saves time, because Google recommends using its names where they fit so that reports can use them.
- Automatically collected: session_start, first_visit, user_engagement
- Enhanced measurement: scrolls, outbound clicks, site search, file downloads, form interactions, video engagement
- Recommended: names Google defines for common actions, such as sign_up, login, generate_lead, purchase
- Custom: events you name yourself for actions specific to your product
Events and parameters
Parameters add detail without creating new event names. A single cta_click event with a location parameter is easier to analyze than separate events for every button. To see a custom parameter in standard reports, register it as a custom dimension or metric.
gtag('event', 'generate_lead', {
form_id: 'demo_request',
plan_interest: 'enterprise'
});Designing a tracking plan
Write down each event, its trigger, its parameters and the question it answers before anyone builds it. Use consistent naming (GA4 event names are case sensitive), avoid personal data in parameters, and keep the list short enough that someone will actually maintain it.
Example
One event instead of twelve
Suppose Fernstack, a cloud cost tool, tracks twelve separate button-click events with names like hero_cta_click and footer_cta_click. Reporting is messy and two names have typos. Replacing them with one cta_click event and a cta_location parameter makes the report a single table and stops name drift.
Common mistakes
Putting personal data in parameters
Sending email addresses or names in event parameters breaks Google's policies and creates privacy risk. Use IDs you control instead.
Inventing names when a recommended one exists
Recommended event names unlock built-in reporting. Check Google's list before naming your own.
Questions
No. Only events you mark as key events are treated as conversions-style goals in GA4 reports.
