Discovering an unexpected usage spike in your Analytics can be puzzling and raise questions about its origin and cause. When you observe a significant increase in usage metrics without corresponding help items in your statistics, it can add to the mystery and confusion. In many cases, such spikes can be attributed to unintentional actions, such as the inadvertent creation of an auto-load help item that appeared for all users. This support article delves into the common scenario of encountering usage spikes in Analytics and explores potential causes, focusing on the possibility of unintentional actions by team members leading to the spike. By understanding how such situations can arise, administrators can effectively troubleshoot and address usage spikes to maintain clarity and accuracy in their analytics data.
You may be browsing through your Analytics one day and unexpectedly notice a usage spike. Something like this:
To add to the mystery, when you look at your Clicks by Help item statistics, you can't find the corresponding help item(s) to account for the usage spike.
The most likely reason is someone on your team created an auto-load help item that unintentionally was appearing for everyone. As this was un-intended, in a panic, the help item was deleted, which is why you don't see the help item in the Clicks by Help item statistics.