Reasons for “Direct Traffic” in referrer reports
(Applies to: all)
“Direct Traffic” is a legacy name that no longer is valid. Once upon a time, in long-ago simpler days (approximately 2003), the absence of a referrer in log files could only mean that somebody typed your site’s name into the browser’s address window, or used a bookmark, which amounts to the same thing.
No longer.
Here’s our current list of reasons for an empty referrer field, a.k.a Direct Traffic, or more accurately “Referrer Unknown Traffic.”
- Somebody really did type in the address or used a bookmark to get to your page
- They clicked on a link in an email (not always true. If they used some kind of web mail, the web mail server will be the referrer)
- The link was in a document
- The link originates at a secure (https:) page and your page is not secure (http)
- Spiders and bots were working from a list of URLs from a previous crawl (this one mostly applies to server logs, rarely to SDC)
- Spiders and bots may be programmed to suppress the referrer information (this one mostly applies to server logs, rarely to SDC)
- The visitor is using IE and the link to your site was in Javascript. Javascript links to your site include those that open your site in a new browser window, or any kind of javascript redirect. Many banners’ links are programmed this way.
- The visitor is using IE and the link to your site is from within a Flash application (there are a lot of ways to do this in Flash so there may be exceptions)
- Your landing page redirects to another page via a 301 permanent server-side redirect
- The link was on an intranet or some other web site behind a proxy or corporate gateway that was set up to strip referrers from requests
- The visitor has made changes to their browser that suppresses the referrer information
- Another site has put your page content into an iFrame and coded the frame to suppress the referrer, in order to make it difficult for you to find out who is framing your content
As you can see, IE is responsible for a big proportion of non-referrer visits. If you want to get a better idea of your referrer mix, you could try a Firefox-only Referrers report.
If you want to do a little more sleuthing, go to a search engine and request a list of all the indexed pages that have links to your site (or to a particular page). (Search for “link:www.yoursite.com”) Visit those pages to see if the links have the quirks described above.
July 31 update: Linda Bustos wrote a good treatment of the same thing for Google Analytics, here.
12 comments
What about when the referring site has coded links to open in a new window using ‘target=”_blank”‘ or ‘target=”_new”‘? Or are the results browser-dependent? Now I’ve got to do some of my own testing now that I’ve raised this question….
Those seem to produce a referrer, at least in IE 7. The new-window problem is pretty much javascript links that open in a new window.
Quick question about number 4 -
The link originates at a secure (https:) page and your page is not secure (http)
What if its the other way round. Link originates at a not secure page(http) but my page is secure (https)?
Thanks
Anyone??
Sorry. Non-Outsider activity level too high, glug glug.
No, the other way around is fine. The referrer gets through as usual when the origination is non-secure and the destination (the page you track) is secure.
[...] being passed by the user’s browser, and this can happen for lots of reasons as defined in this rather neat list. I have done some tests on some of my clients’ sites and estimate that in some cases up to [...]
[...] leave a comment » I came across this post at Jonny Longden’s blog on how Direct Traffic isn’t what it seems, always. I’m only re-blogging it because this fact cannot be emphasized enough. To quote: The fact is, this definition of direct traffic in web analysis is extremely misleading. It’s true that the direct traffic bucket does include bookmark traffic and typed URLs, but these days (unless you are very strict about your campaign tracking parameters) it can and does include all kinds of other stuff. All it really means is that the session started without a referrer being passed by the user’s browser, and this can happen for lots of reasons as defined in this rather neat list. [...]
[...] WebTrends Outsider has a good list of reasons for “Direct Traffic” in referrer reports. [...]
Great list, and point that direct traffic isn’t segmented well enough. I wonder if we will see further insights and segments in GA, ST and Omniture?
[...] WebTrends Outsider uvádí seznam důvodů, proč zůstává pole referrer field [...]
[...] Here is a list of traffic sources that cause direct traffic (thanks to the WebTrends Outsider): [...]
[...] Fuente: Webtrends Outsider [...]
Leave a Comment