TRACKING SPECIALIST — BARIS ASA · LONDON
Synctag
Start the check → TRACKING SPECIALIST — BARIS ASA · LONDON

READING ROOM › SYMPTOM FILES › SYM-046

SYMPTOM FILE SYM-046 FILED 08 NOV 2026 · REVISED 08 NOV 2026

Payment gateway showing as referral in GA4: which domains to exclude and how to check it worked.

ALSO FILED AS
  • “payment gateway showing as referral in GA4”
  • “PayPal showing as referral in GA4”
  • “Stripe showing as referral in GA4”
  • “Klarna showing as referral in GA4”
  • “checkout.stripe.com referral GA4”
  • “paypal.com / referral getting purchase credit”
  • “GA4 referral exclusion for payment gateways”
  • “unwanted referrals not working GA4”
  • “3-D Secure bank page showing as referral”

Baris Asa, tracking consultant, London · Last checked: 8 November 2026

PayPal, Stripe or Klarna showing as a referral in GA4 means the shopper left your site to pay, came back, and GA4 read the payment page as a source: either the return started a new session (a payment step longer than the 30-minute timeout), or attribution reports credited it as a touchpoint. The fix is in GA4 Admin, no code: list each payment hostname as an unwanted referral, prove it with a test order, and date the change.

The order is real. The credit moved: a sale your ad or email earned is filed under paypal.com / referral, and paid and email look weaker than they are. If you import GA4 key events into Google Ads, the bidding can learn from the same misattribution.

The fault is on file as F-205 , self-referrals and session fragmentation. That page explains the mechanism and the other branch, your own domain as a referral. This note is the gateway branch, from finding the hostnames to a test that proves the fix.

Is it really the gateway?

Check in GA4 first. No developer needed.

  1. Reports, Acquisition, Traffic acquisition. Set the primary dimension to Session source / medium and type referral in the search box.
  2. On the Key events column header, open the dropdown and pick purchase. Session key event rate is now the share of those sessions that ended in a purchase.
  3. A payment hostname whose rate sits far above your site average is the gateway taking credit. Shoppers come back from a payment page to finish an order, not to browse.

If the row is your own domain, such as shop.yourbrand.co.uk / referral, this is the other branch. It is covered on F-205 and, for two root domains, in the cross-domain note.

Which domains do I add?

Every payment hostname that sits right before a purchase. Small ones, like a bank’s verification page, rarely reach the top of Traffic acquisition, so list them from the purchase event itself:

  1. Explore, Blank. Add the dimensions Page referrer and Event name, and the metric Event count.
  2. Filter Event name to purchase. Put Page referrer in rows.
  3. Each row is the page the shopper was on just before the confirmation page loaded. Your own checkout URLs are expected. Every other hostname is a candidate for the list.

What you will usually find:

  • PayPal. paypal.com or a subdomain of it. A Contains condition on paypal.com usually covers them. If a country domain such as paypal.de appears, add it separately.
  • Stripe. Only if you send shoppers to a Stripe-hosted page. Stripe’s default hosted domains are checkout.stripe.com, and buy.stripe.com for Payment Links. Stripe also offers a custom domain, a subdomain of your own such as payments.yourbrand.co.uk. GA4 ignores referrers from your own domain and its subdomains by default, so a custom domain should not show as a referral. If it does, check that it sits under the same root domain as your shop (a shop on .com with payments on .co.uk does not); if it does not, list it.
  • Klarna, Clearpay and other pay-later services. Same pattern as PayPal when the shopper is sent to their page or app and back. Copy the hostname your data shows.
  • 3-D Secure pages. The bank’s card check can redirect to the bank’s own page, and the hostname varies by bank. Expect several small rows.

What stays off the list: partners, affiliates, review sites, press and marketplaces. They are real referrers, and excluding them hides traffic you paid for or earned. Only checkout, payment, wallet and verification hostnames go on. Google warns against suppressing referrers broadly for the same reason: you lose source data you want.

What the data showsWhat it meansWhat to do
paypal.com / referral, rate far above site averagegateway return read as sourceadd to unwanted referrals
bank hostname as Page referrer on purchase3-D Secure redirectadd the hostname
your own domain as referralidentity broke at your hopF-205, cross-domain note
paid traffic filed as (direct)click ID lost on the way inF-204
Referral rows after a payment step · what each one points to · worked example, illustrative, not a client account

How do I set it up?

  1. GA4 Admin, Data collection and modification, Data streams, Web, your stream.
  2. Configure tag settings (at the bottom), Show all, List unwanted referrals.
  3. Add one condition per hostname. The match types are Contains, Begins with, Ends with, Exactly matches and Matches RegEx. Contains on paypal.com is the simple choice. Avoid Contains on a fragment like pay, which matches far more than you meant.
  4. Save. GA4 allows 50 conditions per web stream. They apply on every page that carries the Google tag, which adds ignore_referrer to matching events.

Do it on the stream your site actually sends to. A property with an old second stream is a common place for the list to go missing.

What changes after the exclusion?

The sale goes back to the ad, email or search that brought the shopper.

The detail: GA4 stops reading the gateway as a source, so the return counts as direct. A direct session takes the shopper’s earlier non-direct source if there is one within the key-event lookback window set in Attribution settings, 90 days by default. With no earlier source, it stays (direct).

One limit. If the payment step ran past the session timeout, the return is still a second session. Its source is corrected, but session counts stay split. The timeout can be raised in the same Configure tag settings menu. It changes how every session on the site is counted, so treat it as a separate decision.

How do I check it worked?

Whoever runs your shop admin can place and refund the orders. Each test answers a different question, because GA4 credits sources in two ways: per session, and per key event.

  1. Open your site from a tagged link, such as ?utm_source=test&utm_medium=check.
  2. Quick order. Pay with the gateway straight away and finish the order.
  3. Slow order. From the same tagged link, go to the payment page and leave it open for 35 minutes before paying. This forces the new session that a long payment step causes.
  4. Next day: Explore, Blank. Dimensions Transaction ID, Source / medium and Session source / medium. Metric Purchases. Find both orders.
  5. Read them. Source / medium (no “Session” prefix) is the key-event credit: on both orders it should read test / check, not the gateway. Session source / medium on the slow order is the session test: it should also read test / check. Before the fix, it reads the gateway.
  6. Repeat for each payment method you offer. A method that still shows the gateway has a hostname you have not listed.

Page referrer will still show the gateway on these orders. That is expected: it is the raw browser referrer, not the source GA4 credits.

I added it and it still shows. Why?

  • The date range includes days before the change. Start it on the day after.
  • Old sessions are still passing credit on. A shopper whose last non-direct source was the gateway before the change can carry it into later direct visits, for up to the lookback window.
  • The hostname differs. Your data says www.paypal.com and you entered something narrower, or a bank page you never listed. Compare character by character.
  • Wrong stream. The list belongs to one web stream. Check it is the stream whose measurement ID loads on your checkout.
  • It is your own domain. The gateway is gone and your checkout subdomain or second domain now shows. That is the other branch of F-205 , fixed with cookie domain and cross-domain settings.

What about the months before the fix?

Two things help you read the old rows.

  • A custom channel group. Admin, Data display, Channel groups. Google says custom channel groups apply to reports retroactively, so a “Payment return” channel can lift the gateway rows out of Referral for past months. It relabels them. It does not recover the source that earned the sale.
  • Key event attribution paths. Advertising, then Key events, then Key event attribution paths. Where the shopper kept the same cookie, a path can show the channel before the gateway. Read it as a pointer, not a corrected report.

Annotate the date of the change. Anyone comparing month on month will otherwise read a jump in paid or email as performance.

When is it more than a settings change?

  • Google Ads bids on GA4 key events, and months of purchases were credited to the gateway.
  • More than one web stream or property collects the checkout.
  • The gateway row is gone and your own checkout domain now shows as a referral (F-205 ).
  • Paid clicks arrive as (direct) before the payment step even starts (F-204 ).

Common questions

PayPal is showing as a referral in GA4. What do I do?

List paypal.com, and any other payment hostname your data shows before purchases, under GA4 Admin, Data streams, your web stream, Configure tag settings, Show all, List unwanted referrals. Then place a test order and read it in an Exploration by transaction ID. The source should be your test link, not PayPal. Note the date: sessions recorded before the change keep PayPal as source.

Which domains should I add to unwanted referrals?

Payment, wallet and verification hostnames that sit right before your purchases: typically paypal.com, checkout.stripe.com, a klarna.com hostname, and the 3-D Secure page of a shopper’s bank. Find them with Page referrer on the purchase event, and copy them exactly. A Contains condition on paypal.com usually covers PayPal’s hostnames; add any country domain, such as paypal.de, separately. GA4 allows 50 entries per web stream.

I added PayPal to unwanted referrals and it still shows. Why?

Usually one of five things: the date range still includes days before the change, the hostname in your data differs from the one you entered, the entry sits on a different web stream, later direct visits are still inheriting credit from an old PayPal session, or the row is your own domain rather than the gateway.

Does excluding a payment gateway fix past data in GA4?

No. A custom channel group can move the old gateway rows out of Referral into a channel of their own, and it applies to past data, but it only relabels them. It does not recover the ad or email that brought the shopper.

Do I need cross-domain tracking for PayPal or Stripe?

No. Cross-domain measurement is for domains you own and tag. You cannot put your tag on paypal.com or checkout.stripe.com, so those go on the unwanted-referrals list. Cross-domain is for a checkout or booking step on a second domain of your own.

Will an embedded payment form stop the referral?

Usually. A form that stays on your page does not send the shopper away, so there is no return to read as a source. Stripe offers its Checkout either as a redirect to a Stripe-hosted page or embedded on your site. A payment method that redirects, such as Klarna or a bank-redirect method, can still send the shopper away and bring a referral back.

Sources

Read on 8 November 2026:

  • Google Analytics Help, Identify unwanted referrals (the Admin path; ignore_referrer=true added to matching events; 50 per data stream; the third-party payment processor example; a session recorded before the exclusion stays attributed to the excluded domain, and later direct sessions can inherit that credit; referrers on the same domain or its subdomains are ignored by default; do not set ignore_referrer on all pages)
  • Google Analytics Help, Configure your Google tag settings (match types Contains, Begins with, Ends with, Exactly matches, Matches RegEx; session timeout 30 minutes by default, adjustable in hours and minutes)
  • Google Analytics Help, About Analytics sessions (sessions use non-direct last click; a direct return inside the key-event lookback window keeps the earlier source; 90 days by default)
  • Google Analytics Help, Scopes of traffic-source dimensions (Session source is session-scoped; Source with no prefix is event-scoped and credits key events under the reporting attribution model)
  • Google Analytics Help, Custom channel groups (Admin, Data display, Channel groups; applied to reports retroactively; two custom groups on standard properties)
  • Google Analytics Help, Advertising and attribution (Advertising, Key events, Key event attribution paths)
  • Stripe Docs, Build a payments page (Checkout as a redirect to a Stripe-hosted page or embedded on your site; the embedded form works without redirection)
  • Stripe Docs, Use your custom domain (default domains checkout.stripe.com and buy.stripe.com; a custom domain is a subdomain of your own, such as payments.example.com)

← back to the reading room