How to remove https://stats.wp.com/
-
My page is loading
<script data-wp-strategy="defer" defer id="jetpack-stats-js" src="https://stats.wp.com/e-202623.js"></script>
but I have the traffic options disabled under /wp-admin/admin.php?page=jetpack#/traffic. It’s problem for us because this is not implemented with the Subresource Integrity protocol in mind.
I have seen https://wordpress.org/support/topic/how-do-remove-this-stats-js-code/ but it seems a bit different.
-
If you are using a browser, you have to open the page in an iframe (so the browser doen’t set Sec-Fetch-Dest: document). It’s simpler to use a
curl https://store-wp.mui.com/.> A screenshot showing where you’re seeing the script.
> The Jetpack version you’re running
15.8
> Confirmation that Site Stats is disabled under Jetpack → Settings → Traffic.
Proof:
I have tried to flush the cache, but it didn’t work. There are no cache enabled.
We could solve the issue with this logic:// We have disabled the WordPress / WooCommerce / Jetpack analytics, but them keeps
// injecting a script in the page for some reason. This logic forces it out.
// See https://wordpress.org/support/topic/how-to-remove-https-stats-wp-com/
add_filter('jetpack_active_modules', 'force_kill_jetpack_tracking', 999);
function force_kill_jetpack_tracking($modules) {
if (is_array($modules)) {
return array_diff($modules, ['woocommerce-analytics', 'stats']);
}
return $modules;
}Thanks for the follow-up and the code sample. Your filter is the right approach, and I want to explain what’s actually going on here because it’s more nuanced than it looked at first.
There are two separate Jetpack modules that independently load scripts from stats.wp.com:
- The Stats module, which enqueues
stats.wp.com/e-YYYYWW.js(handlejetpack-stats). This is what the toggle under Jetpack → Settings → Traffic controls. - The WooCommerce Analytics module, which enqueues
stats.wp.com/s-YYYYWW.js(handlewoocommerce-analytics). This one auto-activates whenever WooCommerce and Jetpack are both active and connected. There’s no toggle for it in the Jetpack settings UI.
So when you disabled Stats under Traffic, that stopped the
e-script, but thes-script from WooCommerce Analytics kept loading because it’s a completely independent module. That’s why your filter targets both'woocommerce-analytics'and'stats'and that’s the correct way to handle it.On the discrepancy where Stats appeared disabled on your end but was still active on the backend; I’m not sure what caused the mismatch there. It may have been a settings sync issue between the UI and the server-side module state. I’ve deactivated it from the backend for you, and your filter covers both modules regardless, so you should be good either way.
Regarding the SRI concern, that’s valid feedback 🙂 I’ve logged it internally so the team is aware of the use case. For now, the
jetpack_active_modulesfilter you’re using is the most reliable way to ensure zero requests to stats.wp.com.Hope that’s all clear! Let me know if you have any other questions.
(Internal ref for the feedback: JETPACK-1721)
Actually, I could find a way to disable the analytics without needed a custom PHP logic. WooCommerce Analytics was enabled under the hidden /wp-admin/admin.php?page=jetpack_modules page even though it was disabled under the WooCommerce settings. Disabling it there solved the issue.
- The Stats module, which enqueues
You must be logged in to reply to this topic.
