Nearly everything that has to do with ads (both tracking and serving) is already standardized client side script, so it won't make much difference for publishers/advertisers. Ad agencies already want data vetted by someone like Comscore, and most publishers use tools like Google Analytics for their own purposes. I suspect those tools already account for invisible pre-rendering.
This doesn't really effect much, to be honest. People who want to inflate their stats already do so by counting bot traffic, iframe requests, etc. Google's been doing partial javascript evaluation for a long time as part of their spidering.
Re:WebKit and Chrome prerendering
by petercooper on Monday June 20, 2011 @07:44AM
(#2673742)
So won't this be confusing, as non-discriminating sites choose to inflate their page views by ignoring whether those were prefetches or real loads?
There are a lot of sites out there that use JavaScript reloads every X minutes to do this sort of thing already. More trackable but I bet they still include those numbers in their media packs ;-)
TechCrunch, for example, has this near the bottom of the source:
setTimeout('location.reload(true)',1200000);
So that's every 20 minutes.A more insidious trick to "inflate" your views would be to detect when a tab isn't open but still showing your site and to refresh a lot more often in that case (meaning the user won't notice).
So won't this be confusing, as non-discriminating sites choose to inflate their page views by ignoring whether those were prefetches or real loads?
And what about ads?