Anyone else noticed an increase in "Not Provided" since Sun, Oct 30, 2011? I see a substantial spike from that day forward.
8:34 pm on Nov 2, 2011 (gmt 0)
Not provided in what? In what particular tool/log/field?
8:53 pm on Nov 2, 2011 (gmt 0)
I'm surprised there isn't much discussion on this one. This is above and beyond what folks have been discussing to date. There have been significant increases in "Not Provided" stats starting on Oct 30, 2011. I've had 10+ people confirm on Twitter and there are plenty of screenshots floating around depicting the increase. It is rather significant. This is not the measly increase we first saw when it was announced.
On one site I monitor, we were averaging about 500 per day. That jumped to 1,700 on Oct 31, 2011 and it then jumped to 4,200 on Nov 01, 2011 and appears it will be in the same range if not more once Nov 02, 2011 closes. Similar spikes are being seen by quite a few folks.
^ I was expecting to see it reported here at WebmasterWorld first. Most appear to think I'm talking about the first SSL announcement. I'm not that far off the grid. Sheesh...
2:30 pm on Nov 3, 2011 (gmt 0)
18% yesterday for us... Specifically the obfuscated, not provided, Google referrals.
4:58 pm on Nov 3, 2011 (gmt 0)
yes, very annoying not set and not provided make up 20%, time to remove that code?
10:18 am on Nov 8, 2011 (gmt 0)
Not sure if it's connected, but 2 site's i monitor received dramatic spikes on 4 thru 5 Nov from [t.co...]
Everything's back to normal now - but it throws GA performance measurements out, so quite frustrating.
11:57 am on Nov 8, 2011 (gmt 0)
I'm not keen on flying blind.
I hit 19% yesterday. If the trend continues, I'm going to look at phasing in alternative analytics so I can compare an another solution with Google Analytics while data from the later is still largely available.
Given the lax response on this, I kind of feel like I'm over overreacting -- but in a case like this, I'd rather be safe than sorry.
Any other opinions?
12:46 pm on Nov 9, 2011 (gmt 0)
Self correction: SSL queries of logged in users from G aren't visible to other analytics services either.
4:27 pm on Nov 14, 2011 (gmt 0)
For some clients I've been seeing the number creep north of 20% (this for the last 7 days, i.e., 11/7 to 11/13). Not happy at all, but I think we're fairly helpless on this one...at least until Google starts getting more heat from Federal government inquiries into its monopolistic practices, at which point this issue should start getting more sunlight (i.e., "Protecting privacy? Really? Like you DON'T do for visitors clicking through paid ads?")
1:04 pm on Nov 16, 2011 (gmt 0)
I'm seeing 14% "not provided" this week, and the "not provided" is converting nicely at above averages.
I'm a bit surprised over here that there's little discussion and apparently not much concern.
1:09 pm on Nov 16, 2011 (gmt 0)
Also 9% "not provided" on a much larger site. 9% in this case is over 40K visitors. Ouch.
1:10 pm on Nov 24, 2011 (gmt 0)
So this is possibly a useful hack to get some data back.
The usual caveats apply.
I will be testing it over the long holiday weekend.
Thanks chewy! Looking forward to hearing what you think.
3:39 pm on Nov 25, 2011 (gmt 0)
if workarounds are the best we can come up with, that is a start.
my preference is, and has always been, that we need to pressure the powers that be to give webmasters reasonable access to information over obscuring and obfuscating a small but increasing subset.
professionals with the appropriate knowledge have the ability to 'read between the lines' and see the data that is missing.
but it is a great thing to be able to say to an executive "we know x is doing y".
it is not so great to have to say "it is a reasonable and educated guess that x may be causing y to happen".
9:35 pm on Dec 1, 2011 (gmt 0)
We've noticed an increase in (not provided) on most of the websites we track. Even more strange though is that one of our client sites do not have even one instance of (not provided) though we do show (not set). I find it hard to believe that not one person coming to the site is logged into Google. Any ideas?