Segments
A segment is a saved, named filter. You build the conditions once and apply them wherever you need them: on the Users page, in reports and in a broadcast audience.
Typical segments: "paying customers" (did successful_payment at least once), "Premium users",
"Russian-speaking", "pressed the button but never paid".
What a segment stores
- Conditions, not a list of people. Who is in a segment is worked out again for the period of the page where you apply it. "Paid at least 3 times" over the last 7 days and over the last 30 days are different people.
- One bot. Event and property names belong to each bot, so a segment applies only to the bot it was built for.
- Shared by the project. Everyone in the project can see and apply it.
Creating a segment
- Open the Users page and choose a bot.
- Build the conditions in the filter builder. The table below it is a live preview: you see straight away who falls into the segment for the selected period.
- Press "Save as segment" and give it a name.
To change a segment, apply it, adjust the conditions and press "Update "name"". If a colleague changed the segment while you were editing it, the save is refused, so nobody's edit is overwritten silently. Your conditions stay in the builder: save them as a new segment, or apply the segment again to see its current version.
Segment names are unique within a project, not within a bot: two bots in one project cannot both have a segment called "VIP". If a name is taken, Metriox tells you which bot holds it.
The Segments section
Every segment in the project is in the Segments section of the menu on the left.
- Search and filter by bot. Find a segment by part of its name, or show one bot's segments. The search and the filter are kept in the page address, so a filtered list can be shared.
- Open on the Users page. Click the segment's name: its conditions load into the filter builder, and the table shows who matches them.
- New broadcast to the segment. The broadcast icon in the segment's row opens a broadcast draft on the segment's bot with a copy of its conditions.
- Rename and delete are available to members with the Writer role or above. Deleting asks you to confirm.
- The top of the section shows how many segments the project has. From 80% of the plan's limit, the limit and a warning appear next to it. Once the limit is reached, no new segment can be created until you delete some.
"Create segment" opens the Users page: a segment is built where you can see straight away who falls into it.
A segment holds what the filter builder can show; anything else would be lost the next time it is opened:
- a list of conditions joined by a single AND or a single OR; each condition can be negated;
- a "did something N times" condition counts one event by name;
- up to 40 filter elements and no more than 4 profile-property conditions.
Nested groups such as "(A or B) and C" cannot be saved.
People or events
Every segment carries a badge. It tells you whether the segment behaves the same on every screen.
| Badge | Conditions | How it behaves |
|---|---|---|
| People | Only conditions about the person: a profile property ($tg.is_premium, $tg.language_code) or "did something N times" | Selects the same people in reports, on the Users page and in broadcasts |
| Events | At least one condition on an event or an event property | In a broadcast it selects the people who had such events. In a report it narrows the events themselves: the "Events by name" report with "pressed button X" shows only those presses, not everything those people did |
If you need a segment of people, describe the action as "did something at least 1 time"; the segment then gets the "People" badge.
Segments in reports
A report page has a "Segment" field next to the bot and the period.
- A segment in a report is live: change the segment, and the report shows the new membership the next time it is opened.
- The chosen segment goes into the link. A link with a segment opens the report on that segment's bot.
- If the segment in a link has been deleted, the report says so and offers to show data for all users. A chart without the segment is never shown under a link that names one.
Not every report can take a segment:
| Reports | Segment |
|---|---|
| Most event and user reports | Any |
| Retention | Only with the "People" badge: an event condition would change what "came back" means |
| Profile-property reports (languages, Premium, deep links), "New users", audience inflow and outflow, channel subscribers, the heatmap, 30-day churn, the funnel | Does not apply: these reports always count all of the bot's data, and their "Segment" field is disabled |
Segments in broadcasts
In the audience editor, press "Insert a segment": the segment's conditions are copied into the broadcast draft.
- It is a copy, not a link. If you later change or delete the segment, the broadcast does not change. That way a prepared broadcast can never be retargeted by accident by editing a segment.
- The editor shows which segment the conditions were copied from and whether they still match it. If they no longer match, you can insert them again.
- If the draft already has conditions, inserting a segment replaces them, and Metriox asks you to confirm.
- You can also start a broadcast from the Segments section: the broadcast icon in a segment's row opens a draft with a copy of its conditions.
On the Users page a segment contains everyone who matches the conditions. A broadcast reaches only people who opened a private chat with the bot; see who is in the audience.
Permissions and limits
| Action | Minimum role |
|---|---|
| Apply segments in reports, on the Users page and in broadcasts | Reader |
| Save, update, rename and delete segments | Writer |
- Deleting a segment is recorded in the project audit log as
segment.delete. - How many segments a project can keep depends on its plan: up to 10,000 by default. When the limit is reached, Metriox shows how many segments there are and how many are allowed: delete ones you no longer use in the Segments section and save again.
- If a plan's limit goes down, existing segments are not deleted: only saving new ones is refused.
- If you move a bot to another project, its segments move with it. A name already taken in the new project gets a suffix: "VIP (2)".
Segments and AI agents
Over MCP an agent sees the list of segments (metriox_list_segments): names, bots and the "People" or
"Events" badge. It can create a broadcast draft for a segment by passing segmentId to
metriox_create_campaign. The list comes in pages and can be searched by name. The conditions themselves are
never handed to the agent and cannot be edited over MCP.
What's next?
- Filters — which conditions you can build
- Users — where to build and check segments
- Reports — the ready-made reports a segment applies to
- Broadcasts — how to send a message to a segment