# Build a segment and confirm who is in it

> Build a segment and confirm who is in it: 1 companies fully do it, 7 with a limit, 11 carry the tag. Every listing in Lifecycle marketing & customer engagement with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/lifecycle-marketing.segment-build-readback/
- Markdown: https://www.anchorterminal.com/niches/lifecycle-marketing.segment-build-readback/index.md (~1,350 tokens)
- Slim: https://www.anchorterminal.com/niches/lifecycle-marketing.segment-build-readback/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/lifecycle-marketing.segment-build-readback/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 7 | 11 | 10 | 3 |

## What counts as done

A segment exists with the stated conditions and its full member list or exact count can be read back with paging, before any send.

Measured, for our own tests: the read-back takes at most 3 calls.

How agents ask for it: who are our lapsed purchasers; build a segment of VIPs who haven't opened in 90 days; how many people will get this

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Sequenzy (Nic Tech Solutions, LLC)**: Create segment takes flat filters or a nested filter tree, and GET /segments/{id}/count recalculates the active subscriber count from the saved filters, two calls in all.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Braze (Braze, Inc.)**: create_segment takes a filter tree checked against get_segment_filters, but size comes back as a daily estimate and the member list only through an async segment export to a ZIP URL, not paged in 3 calls.
- **Customer.io (Peaberry Software, Inc. d/b/a Customer.io)**: customer_count and paged membership read a segment back, but POST /v1/segments creates only empty manual segments; data-driven segments come through the MCP server, whose filter validation is not documented.
- **Klaviyo API + MCP (Klaviyo, Inc.)**: POST /api/segments takes a definition, profile_count is an additional field and segment profiles page back, but creation is capped at 100 a day, filter-key validation isn't documented, and acc-07 found the SDK dropped the paging links.
- **Mailchimp Marketing API (The Rocket Science Group LLC d/b/a Mailchimp)**: Create Segment takes match and conditions, member_count is returned and members page back up to 1,000 with total_items, but acc-21 shows Mailchimp silently ignoring a non-existent filter and returning everyone.
- **MoEngage (MoEngage, Inc.)**: create_custom_segment takes filters and start_segment_count then poll_segment_count returns a count in three calls, but event and event-attribute names are never checked at creation, so a wrong one fails later with no reason unless deep_validate_segment_filters runs first.
- **Nitrosend (Nitrosend Pty Ltd)**: nitro_define_segment previews filters by default and saves on request, but counts are refreshed in the background as an operational guide, not exact, and no paged member read-back was found for a segment.
- **Omnisend (Omnisend, UAB)**: POST /segments takes contact and event filters and segment statistics return contactsCount, but the count answers 409 while the segment builds, and whether unknown filter keys are rejected wasn't found.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **ActiveCampaign (ActiveCampaign, LLC)**: Not read: hosts paused under the terms question. The 8 October notes say create_segment exists and unsupported filter keys are silently ignored, which would make this a caveat at best.

- not this job: CleverTap (WizRocket Inc.): Create Segment takes only a segment_name and customer_segment_id, with no filter conditions, so a segment with stated conditions cannot be built; Get Profile Count can count an event query separately.
- not this job: Dreamlit (Notika AI (d/b/a Dreamlit AI)): There is no segment object or member read-back; a workflow's audience is described in its prompt and resolved by query steps against the app database.
- not this job: Iterable (Iterable, Inc.): POST /api/lists creates static lists only; no operation builds a list from conditions, though list size and getUsers read a list back.

## What stops agents finishing

- no API to build a dynamic segment (Iterable)
- segment creation limited to 100 a day (Klaviyo)
- a filter the API ignores silently, returning everyone

## Around it

Before: lifecycle-marketing.profile-event-sync. After: lifecycle-marketing.campaign-draft, lifecycle-marketing.send-with-approval.

## Where this comes from

Weight 10 of 100 in Lifecycle marketing & customer engagement: 3 of 30 counted mentions (acc-07, 13, 21); vendor pages (Customer.io, Klaviyo) push this use case harder than accounts do

As data: https://www.anchorterminal.com/api/v1/use-cases/lifecycle-marketing.segment-build-readback.json, or the MCP tool get_use_case with id lifecycle-marketing.segment-build-readback. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
