Uptime.com sends server requests to your website as part of the monitoring that we do. These requests can cause some issues with your site’s analytics, inflating traffic numbers or otherwise obscuring traffic statistics. To avoid this issue, you can take one of two steps to filter traffic from Uptime.com monitors without affecting the checks themselves.
Method One: Filter Check Data From Google Analytics
For this method, you need to access the list of Uptime.com probe servers (Support>Probe Servers). Use Download CSV to acquire a list of all of the IP addresses, then visit your Google Analytics Account. Google has detailed instructions on adding a filter to Google Analytics. Add a Predefined filter that Excludes by IP Address.
Use the IP addresses from the CSV you downloaded from Uptime.com to fill in these values. Google suggests using more than one filter to exclude multiple IP addresses. You can exclude each probe server if you are using monitoring from around the globe. Otherwise, only exclude the servers that correspond with locations you are actively monitoring.
Method Two: Filter by User in Your Database
Uptime.com Transaction Checks typically use the same username or ID as they run through their steps. A Transaction Check can purchase items the same way a user can, so this data will expand overtime causing some issues with reporting. For example, it could create an “out of stock” warning or create data suggesting conversions were higher than they are.
This method uses a schedule to delete any data this user agent generates. (NOTE: we recommend storing the user agent ID and using this ID as a filter where possible).
Simply create a job that deletes all data the Uptime.com user creates, and schedule it to run once per day.