GA4 Goals vs Key Events: Understanding the Migration from Goals (2026)

What replaced Goals in GA4?

Universal Analytics used "Goals" — configurable conversion definitions (destination URL, time on site, pages per session, or event) that produced a "Goal completions" metric in reports. GA4 eliminated the Goals concept entirely and replaced it with Key Events — events marked as commercially significant in GA4 Admin (Admin → Events → toggle "Mark as key event").

The architectural shift: in GA4, everything is an event first. You configure what happens (an event fires) and then declare it significant (mark as key event). In UA, Goals were a separate configuration layer that counted specific conditions. The practical impact: GA4 Key Events are more flexible and more reliable than UA Goals — but they require proper event implementation, which UA's destination goal type didn't require (it just pattern-matched page URLs).

The four UA goal types and their GA4 equivalents

1. Destination goal → page_view event + parameter filter

UA: Goal fires when page URL matches /thank-you or similar.

GA4 equivalent: The page_view event fires automatically on every page. Mark it as a key event? No — page_view is not selectively markable. Instead:

Option A (recommended): Implement a custom goal_complete or form_submitted event that fires only on the thank-you page load. Mark this custom event as a key event.

Option B (simpler): Use GA4 Explorations to filter page_view events where page_location contains /thank-you — but this is an analysis approach, not a key event count.

Why Option A is better: A custom event on the thank-you page is specific, less susceptible to direct URL access, and can include parameters (form_id, conversion_value) that a destination goal couldn't capture.

2. Duration goal → engagement time condition

UA: Goal fires when session duration exceeds X seconds.

GA4 equivalent: No direct equivalent as a key event. In GA4, session engagement is measured via engagement_time_msec parameter. You cannot directly mark "sessions over 120 seconds" as a key event without a custom implementation.

Workaround: Create a custom event using GTM:

Practical reality: Duration-based goals were rarely useful for business decision-making. The GA4 equivalent (long_engagement custom event) is only worth implementing if session duration is a genuine business signal for your specific use case.

3. Pages/screens per session goal → no direct equivalent

UA: Goal fires when a user views ≥ N pages in a session.

GA4 equivalent: No native equivalent. GA4 doesn't count pages per session and fire an event when a threshold is crossed.

Workaround: Not straightforward. If pages-per-session was a proxy for engagement depth, use GA4's built-in engaged_session metric (2+ page views = engaged session) as a proxy. If you need a specific threshold (e.g., 5+ pages), implement a custom event counting pageviews and firing at the threshold.

4. Event goal → event marked as key event

UA: Event goal fires when a specific event category/action/label combination occurs.

GA4 equivalent: This is the native GA4 pattern. Implement the event with the correct name and parameters, then mark it as a key event in Admin → Events.

This is the simplest migration path. Any UA event goal becomes a GA4 event with a key event toggle.

The metric name change

Stakeholder communication tip: When presenting GA4 data to stakeholders used to UA Goals, use "key event rate" as the equivalent to "goal conversion rate" — the terminology update needs to be explicitly stated once, after which stakeholders adapt quickly.