Goal
In Universal Analytics, a Goal was a configured conversion target that tracked when users completed a desired action, replaced by conversion events in GA4.
In web analytics, Goal was the Universal Analytics term for a configured conversion target that tracked when users completed a specified action, replaced by conversion events when Google migrated to GA4.
What Goal Means in Marketing
The word “goal” in analytics has a specific technical meaning that traces back to Universal Analytics, where Goal was a configuration object: a named conversion target you set up in the admin panel, chosen from four types (destination, event, duration or pages per session), and applied to one or more views within your property.
Goals were the mechanism by which Universal Analytics translated user actions into conversion data. Without a configured Goal, form submissions, purchases and signups did not appear in your conversion reports. Setting up Goals was a foundational analytics task for any new property, and organisations that skipped it had no conversion data regardless of how much traffic they were getting.
With the move to GA4, the Goal concept was retired. GA4 uses conversion events instead, which are simply events you mark as important. The vocabulary shifted from “Goal completion” to “conversion” in GA4 reporting, but the underlying purpose is the same: identifying and counting the actions that matter to the business.
How Goal Configuration Works
Destination goals. The most common type. When a user reached a specific URL (typically a thank-you page after a form submission or a purchase confirmation page), a goal completion was recorded. The destination goal was reliable when your site had a dedicated confirmation page that users only reached by completing the intended action.
Event goals. An event goal fired when a specific Universal Analytics event (defined by category and action) was triggered. This was used for interactions that didn’t produce a page load: button clicks, form submissions handled via JavaScript, video completions, file downloads.
Duration and pages-per-session goals. These engagement-based goals measured session quality rather than task completion. A duration goal might fire if a user spent more than three minutes on the site. A pages-per-session goal might fire if they viewed more than five pages. These were less commonly used because they measured attention rather than intent, and were easily gamed by slow navigation or confused users clicking around.
Goal values. You could assign a fixed monetary value to each Goal in Universal Analytics. A lead submission goal might be assigned a value of £50 based on your average lead-to-revenue ratio. This allowed reports to show “goal value” as a proxy for revenue in non-ecommerce scenarios.
Views and Goal limits. Universal Analytics allowed up to 20 goals per view. Organisations with more than 20 conversion actions to track needed to prioritise, often lumping lower-priority conversions into a single event goal.
Goal Example
GA4’s conversion events are more flexible than Universal Analytics Goals. There’s no limit of 20. Conversions don’t need separate configuration beyond marking an event. The value is dynamic rather than fixed. But the shift also means that conversions in GA4 require events to be firing correctly, whereas destination goals in Universal Analytics worked off URL matching alone, without any event instrumentation.
Why Goal Tracking Matters for Marketers
Understanding the Goal concept matters because much of the analytics documentation, tutorial content and historical data you’ll encounter still references it. If you’re auditing an old analytics setup, migrating historical data, or onboarding someone who learned analytics before 2023, Goal is the vocabulary you’ll need. In GA4 terms, the thing to configure is conversion events, but knowing what Goals were and how they worked helps you map the old and new systems correctly.
Frequently Asked Questions
How were Goals set up in Universal Analytics?
Universal Analytics supported four goal types: destination (a user reached a specific URL, such as a thank-you page), duration (a session lasted longer than a set time), pages per session (a user viewed more than a set number of pages) and event (a specific event category and action combination was triggered). You configured up to 20 goals per view, gave each a name, and optionally assigned a monetary value. Goals then appeared in conversion reports across the platform.
What replaced Goals in GA4?
GA4 uses conversion events instead of Goals. Any event that fires in GA4 can be marked as a conversion in the admin settings. The mechanics are simpler than Universal Analytics Goals: there is no configuration wizard, no goal types, and no per-view limit of 20. You mark an event as a conversion and it appears in conversion reports. The trade-off is that more events need to be explicitly tracked, whereas Universal Analytics destination goals worked without any event setup.
Can GA4 Goals be set with monetary values like Universal Analytics?
Not exactly. Universal Analytics let you assign a fixed goal value to each Goal completion. GA4's conversion events pull value from the event's value parameter, which is set dynamically when the event fires rather than statically in admin. For ecommerce, this is more accurate because the purchase value varies by transaction. For lead generation goals where you want to assign a fixed estimated value, you set the value parameter in your tag or event configuration, not in the GA4 admin.
Want help with this for your brand? See my services.
Need help putting this concept into practice on your campaigns? Share your current targets and I will suggest the right approach.