![\"\"](\"http:\/\/www.dpscomputing.com\/blog\/wp-content\/uploads\/2013\/06\/wordpressjetpack.png\")
<\/a><\/p>\nJetPack<\/a>, a feature packed and ever expanding and updating set of features for the worlds most popular blogging platform (indeed, this blog is powered by it as well!), has now become a mainstay of any self respecting WordPress<\/a> bloggers blog.<\/p>\n Even if you use none of the extra fancy features (which can be quite useful) its worth it alone just for the stats. \u00a0For those who have been blogging for quite a while now, you’ll remember the days that WordPress.com stats was a feature in itself, which was later merged into JetPack on its release.<\/p>\n Many people use the stats to track activity on their website, popular topics, posts, pages, times of day etc etc. \u00a0You name it, there’s probably a metric for it in the JetPack stats somewhere (and if there’s not, its pretty much assured to be in Google Analytics – which of course you’re all using as well aren’t you? \ud83d\ude09 ).<\/p>\n However, one thing that has particularly plagued JetPack since its inception has been the periodically and sometimes, apparently random, dumping of previous stats. \u00a0Many users log in, check there stats and to their horror they’re gone. \u00a0But what’s causing this?<\/p>\n Well there’s only one group of people that can definitively answer this, and thats the WordPress Devs. \u00a0However, due to nature of the beast that is WordPress and the many different scenarios a user can be in when there stats go bye-bye, its impossible for even them to determine one definite cause (as is to be expected).<\/p>\n However, with a lot of confidence I can safely say:<\/p>\n Indeed, it most definitely is caused by multiple different situations – probably 10s or even 100s. \u00a0However, the result of all these different situations is the same – the apparent removal of historical stats, or reset.<\/p>\n First culprit – JetPack updates. \u00a0Probably an obvious one for most of you but its possible on some occasions updating your JetPack has conspired with other events to rid you of your past statistical information. \u00a0However, to make it clear, updating JetPack doesn’t, as a matter of course, delete your stats – indeed many updates are performed and no stats are lost.<\/p>\n There are several possible reasons for this apparent indeterminacy of the problem. \u00a0Maybe you’ve reconnected to a different WordPress.com account that you have (i.e. the wrong one!). \u00a0Maybe you’ve logged on to your WordPress account and accidently (intentionally) deleted your previous stats? \u00a0Or maybe the server holding that data had a hiccup and its temporarily lost. \u00a0There are literally hundreds of reasons.<\/p>\n [adrotate banner=”45″]<\/p>\n Similar in nature to the JetPack updates above – maybe slightly more likely than the above reason but most of what’s said above applies to WordPress Updates as well.<\/p>\n As we say, many updates go without a hitch and updating WordPress, as a matter of course, shouldn’t rid you of your stats.<\/p>\n It’s good to note here that updating your WordPress (and indeed JetPack and any plugins) is essential to maintaining the security of your blog. \u00a0The small risk of losing your stats shouldn’t dissuade you at all from providing updates – security is paramount on the importance scale.<\/p>\n Maybe your WordPress.com account was hacked? \u00a0Maybe your blog was hacked? \u00a0Either way, both mechanisms could potentially allow an attacker to delete, reset or remove your stats.<\/p>\n Maybe WordPress are upgrading the server that your stats are held on? \u00a0Maybe its being maintenaned? \u00a0Maybe there’s a fault? \u00a0Maybe its failed? \u00a0All of these causes should thankfully be temporary and resolve without your intervention.<\/p>\n Maybe the above has happened \/ is happening to your own server? \u00a0If you’re on a managed hosting solution<\/a> then check with your host and see if they can offer assistance (and maybe an explanation).<\/p>\n Maybe there’s some for of communication problem between the server your site is hosted on and the WordPress.com server that your stats are on? \u00a0This isn’t as uncommon as you may think.<\/p>\n Maybe you’ve accidently installed some crap (yes, that is a technical term) onto your server. \u00a0Or maybe a hacker has. \u00a0Or maybe one of your users has accidently or otherwise exploited a loophole in your website somewhere. \u00a0This is probably on the lower end of the likeliness spectrum for this problem.<\/p>\nWhat’s Causing Stats To Do A Runner?<\/h2>\n
It’s not just one problem!<\/h3>\n
Some Likely Culprits…<\/h2>\n
JetPack Updates<\/h3>\n
WordPress Updates<\/h3>\n
Compromised Accounts (Hacking)<\/h3>\n
Temporary Server Faults \/ Failure \/ Maintenance \/ Downtime \/ Communication Errors<\/h3>\n
Malicious Software<\/h3>\n
Conclusion<\/h2>\n