{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/lifecycle-marketing.segment-build-readback/",
    "json": "https://www.anchorterminal.com/niches/lifecycle-marketing.segment-build-readback/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/lifecycle-marketing.segment-build-readback/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/lifecycle-marketing.segment-build-readback/index.min.md"
  },
  "markdown": "One company's docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 1 | 7 | 11 | 10 | 3 |\n\n## What counts as done\n\nA segment exists with the stated conditions and its full member list or exact count can be read back with paging, before any send.\n\nMeasured, for our own tests: the read-back takes at most 3 calls.\n\nHow 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\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **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.\n\n## Does the job, with a limit\n\nIt 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.\n\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **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.\n\n- 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.\n- 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.\n- 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.\n\n## What stops agents finishing\n\n- no API to build a dynamic segment (Iterable)\n- segment creation limited to 100 a day (Klaviyo)\n- a filter the API ignores silently, returning everyone\n\n## Around it\n\nBefore: lifecycle-marketing.profile-event-sync. After: lifecycle-marketing.campaign-draft, lifecycle-marketing.send-with-approval.\n\n## Where this comes from\n\nWeight 10 of 100 in Lifecycle marketing \u0026 customer engagement: 3 of 30 counted mentions (acc-07, 13, 21); vendor pages (Customer.io, Klaviyo) push this use case harder than accounts do\n\nAs 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.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Build a segment and confirm who is in it",
        "url": ""
      }
    ],
    "description": "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 \u0026 customer engagement with the reason and a source.",
    "facts": null,
    "h1": "Build a segment and confirm who is in it",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/lifecycle-marketing.segment-build-readback/",
    "published": "",
    "section": "agents",
    "title": "Build a segment and confirm who is in it | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/lifecycle-marketing.segment-build-readback/"
  },
  "tokens": {
    "markdown": 1350,
    "slim": 280
  },
  "version": 1
}
