Skip to content
  1. Home
  2. Help center
  3. Reports & metrics
  4. Settings → Segments

Settings → Segments

Last updated:

The Segments screen answers “which categories of my own do I want reports broken down by”. Here you define a slice — a dimension that shows up in breakdowns and filters next to source and campaign — and the rules that put a row of data into one category or another.

What you see here

Every slice of the project sits on one page, one block each, top to bottom. Each block has its own header: the name, the field the slice is exposed under in reports, and an Add segment… button.

Inside the block is a table of segments:

  • Segment — the category name. This is what becomes a row in a breakdown.
  • Condition — the rule that gives a row of data this segment.
  • Reach — how many rows the rule caught over the selected period, and what share that is.
  • State — applied, waiting for recalculation or off.

Below the table are the Unlabelled values: value sets that no rule of this slice caught. That is not junk, it is the list of what you have not named yet; the Segment… button next to a row creates a rule from that exact set.

Above the table is a status line: how many rows were scanned over the period, how many matched no segment, how many segments are waiting for recalculation, and when the last recalculation ran.

Set it up for your question

Create a slice

  1. In the section toolbar, click Add slice….
  2. Pick a preset — Channels, Ad platforms, Paid and organic traffic — or a Blank slice if you would rather write the rules yourself.
  3. A preset is created with working rules; you can edit them afterwards.

The presets follow one principle: a slice answers a single question. Channels answers how a person arrived, Ad platforms answers which platform the click was bought on. Mix the two in one slice and a breakdown row stops answering anything in particular.

Describe a segment

  1. Click Add segment… in the slice header.
  2. Give it a Segment name — that is what becomes a report row.
  3. Build the condition on the Builder tab: field, operator, value. Conditions inside a group are joined by the AND / OR switch on the vertical rail to the left.
  4. Click Check reach — KO counts against live data how many rows the rule catches.
  5. Save.

The ? next to an operator opens “What this means”: what exactly the operator compares and which syntax it understands. Operator names in the builder currently come from the backend in Russian — the English interface shows them as they are.

Two operators are easy to confuse and behave very differently. Совпадает (matches) compares the whole value against a pattern: a comma-separated list reads as OR, * stands for any characters, #…# is a regular expression, and case is ignored. Один из списка (one of a list) is exact equality, case-sensitive, no patterns. Use matches for tags and domains, and one of a list for identifiers (connector, campaign, CRM step).

A rule that does not collapse into two levels will not open in the builder — edit that one on the JSON tab.

Turn off what you do not use

Turn slice off in the More menu removes the slice from reports but keeps the markup already calculated: turning it back on restores it at once, with no recalculation. Deleting does not keep it.

How to read it

Reach is counted over the window selected in the section toolbar (7, 30 or 90 days), and over rows, not leads. The “matched by no segment” figure is the key number on this page: while it stays high, a breakdown by this slice will be half “other”.

Segments of one slice must not overlap. A row of data lands in every segment it matches, and the report shows it in each of them — so an overlap double-counts. If two rules catch the same thing, narrow one of them.

Edits do not apply instantly. A segment whose rule changed sits in the waiting for recalculation state, and the editor says “Data is recalculated by a separate run”. Until then the report shows the old markup.

Recalculation changes the numbers retroactively, across the project’s whole history. That is not a bug: a segment is not a property of a moment, it is a reading rule, and it applies to all data at once. So edit rules deliberately rather than to see what happens.

A “no such field” mark on a condition means there is no such field in the data at all — the rule will never match. Usually that is a typo in the key, or a field the source stopped sending.

If there are no numbers

  • “No slices yet” — the project is new. Start from a preset: it comes with working rules, and you can see at once how the thing is put together.
  • “No segments in this slice yet” — the slice was created blank. Until it has at least one segment, the dimension stays empty in reports.
  • Reach is zero for every segment — either the project has no data over the selected period, or the rules point at fields that are not in the data. Check the Condition column: the “no such field” mark is visible right there.
  • The rule caught rows but the report is empty — the segment is still waiting for recalculation.

What’s next to it