Tips, tricks, and pokes, just WebTrends Analytics
Random header image... Refresh for more!

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.”

  1. Somebody really did type in the address or used a bookmark to get to your page
  2. 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)
  3. The link was in a document
  4. The link originates at a secure (https:) page and your page is not secure (http)
  5. Spiders and bots were working from a list of URLs from a previous crawl (this one mostly applies to server logs, rarely to SDC)
  6. Spiders and bots may be programmed to suppress the referrer information (this one mostly applies to server logs, rarely to SDC)
  7. 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.
  8. 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)
  9. Your landing page redirects to another page via a 301 permanent server-side redirect
  10. 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
  11. The visitor has made changes to their browser that suppresses the referrer information
  12. 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.

Share:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google

Tags

, , ,

Somewhat Related Posts

  • Cool custom report: Small-scale but interesting referrers
  • ...
  • Beyond WT.srch — the better way to track PPC
  • ...
  • Filtering out internal traffic (from your own organization)
  • ...

    2 comments

    1 MitchellT { 05.22.08 at 9:01 am }

    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….

    2 rocky { 05.22.08 at 3:04 pm }

    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.

    Leave a Comment