As publishers, why should we be supporting any of these services, Quantcast included?  Am I really going to have to put 12 different JS includes on my site and pass on my users' browsing history to these companies just on the slim chance that some advertiser is using their stats?   I get enough complaints already about the Google Analytics tracking (and that's after putting it on the bottom of the page to minimize the chance of blocking the page, thus hurting my stats).<p>Everyone is talking about "pixels," but actually giving publishers blocking JS includes.  This means that as a publisher, you're going to have to prioritize the user experience versus tracking, and also prioritize the tracking!  If you put the Comscore JS under the Quantcast JS, then the slower the Quantcast JS returns, the lower your Comscore stats will be (because it gives the user more time to navigate away from the page).  It seems like it would give an incentive to the analytics firm to serve the tracking JS as slowly as possible.<p>I wish we could just make portions of our Google Analytics data public and be done with it.  I don't think the "pixel include" race is going to scale very well.