A referral source is where a visitor came from: the website, app or link they clicked to reach you. Analytics tools read it from the visit's first page, and it's the raw material for every "traffic by channel" report you've seen.
The phrase has a second meaning on sales and healthcare forms. There it's the answer to "how did you hear about us?", a field someone fills in, and this post is about the one your analytics records on its own.
Where it comes from
When someone clicks a link, their browser usually tells your site which page they were on. That's
the referrer. An analytics script reads it on the first page of the visit and records the site's
domain, such as news.ycombinator.com, as the source.
UTM tags take priority. If the link carries utm_source=newsletter, that's the source, whatever the
referrer says. Some tools also accept a plain ref or source parameter.
Referral source vs referral channel
The source is the specific site, and the channel is the broader group it falls into.
Google Analytics 4 sorts sources into channels such as Organic Search, Organic Social, Email and
Referral. Its Referral channel holds traffic whose medium is referral, app or link, which in
practice means links from other websites that aren't a search engine or a known social network. So
a visit from a blog that mentioned you is a referral, and a visit from Google is organic search, even
though both had a referrer.
Why referral sources go missing
Plenty of visits arrive with no referrer at all, and they end up counted as Direct.
- Apps. Links opened from desktop chat apps, email clients and some mobile apps often send none.
- Privacy settings. A page can ask the browser to send no referrer, and some browsers trim it to the domain or drop it.
- Typed addresses and bookmarks. These have no referrer by nature.
The fix for links you control is to tag them. Add UTM parameters to newsletter links, social posts and anything you share in an app, and the source survives even when the referrer doesn't. Our guide to UTM parameters covers how to name them.
Referrals you don't want
Some referrers are your own plumbing. When a buyer comes back from a payment page like Stripe Checkout, or moves between your subdomains, the browser reports that site as the referrer. Counted as a new source, it would steal the credit from the channel that brought them.
GA4 handles this with a list of unwanted referrals in each data stream's tag settings. Add your payment provider and any domains you own.
How Spreelytics records it
In Spreelytics, the source is the utm_source, source or ref value on the first page, or else
the referring site. Visits from your own site and its subdomains, and visits coming back from a
payment page like Stripe, get no source, so they never take credit. Traffic from AI assistants such
as ChatGPT and Perplexity gets an AI channel of its own, apart from Referral.
The full rules are in Definitions. To see which sources bring in paying customers rather than only visits, see how to see which marketing channel earned each Stripe payment.