Effect on web analytics data

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

These scenarios also depend on the monitoring configuration you are using in Conductor Website 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 Website Monitoring won't affect your analytics data.

Conductor Website 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 Website 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 Website 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 Website 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 Website Monitoring’s monitoring doesn’t affect your analytics data, make sure to configure custom on-page request blocking in Conductor Website Monitoring.

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

Need help?

If you have any questions that are not covered by our documentation, don’t hesitate to contact us, we will be happy to help!