How to Set Up Conversion Events in Google Analytics 4

Traffic is only half the story. What actually matters is whether that traffic does something valuable — buys, signs up, submits a form, downloads a file. In GA4, those valuable actions are called conversions, and setting them up correctly is one of the first things you should do after installing tracking. Here's exactly how it works.

How Conversions Work in GA4

Unlike Universal Analytics, where "Goals" were a separate configuration layer bolted on top of your data, GA4 conversions are just regular events that you've flagged as important. Any event already flowing into your property — whether it's automatically collected, part of Enhanced Measurement, or something you built yourself — can be marked as a conversion with a single toggle.

Step 1: Decide What Counts as a Conversion

Before touching any settings, get specific about what actually matters to your business. Good conversion candidates usually include:

• A completed purchase (purchase)
• A submitted lead or contact form (generate_lead or a custom event)
• A newsletter signup (sign_up or a custom event)
• A completed account registration
• A high-intent action, like adding to cart or starting a trial

Avoid marking low-signal events (like page_view or scroll) as conversions — it dilutes the metric and makes your conversion rate meaningless.

Step 2: Mark an Existing Event as a Conversion

If the event you want is already being collected:

1. Go to Admin > Events.
2. Find the event in the list.
3. Toggle Mark as conversion next to it.

That's it — no code changes needed. Within a short delay, that event starts appearing in Admin > Conversions and in your standard reports as a tracked conversion.

Step 3: Create a Custom Event First (If It Doesn't Exist Yet)

If the action you care about isn't already being tracked as its own event, you'll need to send it. A typical implementation with gtag.js looks like this:

document.querySelector("#contact-form").addEventListener("submit", () => {
  gtag("event", "generate_lead", {
    form_id: "contact_page_footer",
    value: 25,
    currency: "USD",
  });
});

If you're using Google Tag Manager instead:

1. Create a trigger for the form submission (Form Submission trigger type, or a Custom Event trigger tied to a dataLayer.push).
2. Create a GA4 Event tag named generate_lead.
3. Add event parameters for form_id, value, and currency.
4. Publish the container, then test it in Preview mode before going live.

Once the event has fired at least once, it'll show up in Admin > Events, where you can mark it as a conversion just like any built-in event.

Step 4: Create a Conversion Directly (Without Waiting for the Event)

You can also pre-register a conversion event name before it's ever fired:

1. Go to Admin > Conversions.
2. Click New conversion event.
3. Type the exact event name you plan to send (e.g., start_trial).
4. Save it.

As soon as that event name starts appearing in your data, GA4 automatically counts it as a conversion — useful when you know a new feature is shipping soon and want the conversion tracking ready on day one.

Step 5: Assign Value to Conversions

For conversions tied to revenue or a meaningful dollar value, always pass a value and currency parameter:

gtag("event", "start_trial", {
  value: 49,
  currency: "USD",
  plan: "pro_monthly",
});

This unlocks conversion value reporting throughout GA4 and feeds accurate ROAS data back into Google Ads if the accounts are linked.

Step 6: Verify It's Working

Don't trust a conversion setup you haven't tested. Two ways to confirm:

• Trigger the event yourself and check Realtime > Conversions by Event name.
• Open Admin > DebugView, enable debug mode, and watch the exact parameters come through live.

gtag("config", "G-XXXXXXX", {
  debug_mode: true,
});

Common Mistakes When Setting Up Conversions

A few patterns show up repeatedly when teams get their GA4 conversions wrong:

• Marking too many events as conversions. If every button click and page view is a "conversion," the metric stops meaning anything. Keep the list short and tied to real business outcomes.
• Forgetting to pass value and currency. Without these, you lose access to conversion value reporting and any ROAS-based bidding in linked Google Ads accounts — even if the conversion count itself looks fine.
• Not testing before trusting the data. An event that looks correct in your code review can still fail silently in production — a typo in the event name, a tag that never fires on mobile, or a trigger condition that's slightly too narrow. Always confirm with DebugView or Realtime before treating a new conversion as reliable.
• Duplicating conversions across similar events. If both purchase and a custom order_complete event fire for the same transaction, you'll double-count conversions without realizing it until revenue numbers look implausibly high.
• Ignoring conversions after a redesign. A site redesign or checkout rebuild can silently break an existing conversion event if button IDs or form structures change. Re-verify conversion tracking as a required step in any redesign QA checklist, not an afterthought.

Reviewing Conversions Periodically

Conversion setups aren't "set and forget." Revisit your conversion list quarterly:

• Remove conversions tied to features or campaigns that no longer exist.
• Confirm values are still accurate if pricing has changed.
• Check that new key actions introduced by product changes have a corresponding conversion event.

A Note on Conversion Limits

GA4 properties have a maximum number of conversion events allowed (the exact cap has changed over time and differs by property edition, so check Admin > Conversions for your current limit). Be deliberate about what you mark — every property benefits from a short, meaningful list of conversions rather than a long list of everything that technically happened.

FAQ about How to Set Up Conversion Events in Google Analytics 4

Do I need code to create a GA4 conversion?

Only if the underlying event doesn't exist yet. If the event is already firing, you can mark it as a conversion with a toggle in Admin — no code required.

How long does it take for a new conversion to show up in reports?

Marking an event as a conversion is usually near-instant, but historical data won't be backfilled — GA4 only counts the event as a conversion going forward from when you mark it.

What's the difference between an event and a conversion in GA4?

Every conversion is an event, but not every event is a conversion. Marking an event as a conversion just flags it for conversion-specific reporting and Google Ads bidding.

Can I unmark a conversion later?

Yes, toggle it off in Admin > Events or delete it from Admin > Conversions at any time.

Should I mark "page_view" as a conversion?

Generally no — it's too broad to be a meaningful business outcome and will inflate your conversion rate without telling you anything useful.

How do conversion values affect Google Ads bidding?

If your GA4 property is linked to Google Ads, conversion values imported from GA4 can be used for value-based bidding strategies like Target ROAS.

Conclusion

Getting conversions right in Google Analytics is less about clicking the right toggle and more about deciding, upfront, what genuinely matters to your business. Nail that decision, verify your events with DebugView before trusting them, and your conversion reporting becomes a real decision-making tool instead of noise. For more implementation walkthroughs, check out my website.