---
type: "Artykuł"
title: "GA4 conversions across two domains: how to set them up correctly"
description: "How to set up cross-domain measurement in GA4 so conversions stop landing in self-referral: 3 steps, checking the _gl parameter and Google Ads import."
resource: "https://webmountain.pl/en/analytics/ga4-cross-domain-conversions/"
tags: ["Analytics and tracking"]
author: "Michał Wojciechowski"
published: 2026-11-20
timestamp: 2026-11-20
---

# GA4 conversions across two domains: how to set them up correctly

> Conversions in Google Analytics 4 count correctly across two domains only when GA4 recognizes the same customer on both sites. That is what cross-domain measurement is for.

You set it up in 3 steps in the GA4 interface and check it in a few minutes. Below: step-by-step setup, testing, the most common mistakes and importing conversions into Google Ads. Accurate as of October 2026.

## Why GA4 loses conversions when a customer moves to a second domain

GA4 recognizes a customer by the `_ga` cookie. That cookie belongs to one domain, and the second domain can’t see it. When a customer moves, for example, from the website `company.com` to the store `company-shop.com`, the store doesn’t know it’s the same person. GA4 gives them a new ID and starts a new session.

It’s like a store where the customer walks from the fitting room to the checkout, and the cashier greets them as if they had just come in off the street.

The effects show up in reports:

- **The conversion has the wrong source.** The purchase is credited to `company.com / referral` instead of Google Ads or organic search. This is called self-referral: the site refers traffic to itself.
- **One customer counts as two,** so the number of users goes up and the conversion rate goes down.
- **The path breaks off.** Reports don’t show what the customer did before moving to the second domain.
- **The conversion may never reach the campaign.** Google Ads doesn’t learn that the purchase followed an ad click, so the campaign looks worse than it performs.

Typical two-domain setups are a company website with a separate store, a store with an external booking system, or a campaign landing page on a different domain than the store.

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

A conversion in Google Analytics 4 is an event marked as important for the business, for example a purchase (`purchase`) or a form submission (`generate_lead`). Since March 2024, GA4 calls these events **key events**. The word „conversion” stayed with Google Ads.

You mark a key event in GA4 under Admin → Data display → Events, with the „Mark as key event” toggle next to the event you choose. I describe the whole setup step by step in the article [how to set up a conversion in GA4](https://webmountain.pl/en/analytics/ga4-conversions/). Marking alone isn’t enough when the customer changes domains. The event gets recorded, but with the wrong source and without the visit history. How an event differs from a conversion is something I explain in the article [what an event is in web analytics](https://webmountain.pl/en/analytics/what-is-an-event/).

## How to set up cross-domain measurement in GA4: 3 steps

**Before you start:** you need editor access to the GA4 property and access to the code or Google Tag Manager on both domains.

### Step 1: The same GA4 tag on both domains

Both domains have to send data to the same data stream, with the same measurement ID (`G-XXXXXXX`). If the second domain has a different ID or a different GA4 property, the data lands in two separate places and there is nothing to connect. You can check the ID on each domain in Tag Assistant (tagassistant.google.com).

### Step 2: Adding both domains in the tag settings

1. In GA4 go to Admin → Data streams and choose your web stream.
2. Click „Configure tag settings”.
3. Choose „Configure your domains”.
4. Add a condition for each domain, for example „Contains” → `company.com`, then `company-shop.com`.
5. Save.

From then on the tag adds the `_gl` parameter to links between these domains. The `_gl` parameter carries the customer and session IDs, so the second domain knows it’s the same person. GA4 also stops treating the domains on this list as traffic sources.

### Step 3: Excluding payment gateways as traffic sources

A customer who pays through an external gateway (for example PayU, Przelewy24, a popular Polish payment provider, or PayPal) comes back to the thank-you page from the gateway’s address. GA4 may then treat the gateway as the source of the visit and credit the purchase to `payu.pl / referral`. To prevent that, go to „Show more” → „List unwanted referrals” in the same tag settings and add the gateway domains. Gateways don’t go into step 2, because our tag isn’t on them.

## How to check that cross-domain measurement works

1. **The parameter in the URL.** Click a link from the first domain to the second. The URL of the destination page should contain `_gl=...`. If it doesn’t, the move isn’t a regular link, or the domain is missing from the list in step 2.
2. **DebugView.** In GA4, under Admin → DebugView (with Tag Assistant on), you should see one device that went through both domains, not two.
3. **The report after a few days.** In the Traffic acquisition report, sessions with your own domain as the source should disappear or drop to a handful of visits.

GA4 doesn’t fix data retroactively. The setup works from the day you deploy it, and old reports stay as they were. That’s why it’s worth writing down the date of the change, so you can compare the periods before and after later.

## Why the _gl parameter doesn’t reach the second domain

When you still see self-referral after the setup, the cause usually lies in how people move between the domains:

- **A script instead of a link.** The tag adds `_gl` to link clicks and submitted forms. A button that sends the customer over with a script (`window.location`) doesn’t get the parameter.
- **A redirect along the way.** A redirect to a language version or from http to https drops `_gl` if the server doesn’t pass URL parameters along.
- **A widget in an iframe.** A booking system embedded on the page is another domain inside the page, and the standard setting doesn’t cover it.
- **No consent for analytics cookies.** Without consent GA4 doesn’t store the ID, so there’s nothing to pass on.
- **An old tag on one of the domains.** The theme or a plugin still sends data under a different ID.

## GA4 conversions in Google Ads with two domains

Google Ads can count conversions in two ways: by importing key events from GA4 or with its own Google Ads conversion tag. With two domains, both ways need the ad click information to make it to the second domain. The `_gl` parameter carries that information too, so step 2 fixes both kinds of measurement. If your tags live in Google Tag Manager, the Conversion Linker tag also needs the list of domains.

Importing a key event from GA4 into Google Ads looks like this:

1. Link your GA4 and Google Ads accounts (in GA4: Admin → Product links → Google Ads).
2. In Google Ads go to Goals → Conversions and click „+ New conversion action”.
3. Choose „Import” → „Google Analytics 4 properties” → „Web” and select the event.

The most common mistake when both ways run at once is **counting the purchase twice**. It happens when the purchase is a primary conversion both from the Google Ads tag and from the GA4 import. The campaign then sees two sales where there was one and learns from an inflated result. One source should be primary and the other marked as secondary.

The numbers in GA4 and Google Ads won’t be identical anyway. Google Ads credits a conversion to the day of the ad click, GA4 to the day of the purchase, and the two systems split credit between channels differently. A gap of a few percent is normal. A large gap that lasts for weeks is a signal to check the measurement.

## When to hand measurement setup to a specialist

The three steps in this article are enough for a simple setup: two domains, regular links, one payment gateway. Paths across three or more domains, widgets in iframes, server-side tracking and stores where the consent banner blocks tags at the key moment take more work, as with [a missing purchase event in WooCommerce](https://webmountain.pl/en/analytics/missing-purchase-event-woocommerce-gtm/). If you still see self-referral after the setup, the problem is in the implementation, not in how the data is read.

At that point it’s worth walking through the customer path step by step with someone who has seen this bug in many accounts. Here’s what that looks like: [analytics and tracking setup](https://webmountain.pl/en/analytics-and-tracking/).

## Frequently asked questions

### Do subdomains need cross-domain measurement in GA4?

Usually not. By default GA4 sets its cookie on the root domain, so shop.company.com and blog.company.com see the same customer without any extra setup. The problem appears when someone manually set the cookie domain to a single subdomain.

### Will cross-domain measurement fix old data in GA4?

No. GA4 counts correctly from the day you deploy the setup, and earlier reports stay unchanged.

### Why did outbound clicks disappear after I turned on cross-domain measurement?

That's normal. GA4 no longer counts clicks on links to domains on the cross-domain list as exits from the site, because it treats both domains as one website.

### Is a key event in GA4 the same as a conversion in Google Ads?

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.
