IP Blocking and Filtering
How can I exclude internal traffic?
For most customers, internal traffic is such a small volume compared to their overall traffic that it does not have an impact on their conversion rates. Customers who do heavy internal QA testing usually prefer to set up a separate KISSmetrics site for their staging/development environment so that their testing activity is recorded under a separate KISSmetrics API key.
However, if there is a specific reason why your internal traffic needs to be ignored, we’d like to hear it. We’re always interested in hearing customer feedback that may tip us off to use cases we hadn’t anticipated.
Notes on the Alternatives
- There is no way to exclude certain data after the fact.
- The proposed alternatives prevent KISSmetrics from loading when the user is internal, thus their data never gets into our system.
- These are not 100% foolproof.
Option 1: Use AdBlock Plus (Easiest)
Open the AdBlock Plus preferences and add these two filter rules:
Remember to insert your API key into the second rule.
Option 2: Exclude known IP addresses
In other words, don’t even load the KISSmetrics JS for internal users. You could alternatively try this concept with any other “matching” criteria – i.e. “if username contains ‘mycompanyname.com’, do nothing, otherwise load the KISSmetrics JS”; however, that example would only work if your internal users were always logged in.
Option 3: Using Cookies
This assumes that you are able to create a new page on your server where you would set the cookie for your employees. It requires you to write some code. This also assumes that all of your employees will comply with getting cookied and do so for each browser that they regularly use.
Create the Cookie Page
You will need to create an HTML page and host it on your server in order to set a first-party cookie. The code for this page would work something like this:
<a onclick = set a cookie called km_ignore with an expiration of 10 years>Click here to set your cookie</a>
You would upload it to
http://www.mysitename.com/ignore-km.html (or something like that). Then your employees would need to visit the
http://www.mysitename.com/ignore-km.html page and click the link to set a cookie for each browser (Chrome, Firefox, IE, Safari, etc.) they regularly use.
Alter your KISSmetrics code
You would need to replace your default KISSmetrics JS code with something like this:
This basically says, “Check to see if this person has a cookie called km_ignore; if so, do nothing; if not go ahead and load the KISSmetrics script.”
This also assumes that your internal users are not clearing their cookies.
Option 4: Opt Out of Tracking