Segments
A segment is a group of leads inside a project. It stores its members and can define joining conditions: required consents and rules for assigning a primary or background agent.
To open the list, select Segments in the project side menu.
Segment or landing
A segment determines who belongs to a group and which rules apply when a lead joins. A landing determines what the user sees: the page, form, fields, and buttons. A landing button can subscribe the user to a selected segment.
If no form or additional fields are needed, you can use a direct subscription link for an ordinary segment. When the segment has required consents, the request first waits for acceptance; the lead does not join the segment before that.
Which subsection to open
- Creating and listing segments — create a segment, find it, filter the list, or delete an ordinary segment.
- Segment settings — change the name, assign agents, save, copy to a project, or share by link.
- Consents — add documents, update the selected version, and find leads who have not accepted the agreements yet.
- Subscription link — get a VK, Telegram, or MAX link and understand how it works with consents.
- Automatic segments — open an agent-managed segment and go to its settings.
Where to view members
View the audience in Leads by adding a filter for the required segment. Leads who are only waiting to accept documents appear in the separate Awaiting consent selection.
To send membership changes to your CRM or another service, configure a webhook for segment subscriptions and unsubscriptions. It reports actual joins and departures; awaiting consent is not a subscription yet. Each event identifies the segment, so one recipient can handle changes across the project's segments. Request fields are described in the event reference.