Table of contents

• How did goals change in GA4?
• What makes a well-defined goal?
• How do you count goal completions correctly?

How did goals change in GA4?

Universal Analytics offered four goal types, configured separately from events and capped at 20 per view.

GA4 removed the separate concept. Everything is an event, and flagging an event as a key event, called a conversion until Google renamed it in 2024, turns it into what a goal used to be. Three differences change how the numbers behave:

• Any event can be promoted, including one already collecting data, with no separate configuration object to build.
• Promotion is not retroactive. The flag counts from the moment it is set, so it has to be in place before the period you intend to report on.
• Counting changed, and it is now a setting. Universal Analytics counted a goal once per session. GA4 defaults to counting every firing, so a visitor who submits twice registers two. Each key event carries a counting method that can be switched to once per session, which is the closer match to the old behavior.

Left at the default, GA4 quietly reports higher numbers than Universal Analytics did for identical behavior, which matters when someone compares year over year across the migration.

What makes a well-defined goal?

Unambiguous. It fires on the outcome itself. Bind it to "submission succeeded" rather than to "clicked submit", since a click that fails validation produced nothing.

Reliable. It fires every time the outcome occurs and never when it does not. Test it by completing the flow yourself on the published site.

Valuable. It maps to something the business cares about. See macro conversion.

Stable. Its definition does not drift, since changing it splits the history.

The defect that costs the most is the first one. A goal bound to the click rather than to the successful outcome overstates completions by however many submissions fail validation, and nothing downstream will flag it.

How do you count goal completions correctly?

Three decisions change the number materially, beyond the counting method above.

Attribution window. How long after a visit a completion still counts, and which touchpoint receives credit. B2B buying cycles routinely run past the default window, which quietly hands the credit to the last touch.

Cross-device identity. Without a user identifier, a visitor researching on mobile and completing on desktop appears as two people, one of whom failed. Sending a hashed user ID after authentication collapses them back into one.

Where the event fires. A client-side event misses anyone blocking scripts. A completion recorded server side counts everyone who genuinely submitted, at the cost of a backend integration. The gap between the two numbers is the size of your measurement blind spot.

Why do Webflow goals report zero?

Webflow's form success message renders in place with no page load, so a destination goal never fires. Redirect to a dedicated confirmation URL in the form settings, which makes the goal trivial, or fire a key event when the success element becomes visible.

Then verify it end to end. Submit the form yourself on the published site, since custom code does not run in the Designer or in preview, and confirm the event lands in the GA4 realtime report. A goal nobody has completed by hand is an assumption.

Related terms

Macro conversion · Event tracking · Micro conversion · Conversion funnel · Landing page conversion rate

Service: Conversion Rate Optimization.

FAQ

Are goals and conversions the same thing in GA4?

Effectively. GA4 replaced goals with ordinary events flagged as valuable, called conversions at launch and renamed key events in 2024. Google Ads kept the word conversion, which is why both terms stay in circulation.

Why are my Webflow goal completions showing zero?

Almost always the in-place form success state, which produces no page load for a destination goal to detect. Redirect to a confirmation page or track the success element becoming visible.

How many goals should you configure?

Few enough that they still express priority. Every extra event flagged as valuable also feeds GA4's key event reporting and audience building, so an over-flagged property produces reports in which everything converts and nothing stands out.