Analytics filters

filters let you narrow down your widget and campaign reports to a specific segment of traffic, location, acquisition source, or goal criteria you can combine multiple filters to isolate exactly the data you need most filters are available on the advanced analytics plan visitor type and device filters are available on all plans how to use filters click the filter button above any report table or chart select a filter from the list, choose an operator, and enter or select a value active filters appear as pills above the report click the x on a pill to remove it you can stack multiple filters; they are combined with and logic, meaning all conditions must be true for a record to be included how filters are structured filters are organized into four groups based on what part of the data they operate on traffic filters apply to the widget or campaign event itself — the record created when a visitor sees, clicks, or converts on a widget or campaign properties like device type, browser, and operating system are captured at the moment the event is recorded location filters also apply to the widget or campaign event the visitor's country, region, and city are resolved from their ip address when the event is recorded acquisition filters apply to the visitor record utm parameters, referrer, and first visit page are stored once when the visitor first arrives on your site and remain constant across all of that visitor's events goal filters apply to the goal event (e g , a purchase, add to cart, or custom event) these filters narrow down which goal events are counted and summed in revenue related metrics they do not affect view, click, submit, or conversion counts on widgets and campaigns traffic filters these filters operate on properties captured on each widget or campaign event visitor type — segment by new or returning visitors a visitor is considered "returning" if their first visit timestamp is earlier than the current session, meaning they have visited your site before this is determined by comparing the visitor's first seen date to the event timestamp device — filter by the device type that was used during the event desktop, mobile, or tablet you can select multiple values location filters these filters operate on the geographic properties recorded on each widget or campaign event, resolved from the visitor's ip address at the time the event occurred country — filter by one or more countries uses the two letter iso country code (e g , us, de, fr) region — filter by one or more regions (states, provinces, or administrative divisions) within countries city — filter by one or more cities acquisition filters these filters operate on properties stored on the visitor record they reflect how the visitor originally arrived at your site, not how they arrived for a specific event all acquisition filters require the advanced analytics plan all acquisition filters (except referrer and first visit page) support the following string operators contains, equals, starts with, does not contain, does not equal, and is empty utm source — filter by the utm source parameter captured on the visitor (e g , google, facebook) utm medium — filter by the utm medium parameter (e g , cpc, email) utm campaign — filter by the utm campaign parameter (e g , summer sale) utm content — filter by the utm content parameter (e g , banner 1) utm term — filter by the utm term parameter (e g , running shoes) referrer — filter by the referring domain or url stored on the visitor record (e g , google com) supports the same string operators as utm filters first visit page — filter by the landing page path stored on the visitor record (e g , /products/my product) this is the first page the visitor saw when they arrived on your site supports the same string operators as utm filters goal filters these filters operate on the goal event record — the event created when a visitor completes a tracked action such as a purchase, add to cart, checkout start, or custom goal goal filters affect which goal events are included when calculating revenue related metrics (goals hit, revenue, extra value, profit) they do not affect widget or campaign event counts like views, clicks, submits, or conversions goal products — filter goal events by specific products mentioned in the event metadata for purchase and checkout start events, product ids are extracted from the order line items for add to cart events, the product id is extracted directly from the event metadata only available when your platform integration supports product data (e g , shopify, wix, shoplazza) select one or more products to see only goals that involve those products goal revenue — filter goal events by their monetary value (the value field on the goal event) supports operators greater than, less than, equals, and between enter values in your store currency for example, "greater than 10" will exclude any goal event worth $10 or less z score threshold — exclude statistical outlier orders from revenue metrics enter a numeric threshold (e g , 3) and any goal event whose revenue z score meets or exceeds that value will be excluded from the report events that do not yet have a z score assigned are always included this filter only affects revenue related aggregations (revenue, extra value, profit); goal counts and conversion rates are not affected understanding the z score filter a z score measures how many standard deviations an individual goal event's revenue is from the average revenue for that event type for example, if the average purchase is $50 with a standard deviation of $20, a $200 purchase has a z score of 7 5 — it is 7 5 standard deviations above the mean setting a z score threshold of 3 tells the report to exclude any goal event with a z score of 3 or higher, removing unusually large (or small) orders that can skew your revenue metrics how z scores are calculated z scores are scoped by event type purchases are compared to other purchases, add to cart events to other add to cart events, and so on a $500 purchase and a $500 add to cart will have different z scores because they are measured against different distributions the z score is calculated asynchronously after a goal event with a value is created the formula is z score = (event value mean) / standard deviation, where the mean and standard deviation are computed across all events of the same type in your store a minimum of 750 events of a given type is required before z scores are assigned until that threshold is reached, events have no z score and are always included in reports regardless of the filter setting this ensures the statistical distribution is meaningful before outlier detection begins the filter does not remove events from the report entirely it excludes them only from the goal event join, so widget and campaign event counts (views, clicks, conversions) remain unchanged only the aggregated goal metrics (goals hit, revenue, extra value, profit) are affected choosing a threshold 3 is a common starting point in a normal distribution, roughly 0 3% of values fall beyond 3 standard deviations, so this excludes only extreme outliers 2 is more aggressive and will exclude more orders (roughly 4 6% of values in a normal distribution) 4 or higher is more permissive and will only exclude the most extreme cases faq do filters affect the "winner" suggestion in experiments? yes statistical comparisons and winner logic use the filtered data set, so adding filters can change significance results can i save a filter combination? not yet filters are applied per session when you share a report url, active filters are encoded in the url so the recipient sees the same view why is a filter grayed out? filters marked with a plan badge require the advanced analytics feature upgrade your plan to unlock them what happens if i combine goal revenue and z score threshold filters? both conditions apply for example, "goal revenue greater than $10" combined with "z score threshold less than 3" will show only goal events with revenue above $10 that are also not statistical outliers do acquisition filters reflect the current visit or the first visit? acquisition filters (utm parameters, referrer, first visit page) are based on the visitor record, which stores the values from the visitor's first arrival they do not change if the visitor returns via a different source later why does the z score filter show no effect on my data? if your store has fewer than 750 events of a given type (e g , fewer than 750 purchases), z scores have not been assigned yet and all events are included once the threshold is reached, z scores are calculated for new events automatically does the z score filter affect conversion counts? no conversion counts (the converted flag on widget events) are pre computed and independent of the goal event join the z score filter only affects goal related aggregations goals hit, revenue, extra value, and profit