Dashboard
Filters and saved segments
Narrow every number on a screen to one page, source, country or device, combine several filters, and save a set of them as a segment.
This page shows how to narrow the dashboard to part of your traffic, such as visitors from one country, and how to keep a set of filters under a name so you can come back to it in one click.
Filter by clicking a row #
The fastest way to filter is to click. On the Overview, click a row of a breakdown card, such as a page, a referrer, a country or a browser, and the whole screen changes to the visits that match.
Places depend on each other. Clicking a region also sets its country, and clicking a city sets its country and, when it is known, its region. Removing the country removes the region and the city with it.
Filters carry over when you move to another screen of the same site. A screen that cannot apply one of your filters still shows its chip, with a dashed outline and the hint "Not applied on this page". Realtime and Revenue take no filters at all.
The filter chips #
Each active filter is a chip in the filter row at the top of the screen. A chip reads like a sentence: "Country is" followed by the name of the country.
- Remove a chip with its remove button, or press Backspace or Delete while the chip has keyboard focus.
- With more than one chip, Clear all removes every filter at once.
- Where a filter can be turned around, the word "is" on the chip is a button. Click it to change "is" into "is not", and again to change it back.
Add a filter by hand #
The Add filter control at the end of the chips lets you build a filter without a row to click. Choose what to filter on, choose how, then pick or type the value. It is the only way to add a "contains" filter.
There are three ways a filter can match:
- is: the value matches exactly. For a page you may end the value with
*to match every page that starts with the text before the star. - is not: everything except that value. Visits where the value is unknown are kept. For a page or a hostname, "is not" leaves out the views of that page or hostname, and a visit that also saw other pages still counts through them.
- contains: the text appears anywhere in the value. Upper and lower case are treated the same.
Not every filter takes every one of these. The key is the name the filter has in the address of the page and in the API.
| Filter | Key | Is not | Contains |
|---|---|---|---|
| Page | path |
Yes | Yes |
| Entry page | entry |
Yes | Yes |
| Exit page | exit |
Yes | Yes |
| Hostname | hostname |
Yes | Yes |
| Referrer | ref |
Yes | Yes |
| Channel | channel |
Yes | No |
| AI tool | ai |
Yes | No |
| Country | country |
Yes | No |
| Region | region |
Yes | No |
| City | city |
Yes | Yes |
| Browser | browser |
Yes | Yes |
| OS | os |
Yes | Yes |
| Device | device |
Yes | No |
| Source | utm_source |
Yes | Yes |
| Medium | utm_medium |
Yes | Yes |
| Campaign | utm_campaign |
Yes | Yes |
| Term | utm_term |
Yes | Yes |
| Content | utm_content |
Yes | Yes |
| Conversion | conversion |
No | No |
| Event | event |
No | No |
| Property | prop |
No | No |
A few of them work differently from the rest:
- Conversion, Event and Property only take "is", and each has a control of its own. The conversion is set with the Conversion selector in the top bar of the Overview. The event and the property are set on the Events screen.
- Region is set by clicking a row of the Regions tab, because its value is a code and not a name you could type.
- City is offered in the Add filter control only while a country is set.
How filters combine #
All filters apply together: a visit must match every one of them. There is no way to say "this or that" between two filters.
One screen takes at most 10 filters, and at most 3 of them may be "contains" filters. The Add filter control tells you when the limit is reached. A link that carries more than that is still opened, with the extra filters left out.
Detailed visit data is kept for 3 years, so a filtered view cannot reach further back than that.
Share a filtered view #
Filters live in the address of the page, next to the date range. So the back button of your browser undoes the last filter, and anyone with access to the site who opens the address you copied sees the view you were looking at.
Filters also work on a shared dashboard and on the public demo.
Saved segments #
A segment is a set of filters with a name, for example your paid traffic from one country. It holds no date range. Segments belong to one site and cannot be shared across all sites of a workspace.
The Segments menu sits at the end of the filter row.
- Apply a segment. Open the menu and choose one. Its filters replace the ones on the screen. The segment whose filters are exactly the ones on screen is the checked one.
- Save one. Set the filters you want, open the menu and choose "Save current filters as segment". Give it a name of up to 60 characters. Two segments of a site cannot share a name, and upper and lower case do not make a name different.
- Rename or delete. "Rename or delete segments" in the same menu opens the list. A change there applies for everyone who can see the site. Deleting a segment touches no visitor data, and links that carry the same filters keep working.
A site holds up to 30 segments.
Owners and Admins can save, rename and delete segments. A Viewer can apply the segments of the sites they were given, and so can a visitor of the public demo. A shared dashboard has no Segments menu.
A saved filter can stop working, for example when it names a conversion goal that was since renamed or switched off. That one filter is then dropped from the segment and the rest still apply.
Filters and segments through the API #
Every report of the API takes the same filters, under the keys in the table above. A plain key means "is", a key ending in .not means "is not" and a key ending in .has means "contains". The filters section of the API reference lists every key with its rule. The API is stricter than the dashboard about the limits: a request with too many filters is refused instead of being trimmed.
Segments can be listed, saved, changed and deleted through the API as well. Reading them needs a token with the Read permission, and changing them needs the Write permission. See the segment operations.