Forum Moderators: martinibuster
There is a huge difference between the number of page impressions that my AdSense Reports say I get, and what my web server log files say I'm getting. It's enough to amount to many hundreds of dollars per month in losses.
For May the difference was 33%, and so far this month the difference is a whopping 47%! That is, Google claims I'm only getting half the traffic that my web server says I am!
Now, this could happen if half my visitors used ad blockers or disabled javascript - but I find it hard to believe that so many would do so, or so suddenly. Also my site's demographic is not the sort to be sophisticated enough to know about ad blocking software.
I haven't analyzed further back than last month, but I certainly will. I'm afraid I let my site go on autopilot for too long because I got busy with other things.
I'll certainly contact AdSense support in hopes they can correct it, and maybe pay me for underreported clicks, but I'd like to know if any of you see this too, on your own websites.
Note that this is just the page impressions - nothing to do with channels, which often yield weird results.
For most of the time I've been in AdSense, the difference between their reports and my logs has been consistently very small.
Take scrapers, good and bad bots, and people with Adblockers and disabled Javascript, and you've got quite a group that retrieves a page but does not see ads. I would look for scrapers and bots, and no, I would not worry too much.
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1;1813)
and read this thread :
I'll certainly contact AdSense support in hopes they can correct it, and maybe pay me for underreported clicks
hahaha.
Even with the one in a million chance that Google is trying to cheat you out of money, they would never admit to it. Do not contact the Google Monster.
[edited by: StoutFiles at 12:00 pm (utc) on June 25, 2008]
Do not contact the Google Monster.
Very good advice here. I absolutely second this: DO NOT CONTACT GOOGLE with this issue.
I think the ONLY reason to contact those overworked, underpaid people at The Plex is when the house is on fire. There's always the risk that you contact the wrong person, or the right person on the wrong day, and they see stuff they don't like on your site. Then your account may be at risk. Why take that risk?
There is a huge difference between the number of page impressions that my AdSense Reports say I get, and what my web server log files say I'm getting.
They are not the same animal!
Google Page Impressions are how many times AdSense have served a new set of ads and this does not happen every time someone uses your site/pages.
If AdSense is serving up the same ads it usually means there is a lack of ad inventory or possibly someone has paid to target your site. Possibly they are serving you the best paying ads they can do, this is something we never know.
Either way MY Google Page Impressions never agree with my own logs, I can kind of correlate them and I feel sure you will be able to once you have enough data.
And don't bother contacting them, their boilerplate responses will drive you crazy! :-(
Either way MY Google Page Impressions never agree with my own logs
Do they just quarrel with each other or do they get down and dirty with hand to hand combat?
<end off topic>
For what it's worth, my page impressions this month are on a roller coaster just like my earnings.
do they get down and dirty with hand to hand combat
Just like Christina Aguilera:-)
You might check your server logs for UAMozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1;1813)
Damn. That looks like what it is.
It doesn't account for the whole discrepancy, but in second place I see this:
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
This difference is SV1 instead of 1813.
Is that also from AVG?
I'm curious about "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)" too--it's #2 in my files as well.
You might check your server logs for UA
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1;1813)
Damn. That looks like what it is.It doesn't account for the whole discrepancy, but in second place I see this:
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
This difference is SV1 instead of 1813.Is that also from AVG
I'm lost. For the benefit of non native techglish speaking people like me, can you please translate the last two posts? I just checked my logs and see those lines too.
We’ve added "SV1" to the UA string so it’ll start looking something like this:HTTP_USER_AGENT :Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 1.0.3705)
This will let site authors know that they’re being visited by someone who’s running an IE browser on the latest, most secure Microsoft platform. Right now only XPSP2 has this token, but soon you’ll see this token show up on other platforms as we bring our security enhancements to them.
SV1 stands for "Security Version 1" by the way. We’re proud of the security work that we’ve done in XPSP2 and wanted to be sure that site authors had some way to differentiate users running the latest version of IE.
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1;1813)
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1;1813)
For more, read the post I mentioned earlier in this thread.
