Careful information is important for decision-making. Google Analytics can provide that information, but it may need some decontamination. Google Analytics filters can remove data pollution, for example:
- Development or other internal (employee) traffic,
- Inconsistent activation of URLs, titles, events, campaigns and the like,
- Multiple websites or host names appear in a single Analytics property.
In this post I introduce Google Analytics filters.
Create a filter
Access filter on the Google Analytics Admin tab at the "Account" or "View" level. (A "View" is a subset of an "Property" account that may have its own configuration settings for specific users or reporting.)
Administrator> Account> All filters lists all filters for all views. You can add, remove or create new filters in any view.
On Administrator> View> Filters, you can create a filter or add an existing filter. I will use the View settings for the examples in this post.
Google Analytics does not include standard filters. Thus, no filters are displayed unless you add them.
IP excludes filters excludes specific IP addresses or ranges, usually to block employee traffic reporting. Use descriptive names for this filter (such as "Exclude Office Traffic" or "Exclude My Home IP Address") instead of repeating the IP address as the name.
"Include" filter allow in reports only traffic from specific host names, geographic locations, campaigns, and other traffic.
Large and small filters clean up your inconsistent case in events, pages, campaigns and more. Small filters are more common than capital letters.
Search and replace filters and advanced filters change field values. A typical example adds the hostname to the request URI (ie the web page), which can be helpful when a company has multiple websites and subdomains that visitors can access in a single session.
The settings for an advanced filter are:
- Filter. Advanced
- Field A. Extract A: Hostname = (. *) (. *) Characters capture everything.
- Field B. Extract B: Request URI = (. *)
- Exit to. Designer: Request URI = $ A1 $ B1. This means that the two fields will be combined.
Make sure the "Field A Required" and "Override Output Fields" boxes are checked and the others are not checked. This means that the host name must exist and that the Request URI field will be overwritten with the combined host name and Request URI.
Check your filters as soon as possible to ensure they work as intended, to minimize the impact on reporting if something went wrong. There are several ways to do this.
In the filter itself. Some filters let you see how the information will change reporting.
Test the same settings in your reports. If you include only one specific hostname, you can apply the same filter to your hostname report on Audience> Technology> Network, then click on the "Hostname" tab between the chart and the table on the page.
Adjust the filter settings according to the setting after the display level setting.
For example, if you used "equal" in the filtering level at the display level, use the same setting when verifying your reports.
Real-time reports. In Realtime reports, confirm that the filters are working correctly. Some filters, such as "Case Event Letters," are easier to confirm than others. If you see incorrect events occurring in real time, go through your filter.
Subsequent reports, like later in the day or the next day.
The order filtered for a view affects the data. Generally place filters in this order:
- Include / exclude filters.
- Search and replace filters or advanced filters.
- Lowercase and lowercase letters.
The sequence above simplifies the process and allows the filters to apply as much raw data as possible. For example, there is no reason to write a host name that you will still filter out.
You can change the filter order by clicking the "Assign filter order" button.
Looks "About View filters"In Google's" Analytics Help "for more resources.