A referrer is the web address a visitor was on just before they clicked through to your page. When they follow a link, the browser passes along that previous address in an HTTP header, so your server and your analytics can see where the click came from.
Think of it like a guest signing the visitors’ book at reception and noting who recommended them. You learn that this person arrived via a partner site, a Google search or a newsletter, which tells you which doors people are walking through. That is how analytics tools group traffic into channels such as referral, organic search and social. The referrer is tied to the URL of the previous page, though it is often trimmed to just the domain for privacy. A site can tune how much it sends with a Referrer-Policy setting, choosing between the full address, the bare domain, or nothing at all.
It is not perfect data. Browsers increasingly hide or shorten the referrer, and clicks from secure to non-secure pages may show nothing, so a chunk of visits land under direct or unknown. Privacy moves like restricting third-party cookies push in the same direction, making clean source data harder to get. So treat the referrer as one clue among several. Pair it with campaign tags in your links, the UTM parameters you add by hand, and you get a far truer picture of where a visitor really came from than the raw header alone.
At TopDevs we set up clean referrer and analytics tracking from day one, so a client can see which channels really bring visitors instead of guessing.
