An event is a single recorded interaction between a visitor and your website or app: loading a page, clicking a button, submitting a form, playing a video or making a purchase. In GA4 everything is an event, page views included, and each one has a name plus optional details called parameters.
How events work
A tag on the page sends a small message to the analytics or ad platform each time something worth recording happens. A GA4 event for a quote request might be named generate_lead and carry parameters such as form_name set to “boiler quote”. GA4 adds its own context automatically, including the page address, the device and the traffic source.
GA4 sorts events into four kinds:
- Automatically collected events Such as first_visit and session_start, sent by the Google tag with no setup.
- Enhanced measurement events Such as scroll and file_download, sent automatically once switched on in the data stream settings.
- Recommended events Such as generate_lead, sign_up and purchase, which Google has named and defined. You implement them yourself, but using Google’s names means GA4’s ready-made reports understand them.
- Custom events Which you name and define for anything the other three do not cover.
Any event can be marked as a key event, GA4’s term for an action that matters to the business, and key events can be imported into Google Ads as conversions.
The word turns up in neighbouring tools with slightly different meanings. Meta calls the actions reported by its Pixel and Conversions API events, with standard names such as Lead and Purchase. In Google Tag Manager, an event is a message pushed into the data layer that can set off tags; it reaches GA4 only if a tag sends it there.
Why it matters
Every GA4 report is built from events, so the quality of your events sets the ceiling on the quality of your reporting. A UK trades business that records phone taps, quote forms and WhatsApp clicks as separate, consistently named events can see which campaigns produce which kind of enquiry. One that records only page views can see traffic and nothing about whether it led anywhere.
Events also drive ad platform bidding. Google Ads and Meta both optimise towards the events you tell them matter, so a badly defined event, such as a lead that fires whenever a form is viewed, trains them to find more of the wrong people.
Common mistakes
- Inconsistent names. GA4 event names are case-sensitive, so Form_Submit, form_submit and formSubmit become three separate events. Use lower case with underscores and stick to it.
- Putting detail in the name. Events called click_header_phone and click_footer_phone multiply quickly. One event, phone_click, with a parameter for where the click happened, is far easier to report on.
- Tracking everything. Dozens of events nobody reads make the useful ones harder to find. Track the actions that answer a business question.
- Using reserved names such as session_start or first_visit for your own events, which GA4 does not accept.
- Sending personal data. Names, email addresses or phone numbers sent with events breach Google’s terms. They usually leak in through page addresses and form fields, so check both.
- Firing before consent. On a UK site, analytics events should be sent only once the visitor accepts analytics cookies, unless you have deliberately chosen a consent mode setup that sends cookieless pings.
How to act on it
- Write a short tracking plan: each event name, when it fires, its parameters and whether it is a key event. A spreadsheet is enough.
- Use Google’s recommended event names where one fits, and custom names only where none does.
- Open the Events list in GA4’s admin settings and compare it with the plan. Rename at source, or remove, anything that should not be there.
- Test every new event in DebugView before marking it as a key event.
A clean event plan is the foundation for the paid campaigns I manage in performance marketing, because every bidding decision downstream depends on it.