Goal vs Event
Conversion & UXAlso: Goals vs Events · GA4 Goal vs Event
Quick definition
A goal is the old Universal Analytics term for a tracked outcome like a purchase or a form submission. An event is the GA4 (Google Analytics 4) term for any recorded user action, from a page view to a button click. In GA4 you no longer set goals, you mark specific events as conversions instead.
How it varies across Australia
Most Australian GA4 accounts we review carry over messy conversion definitions inherited from old Universal Analytics goals, with far more events marked as conversions than genuinely represent business value. The shape is consistent across industries. Too many conversions, not too few.
See data and tracking maturity across Australian industries →Three layers, one confusion
Any recorded user action, from a page view to a completed purchase.
GA4 termAn event you've deliberately flagged as meaningful to the business.
GA4 termUniversal Analytics' word for a tracked outcome, replaced by conversions in GA4.
Retired 2023What it actually means
Analytics terminology has a habit of outliving the systems that invented it. Goal is a hangover from Universal Analytics, the older version of Google Analytics that Google retired in 2023. In that system you configured a goal, a destination page, a duration, an event, and Analytics counted every session that matched it.
GA4 dropped goals entirely. Everything a user does on your site or app is logged as an event, whether that's a page view, a scroll, a form submission or a purchase. There's no separate goal object anymore. Instead, you pick which events matter and flag them as conversions.
The distinction trips people up because the underlying idea hasn't changed, only the vocabulary. What used to be 'set a goal for form submissions' is now 'mark the form_submit event as a conversion'. Same intent, different plumbing.
The bigger risk is treating every event as equally important. GA4 will let you mark a scroll-depth event as a conversion sitting right next to a purchase event, and your conversion rate becomes meaningless the moment low-value events get counted alongside high-value ones. Attribution, CPA and any KPI built on top of conversions inherit that mess.
A goal was a setting. An event marked as a conversion is a decision, and most teams never actually make it.
How it shows up
This shows up the moment someone opens GA4's Admin panel and finds the Events list sitting next to a separate Conversions list. Every event you've ever fired appears in the first list. Flip a toggle and it appears in the second. It also shows up in confused Slack messages asking why conversions spiked overnight, which usually traces back to someone marking a new event, like a video play, as a conversion without telling the team.
Where people get this wrong
Related terms
Common questions
Do goals still exist in GA4?
No. GA4 removed goals entirely and replaced them with events marked as conversions. If you migrated from Universal Analytics, your old goals need to be manually recreated as GA4 conversion events.
How many conversions should I track in GA4?
As few as genuinely represent business value. Most sites need somewhere between two and five, not the dozen or so that GA4 will let you mark without complaint.
What happens if I mark too many events as conversions?
Your reported conversion rate becomes less meaningful because it now includes low-intent actions. Every metric built on top of conversions, including CPA and ROAS, inherits the distortion.
Can I still use the word goal when talking about GA4?
Informally, yes. Just be clear you mean a conversion event, not a configured Goal object, because that object no longer exists in the platform.
Debrief
Get the next one
No spam. No fluff. Just the next article, straight to your inbox.
Keep exploring
About New Rebellion
New Rebellion is a marketing intelligence consultancy. We build tools, score Australian businesses on how their marketing actually performs, and publish Debrief every day. This dictionary is part of how we work in the open.
How we think →