Image you have Google Analytics running on your site or on a client’s site. If you are using your own website a lot (testing, for instance) or if you are often working on projects for clients, it would be a good idea to filter out that traffic from the Google Analytics data. Why? Because if you or your clients are relying on GA data to make decisions or to monitor trends it is important that the data actually reflects real world traffic. When we were launching the new Green Egg Media website about 10 days ago I was spending a lot of time navigating the site and testing every possible interaction. It wouldn’t really be appropriate to have Google Analytics track that usage. Likewise, we spend a lot of time fully testing our clients’ websites, and we don’t want to cloud their data with all of our traffic. So, what’s the solution? Google Analytics Filters.
If you have Admin access to your Google Analytics profiles, it is actually quite easy to filter out internal traffic. Here’s a quick guide.
1) If you don’t already know it, find your IP address by visiting whatismyip.com. Filtering by IP address works best when you have a static IP address. At Green Egg Media, all of our traffic is routed via a secure VPN so we know that we’ll always have the same IP address.
2) Login to Google Analytics and select the “Admin” option from the menu.
3) If you are managing multiple accounts, properties or views, you may have to select them from the Admin screen. Once you have selected the appropriate analytics profile, click the “Filters” link.
4) Click on “New Filter”
5) Create the new filter by giving it a name (“Internal Traffic” or “Client Traffic,” for instance) and select “exclude” “traffic from the IP addresses” “that are equal to,” entering the relevant IP address in the boxes provides. Then just click Save.
6) You’re done!
If you have multiple web properties that you want to apply the same filter to, you can do so using the “All Filters” link under the relevant GA account. You can follow the same steps as above to create a new filter, or you can select an existing one to apply it to other profiles in your GA account.
AWS Elastic Load Balancers communicate with EC2 instances over standard HTTP, which can cause issues when WordPress is setup to use SSL. A single line of code in wp-config.php can fix this problem.