There are several ways to install Urchin. In this response I assume you use the tag method.
Urchin will create traffic sources based on document.referrer
, it doesn't guess, it uses real data.
When you install Urchin one of the options you need to set is the domain name. This setting is used to store a first party cookie that will hold session information including referral info.
Let's say your intranet site is intranet.mycompany.com
, this subdomain is private to your network but maybe the cookie setting in Urchin is set to mycompany.com
, this will create a cookie in that domain and this cookie will apply to all subdomains.
Maybe this hostname has other subdomains, some that might be accessible outside your corporation and since they share the same cookie, they will share the same traffic source as well.
google/(organic)
Imagine this scenario:
- User Looks for Company in Google
- User arrives at the main public site at www.mycompany.com. Urchin registers this as a new visit from google/(organic).
- User opens the intranet website
- Urchin uses the same cookie and this is seen as a continuation of the visit that already has a traffic source
- Urchin just reuses the google/(organic) traffic source defined in the cookie.
Also Urchin can share cookies with Google Analytics, so if you are not using Urchin, but instead Google Analytics the scenario above is also possible.
direct(none)
Now about direct/(none). This is used everytime urchin can't determine a better traffic source. In other words when the javascript variable document.referrer
is empty.
This can happen in a variety of moments, including but not limited to:
- Clicks on a pdf document
- Clicks in a Microsoft Office document
- Directly typing the url in the browser navigation bar
- Clicking in a bookmark
- Going from an HTTPS to an HTTP webpage