|
<< Click to Display Table of Contents >> Navigation: Reference > Predefined filters |
Professional edition only!
In the professional editions you get the following predefined filters as examples. You can customize them to get your own filters.
This filter excludes the bot traffic and displays only successful GET request. The IIS specific field Win32Status is required to be 0 to ensure that the page content was completely downloaded.
Same as the previous filter but without the Win32Status condition because this field doesn't exist on Apache.
Displays page views for which the RefererSite is not the web site itself meaning that it is the first .page view of the visitor on the web site. See the use case Display visits.
The Referer field is required in the logs. The Host field is also required but if missing from the logs you can add the web site host name in the profile configuration.
Same as the previous filter but without the Win32Status condition because this field doesn't exist on Apache.
Page views with a RefererSite that comes from Google (www.google.*)
Same as previous but excluding requests with the Google auto tagging field gclid.
You need to use the auto tagging in your Google Ad campaigns and you need to enable the extraction of the gclid in a new field.
The contrary of the previous filter. Only landings from Google Ads are displayed (with a gclid).
Only web requests that downloaded less than 1 MB are displayed. The ByteSent field is required. Can be used to monitor web server performance.
Only web requests that downloaded more than 1 MB are displayed. Same requirements as the previous filter.
Display small pages request that took more than 1 s second to execute. The TimeTaken field is also required. This field doesn't exist in Apache by default. See this blog article to know how to add it. Also see the use case Monitor web site performance
Displays requests with a 404 status (Not found) and for which the RefererSite is the web site itself and the Referer is not the page itself (a not existing web page cannot link to itself). The second condition may look strange but it allows to remove 404 requests generated by bots that send a fake referer to the web server.
Displays web requests done by the Google bot based on the user agent and validated by the domain of the client IP address host name. The setting Resolve the host name of the client IP address needs to be enabled. Also see the use case Analyze the bot traffic.
Same as the previous filter but for the Bing bot.