GA4 Referral Traffic: Sources, Exclusions and Self-Referrals
Published:
Last Updated:
Category: Web Analytics
Authors: Shusaku Yosa
In GA4, referral is a medium commonly associated with visits from links on other websites. It helps identify sites that send visitors. If a payment service or your own domain appears, investigate the measurement journey before treating it as a successful acquisition source.
Unwanted referrals and internal-traffic filters solve different problems. Ignoring a referrer for attribution does not delete every event from that visit, and an IP-based internal-traffic rule is not a referral-domain exclusion.
Source, medium, channel and referrer
Field | Illustrative value | What it describes |
|---|---|---|
Session source | partner.example | The source recognized for a session |
Session medium | referral | The type of acquisition medium |
Session default channel group | Referral | Classification under Google’s channel rules |
Page referrer | Referring URL, when available | Referrer information collected with an event |
Social, advertising and AI services may be classified under other channels. Do not assume every external link belongs to the Referral channel. A referrer field also does not guarantee the full path of the linking page.
Find and analyze referral sessions
- Open Traffic acquisition for the intended property and date range.
- Select Session source / medium.
- Filter relevant referral rows.
- Compare sessions, engagement and meaningful key events.
- Add a landing-page breakdown where supported and inspect the actual placement on the referring site.
First user source describes original user acquisition; Session source describes session acquisition. Switching between them changes the question. Keep dimensions and metrics aligned rather than comparing their totals as though they were equivalent.
Choose the right response
Situation | Investigate first | Likely response |
|---|---|---|
A payment gateway appears after checkout | The outbound and return journey; tagging access | Consider an unwanted-referral rule where appropriate |
Your other domain appears | Stream identity, cross-domain configuration and redirects | Repair cross-domain measurement before hiding the symptom |
A suspicious source sends unusual activity | Event details, timing and evidence of real visits | Separate reporting filters from collection or abuse controls |
GA4 automatically ignores certain self-referrals and correctly configured cross-domain transitions. You do not need to add every owned domain manually.
Configure unwanted referrals carefully
In the web stream’s Google tag settings, open the expanded settings and find the unwanted-referrals list. Add a narrowly defined domain condition and document why it is needed. Interface labels can differ by language and account configuration.
The setting tells Analytics not to treat the matching referrer as an acquisition source. It affects future collection; it does not rewrite all historical traffic. Nor is it a mechanism for deleting spam events. Do not assume that changing the rule perfectly reconstructs an original marketing source that was never collected.
Internal traffic uses a different mechanism: define appropriate IP conditions and apply the relevant data filter, preferably testing before activation. Entering a referring domain into an internal-traffic workflow does not produce the same result.
Can GA4 show the referral path?
Page referrer can provide useful detail in supported reports or explorations. However, browser referrer policies and navigation behavior may restrict the value to an origin or omit it. GA4 cannot promise a complete list of every linking page.
For controlled partner campaigns, agreed UTM conventions can provide a more reliable placement identifier. Avoid acquisition UTMs on links within your own website; use interaction events for internal promotions and buttons.
Verify the journey after a change
Test an entry visit, the external service and the return to your site. Record the expected source and medium, whether identity and session continuity are preserved, and whether the success event fires once. Include consent conditions in the record.
For example, if a customer arrives through a campaign and returns from payment, the question is whether checkout introduces an unintended referral—not whether the gateway generates more marketing demand. Keep the configuration date in your reporting notes, since a classification change can alter channel trends without changing the underlying business.
Finally, compare referral volume with useful visits and qualified outcomes. A large referral count alone does not establish commercial value.
Related guides
Keep marketing reporting consistent
Use consistent metric definitions and reporting periods when reviewing results. See NeX-Ray’s supported integrations and reporting features, or start for free.
References
Official references checked September 28, 2026. Interface labels and available features can vary by account and rollout.
