Bill is a developer and he loves to test the development version of the website on his development platform(localhost) which he should because that’s a sign of a good developer.
But Bill is testing the development version of the website with Analytics implemented on it.
“Oh noo!” says the marketing team! Bill is just trying to do his job, but by testing the website Bill is affecting the data shown in analytics.
In the analytics report, some of the users have localhost:XXXX as the source, but no one knows who this user is.
So how can Bill do his job without having to worry about sending data to analytics you ask?
Add this filter to your view and tada, problem solved!!
Want more quick tips that will help you make the most of Google Analytics? Connect with us on Facebook and you’ll be notified of all the newest content!