Filters, date ranges and saved views

• 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.

• 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.

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.

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?

• 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.

• 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.

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.
• 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 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.

• 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.

• 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.

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.

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.

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.

Interval on Events sets the chart's buckets: Hour, Day, Week or Month. A week starts on Monday, in 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.

• 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 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.

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

• 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.

• 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.

• 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.

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.

• 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.