csonnek

@koominen Thanks for the additional information! I removed http://jasittenmatkaan.fi from your account.

You should be all set! We’ll mark this resolved for now.

Since we’ll be helping you via email, we’ll mark this resolved for now.

Hi there:

Looking at your site’s page source, it looks like our stats tracking javascript is not being set in your page’s footer.

What we should see is: https://stats.wp.com/e-202104.js and it’s missing from both sites. That would explain why we’re not recording stats – the thing we use to track and send the statistical data is missing.

Since the Stats module is active on both sites, it could be a problem with your theme, a conflicting plugin, or misbehaving advertising code. Based on our data on our end, the problem started on or around January 20th.

If you had a theme update on that day (since you’re using the same theme on both sites) check to make sure it still has the wp_footer() function in the footer.php file as that’s what we use to insert the stats javascript.

I hope that clarifies things. Let us know if you still have trouble after reviewing things and we’ll be happy to take a closer look.

@losteineu All statistics tracking plugins collect and report information differently. For example, Jetpack’s stats do not include the visits from logged in users, by default. Many bloggers find this very useful, since your own visits may artificially inflate your traffic counts. If you’d like to count visits from logged-in users on your site, you can modify that setting under Jetpack > Settings > Traffic tab > Site Stats. That might be one explanation for the variance between your other tracking plugin and Jetpack’s.

Jetpack also does not report visits in real-time; there is a bit of a lag between when visits occur, and when they are reported in your stats. Additionally, there are certain search engine robots and spiders that Jetpack doesn’t count, and referrers that are considered spam referrers by Akismet (our spam-catcher) will not be reported in your stats. Other tracking plugins may be less discerning in what they count toward the stats they report to you, and therefore give you greater numbers.

Since all plugins use different tracking methods, they will rarely, if ever, be perfectly synced in what they report. The benefit of using Jetpack’s stats is that you can see a snapshot of your blog’s activity right from your Dashboard. If you want to use another analytics service that gives you different features, you certainly can! Jetpack’s stats work great alongside Google Analytics and other stats tracking services. You may find it worthwhile to use tracking data from a variety of plugins to develop a broad picture your visitors’ behavior.

I do see that you’re using WP Rocket – so it’s possible it’s caching is preventing our stats tracking javascript from working properly? Check those settings to see if you can exclude our stats javascript (https://stats.wp.com/e-202104.js) and see if that has any impact.

Let us know if you have any questions or need help with anything else.

If Jetpack is deactivated and deleted, then we’re not adding that to your site. However, other plugins like WooCommerce will prompt you to install and connect Jetpack to fully activate features in their plugin.

If you have WooCommerce installed and want to remove that notice, post a new support thread in their forum and they should be able to advise how you can do that:

https://wordpress.org/support/plugin/woocommerce/#new-topic-0

If you don’t use WooCommerce, check your other installed plugins and disable them one by one until you see the notice disappear – then you’ll know what plugin is adding the notice and you can reach out to their support for help.

Since this isn’t a Jetpack issue, per se, we’ll mark this resolved for now.

@fedata While the WooCommerce app uses Jetpack’s connection for various features, you would need to reach out to WooCommerce support for help with their app.

You can open a new thread on their forum here:

https://wordpress.org/support/plugin/woocommerce/#new-topic-0

Since this is a WooCommerce issue, we’ll mark this resolved for now.

How do I switch to the Image CDN that is built into Jetpack? Is that a free feature and how will it work with my image that is in each of my blogs to ensure Twitter won’t block it?

You would find those settings under Jetpack -> Settings -> Performance tab under the “Performance & speed” section – turn on the “speed up images” filter. This feature used to be called “Photon”, so it’s been in use for a long time and is fully compatible with Twitter’s crawler bot.

Is it ok to still leave that section of code in code snippets in…you never explained what that is actually doing when activated?

I assumed since you had found and implemented it that I didn’t think that you needed to know what it was for. It’s not going to hurt anything by being activated, so it’s up to you whether or not you keep it.

Since the problem was stemming from the secureserverCDN and that it’s working for you now that it’s disabled, we’ll mark this resolved for now.

@deivuh Could you contact us so we can run some tests with you to try to figure out what’s happening?

Contact us via this contact form and mention this thread. We’ll continue helping you over email.