Every website has a reason it exists. For a service business, that reason is a contact form submission or a booked call. For an e-commerce store, it is a purchase. For a SaaS product, it is a trial signup. For a content creator, it is an email subscription.
Conversion events are the specific moments when a visitor acts on that reason. They are what connect website traffic to business outcomes in GA4, and GA4 does not configure them for you. Until you tell GA4 which actions count, your analytics will record how many people visited, how long they stayed, and which pages they viewed. It will not record whether any of that activity produced something your business can use.
What a conversion event actually is
The term sounds technical because of how GA4 uses it. The concept is straightforward. A conversion is the thing you built your website to get people to do.
What counts as a conversion varies by business. A service business needs contact form submissions and phone calls. An e-commerce store needs purchases. A SaaS product needs trial signups. A content creator needs email subscribers. The action differs across business models, and the principle holds in all of them: you are counting the specific moment a visitor does the thing your website exists to produce.
A pageview tells GA4 that a URL loaded. A conversion event tells GA4 that a person took action. You can have ten thousand pageviews and zero recorded conversions, and your GA4 reports will look like everything is working. Traffic numbers climb. Session duration holds steady. Engagement rate stays in range. The only thing absent from that picture is whether any visitor actually did what you needed them to do.
That gap stays invisible unless you know to look for it.
What happens when conversion tracking is missing
The pattern across businesses without conversion tracking produces the same category of mistakes.
A business doubles down on the channel with the highest session volume, without knowing that channel converts at a fraction of the rate of a smaller one getting less budget. Another business concludes a landing page is performing because traffic is steady, while its conversion rate sits below the site average. A third kills a campaign because traffic numbers look small, without seeing that those visitors were converting at the highest rate on the site.
Each of those decisions followed from the data that was available. The data that was absent changed the conclusion entirely.
When conversion data is missing, traffic is the only signal a business can act on. Budgets flow toward whichever channel shows the highest session count. Pages get evaluated by how many visitors they attract, with no way to distinguish pages that produce outcomes from pages that absorb traffic and return nothing. The question "is our marketing working?" turns into a guess, because the number that would answer it does not exist in the reports.
If you are not sure whether your current setup is missing conversions, the Growth Leak Diagnostic identifies the most common places tracking breaks without anyone noticing.
What conversion events give you
Conversion tracking gives everything else in your dashboard a denominator.
Traffic volume gains meaning when you can calculate what percentage of visitors converts. Channel data becomes actionable when you can compare conversion rates across sources. Cost per acquisition, return on ad spend, and funnel analysis all require conversion data to produce a number. Those calculations are the basic math that tells you whether your marketing spend is producing results, and every one of them depends on GA4 knowing what a conversion is and recording each time it happens.
Your north star metric, the single number that tells you whether the business is moving forward or falling behind, almost always involves a conversion event. The North Star Dashboard Guide walks through how to identify that metric for twenty-five different business types and build a weekly review around it.
How to set up conversion events in GA4
GA4 does not arrive knowing which actions your business cares about. You tell it by marking specific events as "key events," which is GA4's current label for what most people still call conversions. (More on the terminology below.)
The setup starts at Admin > Events. You will see a list of events GA4 is already recording. Some of those arrived automatically when GA4 was installed, like page views and scroll tracking. The event that represents your primary business action, the form submission, the purchase, the booking, may or may not be in that list already.
If the event exists and is marked as a key event, you are set. GA4 is counting it and the data is flowing into your reports.
If the event exists but is not marked as a key event, toggle on "Mark as key event" next to it. That takes about ten seconds. It is the difference between GA4 recording the action in the background and actually surfacing it as a conversion in your reports.
If the event does not exist at all, GA4 was never told to watch for that action. This is the most common situation, and it does not mean anything is broken. It means the configuration step was skipped, usually because nothing during GA4's installation process indicated it was necessary.
What you do next depends on what your conversion action is.
Purchases from a connected e-commerce platform (Shopify, WooCommerce, BigCommerce) usually send event data to GA4 automatically if the integration is enabled. Check the Events list for an event called "purchase." If it exists, mark it as a key event. If it does not exist, check your platform's GA4 integration settings.
Form submissions are not tracked automatically by GA4. GA4 sees the page view before and after the form, but it does not record the submission itself. The most common way to track form submissions is through Google Tag Manager: you create a trigger that fires when someone submits the form, send that trigger to GA4 as a custom event with a clear name like "contact_form_submit," and then mark the event as a key event in GA4.
Button clicks and link clicks work the same way. You set up a click trigger in Google Tag Manager, configure it to fire when someone clicks the specific element that represents your conversion action, and send that event to GA4.
Thank-you page visits are the simplest conversion to track. If your conversion action results in a visitor landing on a specific URL (a thank-you page after checkout, a confirmation page after signup), you can create a custom event in GA4 directly. Go to Admin > Events > Create Event, set the condition to fire when the page location contains your thank-you page URL, and name the event something clear. Then mark it as a key event.
If the technical setup is beyond your comfort level, write down this sentence and send it to your developer: "I need to track when someone [your conversion action] as a key event in Google Analytics 4. The event should be called [your event name]." That is a standard request and should take less than an hour to implement.
GA4 key events vs conversion events vs Universal Analytics Goals
GA4's terminology around conversions has shifted twice in recent years, which has created real confusion.
Universal Analytics Goals: If you used the previous version of Google Analytics before GA4, you tracked conversions through "Goals." GA4 replaced Goals entirely with events and key events. The concept is the same, you are telling the platform which actions count, but Goals from Universal Analytics did not carry over to GA4 automatically. Many businesses that migrated to GA4 lost their conversion tracking in the transition without realizing it.
Key events vs conversions: In 2024, Google renamed "conversions" to "key events" inside GA4 for properties connected to Google Ads. The word "conversions" was reserved for actions imported into Google Ads. By now, most GA4 properties show "key events" where "conversions" used to appear. The setup process is identical. The label changed. If you see "key events" in your GA4 menus, that is the current name for the same concept.
Throughout this post and across The Decision Loop, the terms "conversion event" and "key event" refer to the same thing. "Conversion event" is clearer for most business owners. "Key event" is what you will see inside GA4.
How to verify your conversion events are working
Configuring a conversion event and confirming it fires are two separate steps. The second step is the one most people skip, and it is the reason a significant portion of all conversion tracking is broken.
GA4's Realtime report exists for exactly this purpose. After setup, open Realtime in one browser tab. In a separate incognito window, go to your website and complete the conversion action yourself. Submit the form. Click the button. Make the purchase. Whatever your conversion is, do it.
Go back to GA4's Realtime report and look at the "Event count by Event name" section. Your conversion event should appear within thirty seconds. If it does, the event is firing and the setup is working.
If it does not appear, something in the configuration is broken. The most common causes: the event name in Google Tag Manager does not match the event name in GA4, the trigger condition is too narrow and is not firing when you expect it to, or there is a sync delay between Tag Manager and GA4 that resolves after a few minutes.
A broken setup is more damaging than no setup at all, because broken tracking produces false confidence. You make decisions from conversion numbers that do not reflect what is actually happening on your site. You trust data that is wrong. Testing the event after configuration is what separates analytics you can rely on from analytics that look convincing until they mislead you.
How many conversion events does my website need?
Most websites need one primary conversion event and one or two secondary ones.
The primary conversion event is the action most directly connected to revenue: a purchase, a form submission, a booking, a trial signup. This is the number that tells you whether your website is doing its job.
Secondary conversion events track meaningful steps toward the primary action. An email signup is a secondary conversion for a business whose primary conversion is a purchase. A pricing page visit is a secondary conversion for a SaaS product whose primary conversion is a trial start. These events give you visibility into the pipeline before the final action occurs.
The mistake most businesses make is marking too many events as conversions. When fifteen events are all flagged as key events in GA4, the conversion data loses its signal. Everything looks like it is converting. Nothing stands out. GA4 surfaces conversion counts prominently in standard reports, so a long list of low-value key events will distort every report that references conversions by count.
A practical ceiling is five conversion events total: one primary and up to four secondary. If you find yourself wanting to mark more than that, leave the additional events as standard events in GA4 and review them in the Events report. Do not elevate them to key event status. The constraint keeps your conversion data clean enough to act on.
What to do after your conversion events are configured
Two things are worth setting up immediately.
A weekly dashboard. Your conversion count and conversion rate belong in a weekly review alongside your traffic volume, traffic quality, and a measure of revenue or value per conversion. The North Star Dashboard Guide covers how to build that structure for twenty-five different business types and identify which single metric should anchor your weekly check.
An alert. GA4 can monitor your conversion rate against its own baseline and notify you when the rate drops below normal. That alert catches problems your traffic numbers will never show: a page redesign that broke the form, a pricing change that reduced purchase completions, a new traffic source that sends visitors who browse and leave. The GA4 Early Warning System is a free guide that walks through three alert builds, including the conversion rate alert, in about fifteen minutes.