Once you deactivate the Stats module, Quantcast should not appear on your site anymore. If it does, it’s either because it’s included by another plugin or service, or because the page was cached.
If you use a Cache plugin on your site, could you try to clear the page’s cache?
Hi Jeremy, I found the problem.
I first deactivated all plugins I don’t use with Jetpack (including stats ofcourse) plus one I use, the Jetpack Comments plugin. I cleared cache, quantcast was gone ( yeah! ).
Then I activated the Jetpack Comments again, cached, and the quantcast was back again ( mmmm 🙁 )
Can you explain why Quantcast is being used for the Jetpack Comments part?
Kind regards,
Willem
Nice catch, I didn’t think of Jetpack Comments!
Jetpack’s comment form is actually hosted on WordPress.com, and served via an iFrame on your site. Since we use Quantcast on WordPress.com, the Quantcast is loaded on all our pages, including the comment form page that appears on your site.
That’s indeed an oversight on our end: we already mention in the readme that the Stats portion of Jetpack uses Quantcast to enhance its data, but we didn’t realize that it was also included in Jetpack Comments because of the iFrame.
I took note of the problem yesterday, and we will update the readme to mention Jetpack Comments.
@willem We have now removed the Quantcast Javascript for the Comments module, until we can update Jetpack’s description and explicitly mention that the Comments module uses Quantcast.
Hi Jeremy, that’s ofcourse a ‘good’ way, mention first then include. But for what reason do you want to include it back to Jetpack Comments if you didn’t thought of Jetpack Comments in the first place?
Also curious at your opinion about Quantcast with al the ‘negative’ links I mentioned before. Because of that, with the knowledge as it look right now thats it’s coming back in Jetpack Comments maybe I think of going to look for an alternative.
But I just don’t know to much about Quantcast, so please you opionion.
Kind regards,
Willem
The DoNotTrack Plugin should still be an effective way to block QuantCast, regardless of means of injection.
But for what reason do you want to include it back to Jetpack Comments if you didn’t thought of Jetpack Comments in the first place?
@siebje As Matt mentioned in one of the threads you mentioned earlier, Quantcast allows us to track useful information that we can use to improve the modules later on.
However, you can always block QuantCast on your site thanks to the plugin mentioned by Chip.
You can also opt-out from QuantCast here:
http://www.quantcast.com/opt-out
