# Filters, date ranges and saved views

> The date bar and the filter builder choose which events a page uses. Saved filters, funnels, flows and retention questions let you ask them again.

> **In short**
>
> - A filter tests each condition against one event at a time. Values match exactly.
> - Days run midnight to midnight UTC. Every page includes the whole To day.
> - Saved filters, funnels, flows and retention questions belong to the project. Everyone in the project sees them. Viewers can only apply them.
> - You can share some views as a link. The link does not carry the project.

## What it is for

Events, Sessions, Users, Funnels, Flows and Retention share two controls: a date bar and a filter builder.

## How a filter matches

A filter is a set of conditions. Each condition is one field and one value.

- **Field conditions match exactly.** A condition on a field, such as **Browser** or **URL**, matches one whole value. From 12 October 2026, **OS** ignores upper and lower case: `Android` also matches `android`. **Event Property**, **Visitor Property** and **Account Property** conditions have more operators. See **Property conditions** below.
- **Conditions apply to the same event.** **Event Type** = `click` AND **URL** = your pricing page means clicks on the pricing page. For "did A, then B", use [Funnels](/docs/funnels). On **Sessions**, this is true only inside one row. See **What the filter does on each page** below.
- **A NOT group also drops events with no value in the field it tests.** See **NOT groups** below.
- **Sequential ignores a condition with no value.** A property condition needs a name. It also needs a value, unless its operator is **is set**, **is not set**, **is true** or **is false**.

## Property conditions

**Event Property**, **Visitor Property** and **Account Property** conditions have a type and an operator. Choose the type first.

| Type | Operators |
|---|---|
| **Text** | is, is not, is one of, is not one of, contains, does not contain, starts with, ends with, matches regex, is set, is not set |
| **Number** | is, is not, >, ≥, <, ≤, is between, is one of, is not one of, is set, is not set |
| **True / false** | is true, is false, is set, is not set |
| **Date** | >, <, is between, in the last, is, is not, is set, is not set |

- **is** on **Text** matches the exact text of the whole value. **contains**, **starts with** and **ends with** ignore upper and lower case.
- For **is one of** and **is not one of**, type the values with commas between them. For **is between**, type the low value, a comma and the high value. Both values count as a match. For **in the last**, type a number of days.
- **Number** also matches a number that your SDK sent as text, such as "9.99". **Date** also matches text that starts with a date, such as `2026-10-09`. **True / false** also matches the text `true` or `false`.
- **is not**, **is not one of**, **does not contain** and **is not set** also match events that do not have the property. The condition says "also events without it". The other operators never match an event without the property.
- `$utm_source`, `$utm_medium`, `$utm_campaign`, `$utm_term` and `$utm_content` are the campaign tags of the page address. `$release` is the release of the event. These event properties take **Text** operators only. **is not set** finds the events without the tag or the release. When your project has a value for them in the last 30 days, the **Property name** menu lists these names first, and **Property value** suggests their values. To group by them, see [Group by a property](/docs/events-explorer).
- A filter can have up to 25 property conditions. Only one of them can be **matches regex**, with a pattern of up to 256 bytes. **is one of** takes up to 1,000 values. A property name has up to 128 bytes. **in the last** takes 1 to 3,650 days. Sequential refuses a filter over a limit and runs nothing.
- If Sequential cannot read a **matches regex** pattern, it refuses the filter with "A regex pattern in the filter is not valid".
- On **Sessions** only, the field **Session Property** tests one value of each session: the first or the last value of an event property in the date range. For the entry or exit page, choose **Page ($page)** in **Property name**, then **Entry page** or **Exit page**, an operator and a page path, for example `/pricing`. Only page views count for **Page**. If the date range ends while a session continues, its exit page can be a page in the middle of the session. For any other property, the choice reads **First in session** or **Last in session**. A Session Property condition takes **Text** operators only. **is not**, **is not one of**, **does not contain** and **is not set** also match sessions without the value: the condition says "also sessions without it".
- Agents can use the same property conditions in the filters of the analytics tools, except **Session Property**. They cannot use an identity property, such as `email`. On an element-text property, such as `$el_text`, they can use only **is set** and **is not set**.

## Build a filter

1. Open **Events**, **Sessions** or **Users**.
2. On Sessions or Users, click **+ Add filter** in the toolbar. If the filter already has conditions, click **Edit filters**, then **+ Condition**. On Events, click **+ condition** in the query card.
3. Choose a **Field**.
4. Click **Value**. A menu lists values your project has sent for that field.
5. For nested logic, add **+ All-of group**, **+ Any-of group** or **+ None-of group**. These buttons show only after the first condition exists.
6. Click **Apply**. **Apply** shows only when the filter or the dates are different from the results on the page. At other times, **Applied** shows in its place.

On Events, Sessions and Users, the toolbar shows each top-level condition or group as a token. Click a token to open the builder. Click the **×** on a token to remove it, then click **Apply**. The toolbar shows up to four tokens. A **+N more** chip opens the builder to show the others.

## Date ranges

The first time you open a page, it shows the last 10 days, with today as the To date.

- **The range includes the whole To day.** Every page counts the events of its To date.
- **Days are UTC.** There is no time-zone setting. Days, chart buckets and retention days run midnight to midnight UTC.
- **Sequential remembers the range.** Each page keeps the range that you last applied or ran, for each project, in this browser. If that range ended on the day that you applied it, it moves forward to end today, with the same length. A link with dates, or a funnel drill-down to **Events**, sets the range for that visit.
- **Apply does not always run the query again.** See **What Apply does on each page** below.
- The Sessions, Users and Events lists and Ask show local times. User detail shows local times too, except in the rows of a funnel's drill-down, which show UTC times without a label.

## Save filters, funnels and flows

Saved filters, funnels and flows belong to the project. Everyone in the project sees them. Owners, admins and members can save, rename and delete any saved item, also one that someone else saved. Viewers can only apply them.

1. On Events, Sessions or Users, click **More** → **Save filter…**. For a funnel or flow, click **Save** in **Funnel steps** or **Flow steps**.
2. Enter a name in **Filter name**, **Funnel name** or **Flow name**. Each name must be unique within its kind in the project. Capital letters do not make a name different: "Checkout" and "checkout" are the same name.
3. Click **Save filter**, **Save funnel** or **Save flow**. The item appears as a pill, a small rounded button, at the top of its page.

From 11 October 2026, you can also save a retention question. On **Retention**, click **Save as view**, enter a name in **Retention view name** and click **Save retention view**. The question needs at least one day.

To rename an item, click ✎ on its pill. Enter the new name and click **Rename**.

You cannot change the conditions or steps of a saved item. To change them, save a new item, then delete the old one with **×**.

When you delete an item, Sequential deletes it for everyone in the project. A message such as `Filter "Checkout errors" deleted.` shows with **Undo**. It sits above the page's own messages, so **Undo** stays in view. Click **Undo** to save the item again. You can also press ⌘Z (Ctrl+Z on Windows and Linux) while the message shows, when you are not in a text field. The message stays for at least 10 seconds, and longer while your pointer or keyboard focus is on it. To close it, click **Dismiss**. After you switch projects, Undo does not work. The message then says "Undo isn't available after you switch projects."

**Dashboard** in the left rail also lists the project's saved items. See **Dashboard controls** below.

> **Everyone in the project sees saved items**
>
> - Everyone in the project sees the same saved items, in every browser and on every device.
> - Each project has its own saved items. A saved funnel runs on its own project.
> - A saved filter can hold values such as user ids, email addresses or property values. Everyone in the project can see them.
> - Each pill shows who changed the item last, and when. Hover over the pill to see it, for example "updated by Ana, 2 h ago".
> - If you delete the project, Sequential deletes its saved items too.

## Use a saved filter as a funnel or flow step

You can build a funnel or flow step from a filter that is saved in the project. Sequential copies the conditions of the saved filter into the step.

1. Open **Funnels** or **Flows**.
2. Next to **+ Add step**, click **+ Step from saved view**.
3. To find a filter by name, type in **Search saved filters…**.
4. Click the filter.

The new step goes at the end of the list, with the name of the saved filter. To put the conditions of a saved filter into a step that you already have, click **Replace with saved view** on that step.

**The step is a copy.** You can change its conditions and its name. Your changes do not change the saved filter. When someone changes or deletes the saved filter later, your funnel or flow does not change.

The step shows **From saved view:** and the name of the filter. To copy the current conditions of the filter again, click **Update from view**.

### More about steps from saved filters

- The menu lists the saved filters of the project. The filter that was changed most recently is first. Each row shows who changed the filter last, for example "by Ana".
- Some filters are greyed out, with the reason:
  - "No conditions yet": the filter has no condition.
  - "Too large to use as a step": the filter has more than 500 conditions and groups in total, or groups more than 25 levels deep.
- If the step already has conditions, **Replace with saved view** asks first, in a dialog titled **Replace conditions**, for example: `Replace the conditions of Step 2 with those of the saved view "Checkout"?` Click **Replace** or **Cancel**. A step with no conditions changes at once.
- **Replace with saved view** keeps the name that you gave the step. A step with a default name, such as **Step 2**, takes the name of the filter.
- The label keeps the name of the filter from the time of the copy. **Update from view** changes the label to the current name of the filter. It does not rename the step.
- If you changed the step after the copy, it shows **edited**. **Update from view** then asks first, in a dialog titled **Update from saved view**: "This step was edited after it was copied. Replace it with the saved view's current conditions?" Click **Replace**, or click **Keep my edits** to keep your step.
- If only the saved filter changed, the step shows "view changed". **Update from view** then copies the new conditions at once.
- If someone deleted the saved filter, **Update from view** is greyed out. Its tooltip says "This saved view no longer exists". The step keeps its conditions.
- A saved funnel or flow keeps the **From saved view:** label of each step.
- Every role can use a saved filter as a step, viewers included. To save the funnel or flow, you must be an owner, admin or member.

## Move saved items from this browser

Earlier versions of Sequential kept saved filters, funnels and flows in each browser. If your browser still has such items, Sequential offers to move them into the project. A dialog, such as **Move your saved items to Web shop**, says how many items it moves and who will see them.

1. Read the dialog. If a name is already taken in the project, a number is added: "Checkout" becomes "Checkout (2)". The dialog lists each name that changes.
2. Click the button that names the project, such as **Move 3 items to Web shop** or **Move 1 item to Web shop**. If the project has no name, the button says "this project".
3. The result says how many items moved. It lists each item that Sequential did not accept, with the reason. Click **Done**.

If you do not want to move them now, click **Not now**. Sequential asks again in 7 days, for this project in this browser. Closing the dialog with Escape, a click outside it or **×** hides the offer only until you reload the page. It saves nothing. To stop the offer for this project in this browser, click **Don't ask again**. The dialog says this too: "Not now asks again in 7 days. Don't ask again stops the offer for Web shop in this browser."

- Sequential does not delete or change the copies in your browser. After the move, the pages show the project's items, not the copies.
- An item without a name, or without conditions or steps, cannot be moved. The dialog lists it under "can't be moved", with "it has no name" or "it is empty".
- Viewers do not get the offer, because they cannot save items.
- Sequential does not make the offer in the replay player. It asks on the next page that you open.

### More about the move

- The items in a browser are not tied to a project. So Sequential offers them once for each project that you open in that browser. Move them only into the project where they belong. For the other projects, click **Don't ask again**.
- After a move that finishes, Sequential does not offer the move again for that project in that browser.
- If the move stops, for example because the connection drops, the dialog says "Moving stopped" and "Nothing was lost." Sequential offers the move again the next time you open the app, but only for the items that did not move. The dialog then says "Items you already moved to Web shop aren't offered again."
- Sequential keeps the list of moved items in this browser, for each project. In another browser, or after you clear this browser's data, the items that already moved are offered again. They then get a number, because their names are taken.

### When saved items stay in this browser

A Sequential server that does not have shared saved items yet keeps them in your browser, as before. This happens only on a server that has not been updated.

- Only you see the items, and only in that browser. They are not tied to a project.
- Every role, viewers included, can save, rename and delete them.
- Sequential does not offer the move.
- On **Dashboard**, a card shows the date when the item was saved.

## Share a view by link

Everyone in the project sees its saved items. To show someone a view without saving it, you can send the page address (URL), because some pages take their view from it.

- **Pages do not add the project to a link.** Ask the reader to select the same project first. Or add `project=` and the project id to the address. The reader must be able to open that project. See [Links that open a project](/docs/sessions-and-replay#links-that-open-a-project).
- **Pages do not add your filter or dates to the address.** To share them, add them to the address yourself.
- **A link can carry only ids as conditions.** See **What each address can carry** below.

## What it needs

A filter can match only the data that your SDK sends.

- To filter your own events by **Event Name**, send them as custom events. See [Send custom events](/docs/custom-events).
- For **User ID** to hold your own ids, call `identify`. See [Identify your users](/docs/identify-users).
- **CSS Selector**, **Account ID** and the properties depend on your SDK. See [What each SDK supports](/docs/support-matrix).

## Limits

- On Retention, **Only people who…** chooses who is counted. Their start event must match it. It does not change which events count as a return.
- Some fields are empty for some SDKs.
- There are no preset date ranges.
- A typed **URL** with query values does not match, because Sequential redacts query values. A `#…` part matches only when it is a hash route, such as `#/orders`. Pick the URL from the menu.
- For Mixpanel and Smartlook, a **Visitor Property** condition finds only identify events. PostHog and Sequential SDK events have no visitor properties.

### Example questions

Use the date bar and the filter builder for questions like these:

- Which errors happened on the checkout page last week, outside Safari?
- Which sessions this month included a `plan_changed` event?
- What did people from Germany on iOS do on Monday?

### How conditions combine

- **Event Type** = `click` AND **URL** = your pricing page does not mean people who clicked something and also viewed pricing.
- **Groups combine their rows** with **All of**, **Any of**, **None of** or **Not all of**. The menu at the top of the builder combines the top-level rows.

### What the filter does on each page

| Page | What the filter does |
|---|---|
| Events | The page counts, charts and lists only the matching events |
| Sessions | On **Latest** and **Watch**, each top-level filter row is tested on its own. A row appears when, for each filter row, at least one of its events matches that filter row. Two filter rows can match different events. The conditions in one **All of** group must match the same event. A NOT group keeps the sessions that have no matching event. **Ask** does not use this rule: a session needs events that match the whole filter. From 9 October 2026, its counts and times cover all of its events in the range |
| Users | Each top-level filter row is tested on its own. A row appears when the person has an event that matches each filter row. A NOT group keeps those with no matching event. From 10 October 2026, a row's counts and times cover all of its events in the range. The line about events without a user id counts only the matching events |
| Funnels, Flows | Each step has its own filter |
| Retention | **Only people who…** narrows the cohorts: the start event must match its conditions. The return event has its own conditions in the sentence |

### NOT groups

- A NOT group is a group whose menu reads **None of** or **Not all of**. Choose the mode in that menu, at the top of the group.
  - **None of** leaves out events that match any of its conditions: NOT (a OR b). A new **+ None-of group** starts as **None of**.
  - **Not all of** leaves out only events that match all of its conditions together: NOT (a AND b).
  - With one condition, the two modes are the same.
- A NOT group in a filter that you saved before these two modes existed is **Not all of**. Its results do not change.
- To leave out either of two values, use one **None of** group with both conditions.
- A NOT group with one condition also leaves out events with no value in the field it tests. For example, a NOT group with only **Browser** = Safari drops events with no browser recorded.
- NOT **Account ID** = … drops every event without an account id. Only Pendo and `sequential.account()` set one.
- **Event Type**, **Session ID**, **User ID** and property conditions do not have this behaviour.
- On **Sessions**, a NOT group leaves out sessions, not events. **None of** lists the sessions that have no event for any of its conditions. **Not all of** lists the sessions that have no event for at least one of its conditions.

### Fields and what they match

| Field | What it matches |
|---|---|
| **Event Type** | The event's class by its id: `pageview`, `click`, `form_submit`, `identify`, `error`, `rage_click`, `dead_click`, `custom` or `system`. See [Events](/docs/events) |
| **Event Name** | The name the SDK sent, such as your custom event names |
| **Source** | The SDK that sent the event |
| **Session ID** | The session id stored on the event |
| **User ID** | The person. With the Sequential SDK, PostHog or Mixpanel, your own id also finds the events sent before your app called `identify`. See **How a User ID condition matches** below |
| **Account ID** | Pendo data, and Sequential SDK events after `sequential.account()` |
| **URL** | The whole stored address. Sequential stores query values as `[redacted]`, unless the parameter is a campaign or ad-click parameter, such as `utm_source` or `gclid`. It does not keep the `#…` part, except a hash route, such as `#/orders`, from 9 October 2026. Pick the value from the menu. Do not type it. Empty for Amplitude events. See [What Sequential keeps from page URLs](/docs/url-policy) |
| **Page** | From 11 October 2026. The path of the URL, as Heatmaps and the Dashboard tiles group pages: no host, no query and no `#…` part, without a slash at the end, and numbers, UUIDs and long hex ids read `:id`. For example, `/orders/:id` matches `/orders/123?tab=2` |
| **Traffic Source** | From 15 October 2026: the other site that a visit came from, such as `google.com`. Empty for no referrer and for your project's own pages |
| **UTM Referer** | The page the person came from (the referrer). Empty for Amplitude events |
| **CSS Selector** | The clicked element. Empty for PostHog, Mixpanel and Amplitude events |
| **Country**, **OS**, **Browser**, **User IP** | Sequential finds these from the request: a two-letter country code such as `DE`, the operating system, the browser, the IP address. Before 12 October 2026, **OS** was called **Platform** |
| **Platform** | The website or the app: `web`, `ios`, `android` or `other`. Safari on an iPhone is `web`, and the iOS app is `ios`. An app view that shows a web page is also `web`. The field suggests only these four values, and Sequential refuses any other value |
| **Visitor Property**, **Account Property** | A text property, by **Property name** and **Property value**. Account properties come from Pendo and from `sequential.account()`. Mixpanel and Smartlook send visitor properties only on their profile (identify) events. So a condition finds those events, not the person's other events. PostHog and Sequential SDK events carry none |
| **Event Property** | One of the event's own properties: its name, a type, an operator and a value. See **Property conditions** above |
| **Session Property** | On **Sessions** only: the first or the last value of an event property in each session, such as the entry page. See **Property conditions** above |

### How a User ID condition matches

With the Sequential SDK, PostHog or Mixpanel, identify sends a link from the anonymous id to the value that your app passes. A **User ID** condition uses that link.

- On **Events**, **Sessions** and **Users**, and in funnel and flow steps, the condition finds the whole person. User detail shows the whole person too. The identified value finds the events from before identify too. A linked anonymous id finds the same person.
- **Users** then shows the person once, with all their events and sessions.
- The **Events** list still shows the id that each event was stored under.
- A funnel's **View users** and **View events** show the same people that the funnel counted.
- A new link can take up to 5 minutes to apply.
- The link is one step. See [Users and identity](/docs/users-and-identity).
- With Amplitude, Pendo or Smartlook, nothing sends the link. The condition matches the stored id.

For **User ID**, the filter builder makes only exact matches. A request to the app's API can use other kinds of **User ID** condition:

- A list of ids finds each person.
- A pattern, such as contains, starts with or a wildcard, matches the stored id or the identified value.
- "Is set" and ranges match the stored id.
- In the `user_id` field of an **Events** request, an empty list matches no event. In a filter condition, an empty list has no effect.

### Past filters and Reset

- **Past filters** lists up to 10 different filters that you applied on that page, newest first. On Events, Sessions and Users, it is in the **More** menu as **Past filters…**.
- To use one, pick it and click **Apply**.
- The list is yours only. Nobody else in the project can read it, admins included. Viewers keep their own list too.
- Each project and each page has its own list. The list follows you to your other browsers and devices.
- A filter that you apply shows in the list at once. The people that a funnel hands over to **Events** or **Users** are not added. They are for that view only. When you switch projects, the list of that project shows.
- Two tabs do not share new entries. A filter that you apply in one tab shows in the other tab after you reload it or switch projects.
- Earlier versions kept past filters in each browser. Sequential does not move that list or delete it. Your list starts empty.
- A Sequential server that has not been updated keeps past filters in this browser, as before. Each browser then keeps its own list, and the list is not separated by project.
- To empty a builder, click its **Reset** button (tooltip **Reset all filters**) and confirm with **Reset all**. The button shows only when the builder has a filter. A new empty condition is not a filter. This also works in the funnel, flow and retention builders.

### Value menus

- The **Value** menu lists up to 1,000 values your project has sent for that field, most frequent first.
- If there is no menu, the project has sent no value for that field.
- The menu covers all time, not only your dates. It does not narrow as you type.
- **Property name** and **Property value** suggest up to 100 values each.

### Move rows and hide the builder

- The arrows move a row up or down.
- If a row is next to a group, the arrows move the row into that group. The group's **All of**, **Any of**, **None of** or **Not all of** then applies to the row.
- The arrows with the tooltips **Move up (out)** and **Move down (out)** lift a row out of its group.
- **×** removes a row.
- On Retention and the funnel and flow steps, a builder with five or more conditions hides behind a **Show** chip with the count, such as **Show (5 filters)**. To open the builder again, click the chip.
- On Sessions and Users, the builder stays closed until you click **Edit filters**, **+ Add filter** or a token. On Events, **+ condition** opens it too. Click **Edit filters** again to close it.

### Explain filter and Analyse with AI

Click **Explain filter** to see the filter on one line (on Events, Sessions and Users: **More** → **Explain filter…**), such as `(event_type = "Error" AND browser = "Chrome")`.

- It uses internal field names, such as `country_code`.
- It shows event types by name, but you enter them as ids, such as `error`.

**Analyse with AI** (**More** → **Analyse with AI…** on Events, Sessions and Users) writes a prompt for your own AI tool. See [AI and third parties](/docs/ai-and-third-parties).

### The Product manager builder (gone)

Until 14 October 2026, the **More** menu on Events had a **Filter builder** choice: **Technical** or **Product manager**. Both edited the same filter. From that date, no page offers the **Product manager** builder. Every page has the builder with all the fields, and a filter that you saved before opens in it.

See [Explore events](/docs/events-explorer).

### What Apply does on each page

On Events, Sessions and Users, one toolbar holds the From date, the To date, the filter tokens, **Apply** and **More**. On the other pages, the date bar at the top holds a From date, a To date and **Apply**, and the filter builder is under it.

| Page | What Apply does |
|---|---|
| Events, Sessions, Users | One **Apply** applies the dates and the filter together. Then it loads the results again |
| User detail | It loads the **Sessions** card again |
| Accounts | One **Apply** applies the dates, the plan and the name or id together. A health chip applies at once |
| Funnels | From 15 October 2026, it runs the funnel again when there is a result. The old result stays, dimmed, until the new one is ready |
| Flows | It clears the results. Then click **Run** |
| Retention | Click **Analyse retention** |

### Which pages include the To day

| Page | The To day |
|---|---|
| Events, Sessions (including **Watch** and **Ask**), Users, User detail, Accounts, Funnels, Flows, Retention | Included, up to midnight UTC |

**Interval** on Events sets the chart's buckets: **Hour**, **Day**, **Week** or **Month**. A week starts on Monday, in UTC.

### Opening dates west and east of UTC

The opening dates are UTC dates too. In the evening west of UTC, the To date is already tomorrow's date. Early in the morning east of UTC, the To date is still yesterday's date, so the range leaves out the events since midnight UTC. To include them, set the To date to your today.

### Funnel drill-downs

- **View events** opens Events with the funnel's dates.
- **View users** keeps the Users page's own dates. It shows the funnel's dates under **Date range** in a banner.
- If the list looks short, set the dates to match the banner.

### Times on screen

Times on screen are not always UTC.

- The Sessions, Users and Events lists and Ask show your local time. The lists show a relative time, such as "2 d ago". Hover it for the exact time. For example, a session starts at 23:30 UTC on 3 September. It belongs to that day's range. Two hours east of UTC, its exact time reads 01:30 on 4 September.
- In a funnel's drill-down, User detail shows the UTC clock time, but it does not say so. There, that session's events read 23:30 on 3 September.

### What each saved item keeps

| To save | Click | What it keeps |
|---|---|---|
| A filter | **Save filter** in the builder on Events, Sessions or Users | The filter as it is in the builder |
| A funnel | **Save** in **Funnel steps** (needs a step) | The steps and their filters, not the dates |
| A flow | **Save** in **Flow steps** (needs a step) | The steps and the From and To dates |
| A retention question | **Save as view** on **Retention** (needs a day) | The start event, the return event, the days, **Group by**, **Count** and **Only people who…**, not the dates |

Saved flows keep their dates. Saved funnels, filters and retention questions do not. They use the dates in the bar.

### How saved pills behave

- Pills appear under **Saved filters:**, **Saved funnels:**, **Saved flows:** or **Saved retention views:** at the top of their page.
- Saved filters are one list for the project, shown on Events, Sessions and Users.
- A filter's pill applies the filter at once.
- A funnel or flow pill loads the steps and waits for **Run**. Until then, the previous funnel results stay on screen.
- A retention pill puts the question on the page and clears the result. Click **Analyse retention**. If the saved question cannot be used, a message says so and the page does not change.
- Hover over a pill to see who changed it last, and when. For example: "Apply funnel: Signup — updated by Ana, 2 h ago".
- ✎ renames an item and **×** deletes it. Viewers do not see these buttons. When a viewer clicks **Save**, a message says, for example, "Your role can apply saved funnels but not change them."
- The pages load the list when you open the app. To see the latest changes of your teammates there, reload the page. The search (⌘K) reads the list again each time you open it, and **Dashboard** each time you go back to it.
- If the list does not load, the strip says, for example, "Couldn't load saved funnels." Click **Retry**.

### When two people change the same item

- Sequential refuses a rename if someone else renamed the item after you loaded the page. The message says "Someone changed this since you loaded it — reload to see their change." Click **Reload** in the message, check the new name, then rename again if you still want to.
- If someone deleted the item, the message says, for example, "This funnel has been deleted. Reload to see the current list."
- Sequential refuses a name that the project already has for that kind: "A funnel named "Checkout" already exists. Choose another name."
- A delete does not check for changes. It deletes the item, also when someone renamed it after you loaded the page.
- **Undo** saves the deleted item again as a new item. Its pill then names you as the person who changed it last.

### Dashboard controls

- Sequential also opens **Dashboard** after you sign in. The project's saved items are in the **Saved items** card, under the dashboard tiles.
- Each card shows when the item was last changed, and by whom. For example: "Updated today by Ana", "Updated yesterday by Ana" or "Updated 3 days ago by Ana". An older change shows a date.
- If you have saved nothing, the card says "Saved filters, flows and funnels appear here." It links to **Create a filter**, **Create a flow** and **Create a funnel**. When **Dashboard** shows the full setup checklist, this card does not show.
- To narrow the list, use **Search saved items…**, the type menu and the sort menu.
- The type menu has **All types**, **Filters**, **Flows**, **Funnels** and **Retention**. A saved retention question's card says how many days it measures, for example "3 days".
- The sort menu has **Most recent**, **Oldest first** and **Name A–Z**. **Most recent** puts the item changed last at the top.
- To open an item, use its card's open icon. The icon has a label such as **Open and apply in funnels section**. It takes a filter to Events and applies it. It opens a funnel or flow with its steps loaded, ready for **Run**. It opens a retention question on **Retention**, ready for **Analyse retention**.
- If the page opens without your item, click its pill there.
- The **Hide** icon moves a card to the **Hidden** list. On that list, **Move back to saved items** brings it back. **Visible** and **Hidden** switch between the two lists. The **Hidden** list is kept in this browser only. Hiding an item does not hide it for anyone else.
- If the list does not load, the card says "Couldn't load saved items." Click **Retry**.
- You cannot delete an item on Dashboard. To delete it, click **×** on its pill.

### What each address can carry

To share a funnel, flow or filter with everyone in the project, save it. To share it with someone outside the project, send its steps or the text from **Explain** or **Explain filter**. They can then build it again.

| Page | What the address can carry |
|---|---|
| Events | `user_id`, `session_id`, `account_id`, `from_date`, `to_date`, `breakdown_by`, as in `/events?session_id=…&from_date=2026-09-01&to_date=2026-09-08`. From a funnel's **View events**, `funnel_handoff=`: the people and the funnel's dates stay in your browser tab for one hour, so this link does not work for someone else |
| Sessions | The tab and Ask question (`?mode=latest`, `?mode=watch`, `?mode=ask&q=…`), `user_id`, `account_id`, and `problems=1`, which shows only the sessions with a JavaScript error or a failed request. **Watch sessions** on Events adds `filter_from=events` and `handoff=`: the filter itself stays in your browser tab for one hour, so this link does not work for someone else. A click on a tab adds `mode` to the address. Without `mode`, Sessions chooses the view: see [Find and replay sessions](/docs/sessions-and-replay) |
| User detail | `user_id`, `from_date`, `to_date`. Here `user_id` picks the user |
| Accounts | `from_date`, `to_date`, `plan`, `health`, and `q` for the name or id. An old `/entities` link opens Accounts with its dates. With an `account_id`, it opens that account's page with its dates |
| An account's page | `account_id`, `from_date`, `to_date`, as in `/account-detail?account_id=acme&from_date=2026-10-01&to_date=2026-10-07` |
| Users | `account_id` |
| Replay | The session, moment and panel. Use **⧉ Share** in the player. See [Find and replay sessions](/docs/sessions-and-replay) |
| Funnels, Flows, Retention, Dashboard | Nothing |

- You cannot share a funnel's drop-outs by link: the address holds only a key to your browser tab. To share the funnel, save it.
- On Events and Sessions, a `user_id`, `session_id` or `account_id` in the address becomes a condition in the reader's filter. On Users, an `account_id` does too. A link carries no other condition.
- The link opens in the project that the reader has selected, unless the address has `project=`. The reader must belong to the organisation that owns the project. See [Organisations, projects and keys](/docs/organisations-and-projects).

## Related

- [Explore events](/docs/events-explorer)
- [Funnels](/docs/funnels)
- [Flows](/docs/flows)
- [Retention](/docs/retention)
- [Find and replay sessions](/docs/sessions-and-replay)
- [Users and accounts](/docs/users-and-accounts)
- [Events](/docs/events)