: Google analytics direct traffic report We launched a blog post which got picked up by a lot of social sites and it's given us a lot of traffic over the last few days. In Google Analytics

@Chiappetta492

(direct) can be misleading. Traditionally, people think of it as meaning "people typed in my URL directly"; the reality is usually a mix of that and of traffic sent from places that don't pass an HTTP REFERER header (and don't have some sort of manual tagging using utm_* parameters).

Specifically:


Non-web sources like smartphone apps, mail clients, and desktop apps. (Twitter for iPhone, Outlook, etc.)
HTTPS traffic linking to an HTTP page (HTTPS only Twitter and Facebook, Gmail, etc.)
Privacy blockers that prevent pages from passing referrers (less common)


So, traffic from Twitter isn't the same thing as traffic that Google Analytics credits as traffic from Twitter.com; that's only the subset of Twitter traffic that came from the web client AND was on HTTP. Same thing with Facebook; only traffic from non-HTTPS, web-based Facebook.com will track as being from Facebook.com; the rest will be tracked as (direct).

Vote Up Vote Down

@Shelley277

Perhaps the social site is using a redirect which strips the referrer? This is usually not the case for mainstream ones like Facebook though.

Certain privacy tools like ZoneAlarm are known to strip referrers too. These are not used that often either but is the only other possibility I can think of.

Vote Up Vote Down