---
type: "Artykuł"
title: "How do you set up a conversion in Google Analytics 4 (GA4)?"
description: "In GA4, conversions are now called key events. How to set them up for a store and a form, check that they work and import them into Google Ads."
resource: "https://webmountain.pl/en/analytics/ga4-conversions/"
tags: ["Analytics and tracking"]
author: "Michał Wojciechowski"
published: 2026-11-20
timestamp: 2026-11-20
---

# How do you set up a conversion in Google Analytics 4 (GA4)?

> You set up a conversion in GA4 by marking an event as a key event: Admin → Data display → Events and the "Mark as key event" toggle. Since March 2024 that is what GA4 calls conversions. When the event doesn't exist yet, for example for a form, you have to create it first.

Below: step-by-step setup for a store and for a form, the counting method, how to check that the conversion works, the most common mistakes and importing conversions from GA4 into Google Ads. Accurate as of October 2026.

## A conversion in GA4 is now called a „key event”

A conversion in GA4 is an event that matters to the business, for example a purchase (`purchase`), a submitted form (`generate_lead`) or a newsletter signup. Since March 2024, Google Analytics 4 calls these events **key events**. The word „conversion” stayed in Google Ads.

In practice this means one thing: if you look for a „Mark as conversion” button in GA4, you won’t find it. There is a „Mark as key event” toggle instead. How an event differs from the result you want to measure is something I explain in the article [what an event is in web analytics](https://webmountain.pl/en/analytics/what-is-an-event/).

## Before you set up a conversion in GA4: what has to work already

- **The GA4 tag on the site.** The site sends data to a GA4 property with a measurement ID `G-XXXXXXX`, pasted into the code or added through Google Tag Manager.
- **Editor access** to the GA4 property. With read-only access you can’t mark events.
- **The event you want to count.** A store on WooCommerce, Shopify or PrestaShop usually sends `purchase` through a plugin or an integration. A contact form often sends nothing, and you have to set that up first.

## How to set up a conversion in GA4 from an existing event

When the event already reaches GA4, for example `purchase` in a store, it takes 3 steps:

1. Go to **Admin** → **Data display** → **Events**.
2. Find the event on the list, for example `purchase`.
3. Turn on the **Mark as key event** toggle.

From that moment GA4 counts the event as a conversion. Old reports don’t get fixed: data from the days before you marked it stays as it was.

## How to set up a conversion in GA4 for a thank-you page

When a form doesn’t send its own event but shows a thank-you page after submission, for example `/thank-you/`, you can build an event from views of that page:

1. Go to **Admin** → **Data display** → **Events** and click **Create event**.
2. Give it a plain name, for example `form_submitted`.
3. Add two conditions: `event_name` equals `page_view` and `page_location` contains `/thank-you/`.
4. Save. The new event shows up in GA4 the first time someone lands on the thank-you page.
5. Mark it as a key event, as in the section above.

This method has one weak spot. People can refresh the thank-you page or open it from a bookmark, and then the conversion counts a second time even though nobody sent the form. An event sent by the form itself, or by Google Tag Manager after a successful submission, is more reliable.

## How to count a conversion in GA4: once per event or once per session

For every key event GA4 lets you choose the counting method:

- **Once per event**: every occurrence is a separate conversion. This fits purchases, because a customer can buy twice in one visit.
- **Once per session**: several occurrences in one visit count as one conversion. This fits forms and inquiries, where the same person’s second form is not a second customer.

## How to check that a conversion in GA4 works

1. **The Realtime report**: make a test purchase or send the form and check that the event appears within a few minutes.
2. **DebugView** (Admin → Data display → DebugView): shows events from your own browser while preview mode is on in Google Tag Manager or Tag Assistant.
3. **Standard reports**: key events show up there with a delay, usually up to 24–48 hours. No data the next morning doesn’t mean anything is broken yet.

## The most common GA4 conversion mistakes

**A conversion on the „Place order” click.** This is one of the most common problems I see in store accounts. A click before the payment gateway looks like a purchase, but some customers never pay. Google Ads campaigns then learn from intent, not from sales. The conversion should be `purchase` after a successful payment.

**The purchase never reaches GA4 at all.** In WooCommerce it happens that GTM doesn’t see the purchase, because the page after payment doesn’t send the order data. I describe the causes and fixes in the article on [a missing purchase event in WooCommerce and Google Tag Manager](https://webmountain.pl/en/analytics/missing-purchase-event-woocommerce-gtm/).

**A purchase credited to your own site or to the payment gateway.** When a customer moves to a second domain, for example a booking system, GA4 loses the source of the visit. In reports the purchase then has a `referral` source from your own site instead of Google Ads. I show how to fix it in the article on [GA4 conversions across two domains](https://webmountain.pl/en/analytics/ga4-cross-domain-conversions/).

**The same sale counted twice in Google Ads.** This happens when the account has a separate Google Ads conversion tag and also imports the purchase from GA4, with both conversions set as primary. Google Ads then counts one order twice, and the campaign looks better than it performs. One of them should be primary, the other secondary.

## How to import a conversion from GA4 into Google Ads

1. Link GA4 with Google Ads: in GA4 go to **Admin** → **Product links** → **Google Ads links**.
2. In Google Ads go to **Goals** → **Conversions** → **Summary** and click **Create conversion action**.
3. Choose **Import** → **Google Analytics 4 properties** → **Web** and select your key event.
4. Decide whether the conversion should be primary (campaigns learn from it) or secondary (reporting only).

Once conversions are counting, the same events can be used to build [a GA4 audience and use it in Google Ads](https://webmountain.pl/en/analytics/ga4-audiences-google-ads/).

Accurate as of October 2026. Google often renames buttons in GA4 and Google Ads, so the path in your account may look slightly different.

## When to hand GA4 conversion setup to a specialist

Marking the event takes a minute. Checking that the event counts the right thing takes longer: a purchase after payment, with its value, counted once and with the right source. If the numbers in GA4, Google Ads and your store don’t match, it’s worth having someone walk through the measurement from start to finish. That is what [analytics and tracking setup](https://webmountain.pl/en/analytics-and-tracking/) looks like.

## Frequently asked questions

### Where are conversions in GA4?

Since March 2024, conversions in GA4 are called key events. You'll find them under Admin → Data display → Key events, and in reports as the "Key events" column.

### How many conversions can you set up in GA4?

A standard GA4 property lets you mark up to 30 key events. In practice a few are enough: purchase, submitted form, phone call or newsletter signup.

### Why doesn't a GA4 conversion show up in reports?

Most often because of the delay: GA4 standard reports usually show data after 24–48 hours. If the event doesn't appear in the Realtime report either after a test purchase or form, the problem is in the tag, or the event isn't being sent at all.

### Is a GA4 conversion the same as a Google Ads conversion?

Not always. A key event is an important event in GA4. It becomes a Google Ads conversion only after you import it into Google Ads, or when a separate Google Ads conversion tag counts it.
