Conversion tracking, goals and key events in GA4

GA4 does not automatically know that a form submission or a phone number click matters more than a scroll event. Every event is treated equally until a specific one is explicitly marked as a conversion in Admin. That marking step is where most GA4 setups quietly fall short.

Why this step is easy to miss

GA4’s enhanced measurement automatically tracks a handful of generic events — page views, scrolls, outbound link clicks — the moment tracking is installed. That can create the impression that “analytics is working” without anything further needed. But the specific action a business actually cares about — someone submitting the enquiry form, someone tapping the phone number — is not one of those automatic events by default. It has to be captured as its own event, through a form plugin, a Tag Manager trigger, or custom code. Then, separately, it needs to be marked as a conversion in GA4’s Admin → Events settings, before it appears meaningfully in conversion-focused reports.

The two separate steps, and why both are required

Step one: the event has to exist and fire correctly. A form submission needs a trigger. Most form-builder tools and website platforms have a way to fire a custom event on successful submission. A phone number link needs to be tracked either as an outbound-style click event, or a dedicated custom event when tapped. This can be verified using GA4’s DebugView, covered on GA4 basics for a non-analyst. Tap the phone number or submit a test enquiry, and watch the event appear in real time.

Step two: the event has to be marked as a conversion. In GA4 Admin → Events, any event already appearing in the list can be toggled as a conversion with a single switch. Only after this toggle is the event surfaced properly in conversion-focused reporting views and available to be used as a target in some advertising platform integrations.

What “Goals” meant before, and why it does not map directly

The older Universal Analytics had a distinct “Goals” configuration, separate from its event tracking, with specific goal types: destination, duration, pages per session, event-based. GA4 removed this as a separate system. Every conversion in GA4 is simply an event that has been marked as one, using the same underlying event data model that everything else in the tool uses. This is a genuinely simpler model in structure. But it means there is no direct one-click migration from an old Goals setup. Each conversion needs to be re-established as a correctly firing, correctly named event, in GA4’s own terms.

Assigning a value, and why it changes how conversions are prioritised

A conversion event in GA4 can optionally carry a value parameter: a number attached to the event. It is commonly used for ecommerce revenue, but a lead-generation site can equally use it to express relative worth between different enquiry types. A phone enquiry and a general contact-form submission are not necessarily worth the same to a business. Assigning a higher value to the event more likely to represent a genuine, ready-to-buy enquiry lets reporting reflect that difference, rather than treating every conversion as interchangeable. This is optional, and a business tracking a single enquiry type has no real need for it. But it becomes useful the moment more than one type of conversion is being tracked, and they are not equally valuable.

The attribution window, and why a late conversion can be missed

GA4 applies a lookback window — a default period, adjustable in Admin, over which it will credit a conversion back to an earlier session’s channel. This exists because a visitor frequently does not convert on their very first visit. Picture a visitor who found the site through organic search two weeks ago, and returns directly today to finally submit the enquiry. Within the configured window, that conversion should still be at least partially credited back to the organic search visit that started the journey. Too short a window undercounts genuinely multi-visit journeys. This is particularly relevant for a business whose purchase or engagement decision is not typically made in a single sitting. The broader context of attribution is covered on attribution, and why it is mostly wrong.

Common mistakes that quietly break conversion counting

Marking a page view as a conversion when the actual action is further down the funnel. Marking the contact page’s page_view event as a conversion counts everyone who merely viewed the form, not everyone who actually submitted it. That is a materially different, and much larger, number, and it overstates genuine enquiry volume.

Double-counting from a thank-you page reachable by direct URL. A conversion might be tracked by a visit to a thank-you page rather than the form submission event itself. If that page can be reached without submitting the form, refreshing it or a bot crawling it can register a conversion that never happened. This is covered in the design context on what to do with a thank-you page.

Marking too many events as conversions, diluting the ones that matter. GA4 allows any number of events to be marked as conversions. But a report listing a dozen conversion types, most of them low-value micro-interactions, makes it harder to see which of them are the genuine business outcome. Restraint in what gets marked is itself part of getting this right.

A short setup sequence

Step	Where	How to confirm it worked
Set up the form submission event	Form tool, Tag Manager, or custom code	Submit a test enquiry, watch it appear in DebugView
Set up the phone-click event	Tag Manager or custom code on the tel: link	Tap the number on a real device, watch it appear in DebugView
Mark both as conversions	Admin → Events	The event’s conversion toggle is switched on
Confirm in reporting	Reports → Engagement → Conversions	The conversion events appear with a non-zero count over a few days of real traffic

“Key events,” not just “conversions”: GA4’s current terminology for a conversion event and page view

Google renamed “conversion events” to key events inside the GA4 interface. So a newer screenshot, or a colleague using a recently updated account, may show “Mark as key event.” Older documentation — and most of this page — says “mark as a conversion” instead. Admin lets you set key event status on any existing event. The mechanism a key event and a conversion both describe is identical: an existing tracked event, toggled on, so it counts as a business outcome rather than routine activity. Older Google Analytics conversions reporting and current key events terminology both remain in active use side by side. Google Ads’ own interface still says “conversions,” so neither term has fully replaced the other yet.

Google Analytics, GTM, an event key, Create Event and the counting method behind a session’s conversion events

An event key like form_submit is the name GA4 stores internally. Set a clear, consistent event name in Google Tag Manager (often shortened to GTM) at the point a tag is created. That naming decision is what determines whether the action tracks consistently to the same key event later, or fragments into several near-duplicate ones. Admin also has a dedicated Create Event option, for building a derived event from parameters of an existing one, separate from marking something a key event. GA4’s counting method for a conversion rate is events-based, not session-based the way the old Goals system counted a session as either converting or not. A single session generating a lead through two different tracked actions can generate lead events twice in GA4’s model. That changes how a conversion rate should be read against an older Universal Analytics benchmark. Some metric definitions are worth checking directly in Admin, rather than assumed to carry over: the event value parameter, the event name itself, and which parameters are actually attached to each event. That is the same discipline that already applies to avoiding a page-view conversion when the real action is further down the funnel. It is covered above as the most common way to over-count and mismeasure genuine enquiry volume.

What to do next

If form submissions or phone clicks are not appearing as distinct, correctly named events in GA4 right now, that is the first gap to close. Everything else in this section assumes those events exist and are marked correctly. For the phone-tracking case specifically, call tracking for phone-first businesses goes further. Where this connects to a paid landing page specifically, landing page design covers building a page structured around a single, trackable action.