A self-referral is when your own website appears as a source of traffic inside your analytics reports. Instead of seeing the ad, search, or email that actually sent a visitor, you see one of your own domains listed as the referrer. It almost always means a single visit got split in two and the two halves were never reconnected.
What is a self-referral?
Every time someone arrives on your site, analytics records where they came from. That source is called the referrer, and normally it's a search engine, a social link, an email, or a paid ad. A referral is when another website sends someone your way.
A self-referral is when that "other website" is actually you. Your own domain turns up in your list of traffic sources, sitting next to the real outside sources. A visitor can't really be referred to your site by your site, so it points to a tracking problem rather than a genuine referral.
Why self-referrals happen
The usual cause is a visitor journey that crosses between two domains you own, without cross-domain tracking set up to hold it together.
Say your main site is on one domain and your checkout or booking tool lives on another. A visitor clicks a Google ad, lands on your marketing site, then crosses over to the second domain to buy. To your analytics, that crossing looks like the end of one visit and the start of a new one. When they land on the second domain, the browser reports the previous domain as the referrer, so your own site gets the credit.
You'll usually see self-referrals when your setup includes:
- A checkout or payment page on a separate domain
- A booking, scheduling, or course tool hosted elsewhere
- Landing pages or microsites on their own domains
The conversion that belonged to the ad, email, or search that started the journey gets handed to your own domain instead. Paid campaigns look weaker than they are, and your funnels break because one journey is recorded as two unrelated visits.
How to fix a self-referral
The fix is to tell your analytics tool that the domains belong to the same site, so a visitor crossing between them stays in one continuous session instead of starting fresh. In Google Analytics 4, that's the cross-domain measurement setting. Once it's in place, the original source carries across the whole journey and your own domain drops off the referral list.
How Conversion Bridge Helps
If you use Google Analytics, Conversion Bridge can turn on GA4's cross-domain trackingA method of tracking user behavior as they move between two or more different domains, allowing website owners to maintain a consistent user journey across multiple properties. for you. You enable it in the Conversion Bridge settings and list the domains you own that run the same GA4 property, without touching the Google Analytics admin. From then on, a visit that spans those domains is measured as one sessionA session is a single visit to your website: a group of a visitor's actions within one window of time. Most analytics reports are built on it. with one source, so self-referrals stop and your campaigns get the credit they earned. The cross-domain tracking guide has the steps.
Frequently Asked Questions
Is a self-referral bad?
It isn't harmful to your site, but it's a signal that cross-domain tracking is missing, which means your visitor counts and traffic sources aren't accurate. It's worth fixing before you trust those numbers.
Why is my own domain showing as a referral?
Almost always because your site spans more than one domain and cross-domain tracking isn't set up. A visitor crossing between your domains gets recorded as a new referred visit, and the only referrer analytics can see is your other domain.
Do subdomains cause self-referrals?
Usually not, because subdomains like shop.yoursite.com share the same parent domain, so most tools keep the session together. It's separate top-level domains that trigger it.