Fix self-referrals during checkout without hiding real acquisition sources

A buyer returns from an external payment provider and the conversion report attributes the sale to that provider. The original campaign seems to disappear during checkout.

Why this happens

A cross-domain journey can lose measurement continuity. A payment-provider referral and a separately owned checkout domain require different configuration decisions.

Step-by-step solution

1. Map every domain in the journey and identify which ones you control. Confirm that relevant pages use the intended analytics configuration.

2. For owned domains that should share a journey, configure cross-domain measurement and verify that redirects preserve the linker parameter.

3. For an external payment provider, review unwanted-referral settings according to your measurement design. Excluding a referral does not repair missing events or restore historical data.

Worked example

Test shop.example to checkout.example and back as one controlled journey. A third-party payment gateway should not be added to cross-domain configuration unless the integration actually supports that arrangement.

Verify the fix

Observe the domain transitions and final purchase in a test session. Confirm the original acquisition context remains meaningful and that events are not duplicated across domains.

Prevent a repeat

Retest whenever checkout vendors or redirect rules change. Do not exclude every unfamiliar referring domain, because that would conceal genuine traffic sources.

Reference

Official documentation or standards guidance

An original Gistmax troubleshooting guide. Scenarios and sample values are illustrative; configuration depends on your software version and environment. Cover diagram: Gistmax Tutorials.