Monitoring FAQs

In general, Conductor Monitoring’s monitoring doesn’t have any effect on your analytics data. However, there are certain edge-case scenarios in which Conductor Monitoring can impact the data.

These scenarios also depend on the monitoring configuration you are using in Conductor Monitoring, namely on the JavaScript Rendering feature.

Effect on web analytics when JavaScript rendering is disabled.

If you're using a JavaScript-based web analytics solution such as Google Analytics, Conductor Monitoring won't affect your analytics data.

Conductor Monitoring may inflate your web analytics data in one situation only: when you're using a server-side web analytics solution.

In this case you should prevent our crawlers from being tracked by excluding our crawlers' IP addresses.

Effect on web analytics when JavaScript rendering is enabled.

When monitoring a website with JavaScript Rendering enabled, Conductor Monitoring blocks requests to the most common web analytics and ad services to ensure that your web analytics data don’t get inflated by Conductor Monitoring’s monitoring.

This means that if you’re using a common JavaScript-based web analytics solution such as Google Analytics or Adobe Analytics, Conductor Monitoring’s monitoring does not have any effect on your web analytics data and you can safely enable the feature without any concerns.

If you’re using a non-standard web analytics solution and you want to ensure that Conductor Monitoring’s monitoring doesn’t affect your analytics data, make sure to configure custom on-page request blocking in Conductor Monitoring.

More about how to set up the blocking you can find here: Custom on-page request blocking

Although we strongly recommend against doing this it is possible to limit monitoring to specific sections of your website. The reason why we don't recommend doing this is that you create a blind spot for yourself, and tests that rely on multiple data points (such as auditing for broken links or duplicate-content issues) will have limited reliability.

We do understand that not every page may be equally important to the success of your business, but we've learned from experience that serious issues do occur in pages initially deemed to be "uninteresting," and these issues may in turn hurt the entire website's SEO performance.

To support the concept of having your entire monitored, we have made our pricing model as fair and flexible as possible: you only pay for pages (not for errors, redirects, etc.), and the more pages you monitor, the lower the price per page.

Having said all of this, if you still want to continue with monitoring only parts of your website, you can do this through the "URL Exclusion List". See this Support article on how to set this up: How can I exclude certain parts of my website from monitoring?

You can pause (and resume) monitoring through the website's monitoring speed settings. See our article on monitoring speed to learn how to do that.

Keep in mind that when monitoring is paused, your subscription remains active (you are still charged), but no changes will be detected and no alerts will be sent out.

We monitor websites from the following IP address subnets:

• 89.149.192.96/27
• 81.17.55.192/27
• 23.105.12.64/27
• 173.234.16.0/28