Timeline for A lot of "(direct) / (none)" traffic in Google Analytics
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 12:37 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Jul 16, 2013 at 13:57 | history | edited | s6mike | CC BY-SA 3.0 |
added further direct visit causes; Post Made Community Wiki
|
| Jul 6, 2013 at 18:06 | history | edited | s6mike | CC BY-SA 3.0 |
added 208 characters in body
|
| Sep 13, 2012 at 22:03 | review | First posts | |||
| Sep 23, 2012 at 20:19 | |||||
| Aug 29, 2012 at 10:34 | history | edited | s6mike | CC BY-SA 3.0 |
Updated to include ssl referrals
|
| Aug 29, 2012 at 10:23 | history | edited | s6mike | CC BY-SA 3.0 |
added 95 characters in body
|
| Aug 29, 2012 at 10:21 | comment | added | s6mike | Actually that's not quite right. Encrypted.google.com doesn't pass on any referral data - so I'll add this to the list. However, while logged in users of www.google.com are also on ssl, this only obscures the search term with (not provided) (due to recent changes made by google), the rest of the referral information is left intact. I've just double checked this is the case by testing in my browser. | |
| Aug 24, 2012 at 21:39 | comment | added | Dan Grossman |
Add to your list: Everyone coming from a Google search that's signed into a Google account. They're automatically put on https://, and transitioning from https:// to http:// when clicking a search result to a non-SSL site wipes the referrer.
|
|
| Aug 24, 2012 at 20:48 | history | edited | s6mike | CC BY-SA 3.0 |
Found better link for explanation of campaign tagging
|
| Aug 24, 2012 at 20:16 | history | answered | s6mike | CC BY-SA 3.0 |