For sites being tested by automated UI testing frameworks like Selenium WebDriver or Watir, developers may find it useful to exclude internal automated testing traffic from Google Analytics.
However, first things first, before talking about how to exclude such traffic, the question would be "why such traffic exists?". If such traffic comes from unknown sources, i.e. some people are running Selenium WebDriver against the website, then there isn't much can be done, unless the IP/ISP or User Agent can be uniquely identified. If such traffic is from site developers' own Selenium WebDriver tests, then the question becomes "Why Selenium tests were run against production"? Normally production servers only require some manual exploratory/smoke testing, instead of intensive automated testing to mess around live databases and slow down the servers.
In this case, when Selenium is used only against testing environment, it would be relatively easy to exclude its traffic. One approach would be using a different Google Analytics token from production, so the analytics data get separated out. Another solution is to avoid executing Google Analytics snippet if the site is deployed on testing servers.
Anyway, if it is really necessary to use Selenium against production for some reason, Here are few solutions which might help exclude internal traffic from Google Analytics. Some of these are just general approaches for excluding certain traffic from Google Analytics side, while some may involve updating Selenium test code explicitly.
- General solutions
- Selenium specific solutions
A custom filter on certain IP address/range or ISP can be created in order to filter out internal traffic. See Google Analytics official documentation's 'Exclude internal traffic' section for details.
- Go to the
ADMINSection of Google Analytics and select one website view from your account.
- Click button
Create new filterand give it a new filter name.
- Choose filter type:
- Choose "IP Address" from
Filter Fieldand type in IP Address Range in
- Apply this filter to the views you want to filter. For example, if the single IP address is 188.8.131.52, then enter
176\.168\.1\.1. If the range of IP addresses is 184.108.40.206-15 and 10.0.0.1-14, then enter
However, this may also filter out data that are not generated by Selenium WebDriver. On the other hand, if the tests are run on distributed CI systems or environment with dynamic IP, maintaining those IP addresses in Google Analytics setting might be too much of a hassle.
Edit hosts file
Without changing Google Analytics settings from data-receiving end, one other direction is to block GA's traffic being sent to its server. To achieve it, editing hosts file on the machines where the tests are run would be a straightforward thing to do. It requires certain permissions on testing environment, and will block all traffic for all sites to Google Analytics, hence this might not be as good as it sounds.
For more details about how to exclude Google Analytics by editing hosts file, here are few posts explaining the same thing:
- Blocking Google Analytics and Statcounter
- How to block google-analytics
- Block Google Analytics
- How to block your browser from sending information to Google Analytics
Selenium specific solutions
Set custom user agents
As most of the browsers' user agents can be set through Selenium, wrap site's Google Analytics' snippet with an if-statement to ignore some certain user agents would be another possible approach to deal with it.
For example, Google Analytics snippet will only be executed if browser's user agent doesn't contain "phantomjs".
If the testing is done using browsers like Chrome or Firefox, an additional step is needed to set a special testing user agent when starting browsers using Selenium WebDriver. A previous article Set user agent using Selenium WebDriver C# and Ruby provides few sample snippets on how to set user agents. Note that user agent can't be set for IE using Selenium WebDriver, therefore this approach is not going to work for IE1.
Here, Firefox for example, add something identifiable (e.g "Selenium") into the user agent when launching, then wrap Google Analytics's tracking code with if-statement to ignore any user agents that contain word "Selenium" like above.
Officially, Google provides browser add-ons to opt-out Google Analytics. With this plugin installed in the browser, no Google Analytics data will be collected and used by Google. It supports IE 11, Chrome, Firefox, Safari and Opera, which unfortunately, means that this won't work for PhantomJS. Additionally, Selenium WebDriver cannot start IE with custom add-ons installed2, therefore this won't work for IE unless pre-install manually.
The Chrome extension can be found within Chrome Store here and downloaded using third party sites like Chrome Extension Downloader. Save it somewhere locally and start Chrome using the following Selenium WebDriver code.
In order to start Firefox with this add-on installed, first download and save the latest version of Google Analytics Opt-out Add-on here, then use the following code to start Firefox.
Use a proxy
BrowserMob Proxy allows manipulating HTTP requests and responses, capturing HTTP content, and exporting performance data as a HAR file. It supports blacklisting which can be used as a way of blocking data sent to Google Analytics.
Below is a simple example of how it's done using the Ruby client for the BrowserMob Proxy.
|Solution||GA Admin||Server||Source code||Testing code||Pros||Cons|
|Exclude IP/ISP||✔||- Straightforward |
- No code changes
|- High maintaining costs for environment using dynamic IP |
- May exclude traffic other than Selenium
|Edit hosts||✔||- No code changes||- Need permissions to setup on testing environment |
- May exclude traffic other than Selenium
|- Make Selenium WebDriver barely usable |
- Only support few browsers
|Use special UA||✔||✔||- Accurate |
|- Source code changes required |
- Need to set a custom user agent in Selenium code
- Not possible for IE
|Opt-out plugins||✔||- Accurate |
|- Need to load plugins in Selenium code |
- Only possible for Chrome and Firefox
|Use a proxy||✔||- Accurate |
- Regardless of browser types
|- Need third party libraries |
- Need to setup together with Selenium