Filters

Combining Filters

You can filter by page, source, channel, UTM source, UTM medium, UTM campaign, country, device, browser and operating system. Each field holds one condition and a list of values.

• Different fields are combined with AND. Page is /pricing and Device is Mobile keeps only mobile pageviews of /pricing.
• Values within one field are combined with OR. Page is /pricing, /signup keeps a pageview of either page: it matches any one of the values.
• A negative condition excludes every listed value. Page is not /pricing, /signup keeps a pageview of neither page.
• Filters live in the address, one parameter per field (?page=/pricing,/signup&device=mobile), so a filtered view can be bookmarked or shared. A prefix sets the condition: none for is, ! for is not, ~ for contains, !~ for does not contain.

Is, Is Not, Contains, Does Not Contain

• is matches the value exactly as the matching dashboard tab shows it. Page paths are case-sensitive; every other field ignores case, and UTM values also ignore surrounding spaces.
• contains matches when the value appears anywhere in it. A contains value needs at least 2 characters, and a field takes up to 5 of them (up to 20 values for is / is not). A 2-letter country value is read as a country code; a longer one as part of a country name.
• is not and does not contain keep everything the positive condition would not. Pageviews with no recorded value are kept too, unless the value you exclude is the one they show as, such as (direct) or not-recorded.
• The filter panel suggests values from the rows already loaded for that field; you can type any other value. Unknown fields, empty lists and values over the limits are ignored.

What a Filter Changes

A filter selects matching pageviews. Some numbers count those pageviews only; session numbers count every pageview of a visit that included one.

• Pageviews, unique visitors, the chart and every breakdown tab count only the pageviews that match every filter, in the current and the comparison period.
• Sessions, bounce rate, avg. visit and new vs returning read whole sessions: a session is included when at least one of its pageviews matches, and then all of its pageviews count. The bounce rate denominator becomes the sessions that included a match, not all sessions. A visit that landed on /pricing and went on to /signup is not a bounce under Page is /pricing, although only one of its pageviews matches.
• Custom events count when their session has a matching pageview. A page filter also applies to the event's own page.
• Goals follow every filter. A page filter narrows conversions by the page they happened on; any other filter keeps the conversions of the sessions that match it. The conversion rate is conversions ÷ pageviews, and the pageviews carry the same filters as the conversions. Conversions recorded before filters were supported have no session, so a filter other than page leaves them out.
• Imported history has one breakdown per field and no combinations, so it follows a filter on one field only. With two or more fields filtered, only data Klar collected itself is counted.

Example: visitor A views /a1 then /a2, visitor B views /b1. With no filter, 3 pageviews, 2 sessions, bounce rate 50%. With Page is /a1: 1 pageview and 1 visitor, and the bounce rate is 0%, because A's session included /a1 and had two pageviews. With Page is /a1, /b1: 2 pageviews, 2 visitors, bounce rate 50%. With Page is /a1 and Device is Mobile, when only B was on a phone: nothing matches.