Migration map.

segment_preview

Calculate a time-specific audience count without saving a segment. Requires the reader's access and required channelCode plus conditions. Read-only behavior may use POST transport.

Condition input

All objects are strict. conditions.include is required; conditions.exclude is optional/null. Each present tree contains 1–20 groups, each with 1–25 anyOf conditions. At most 100 conditions are accepted across both trees together. Conditions within anyOf are OR; groups are AND. Exclusion removes the audience matching its combined tree from inclusion. No empty include or implicit all-user default is accepted. Omitted/null exclude removes exclusion when conditions are replaced.

Composition rules

Copy classificationCode from segment_options. The composer parses its source classification structure, resolves the current parent definition and checks exact option membership. Draft/Upcoming/Sunset are rejected; Deprecated adds a warning. Any MUTABLE condition makes the entire composition mutable.

Entity conditions derive a supported target from the definition and require nonempty observed IDs. SINGULAR or explicit useMultiSelect:false requires exactly one. The source read-only resolver is called twice; identities/order/content must agree and exactly cover the requested IDs, with no deleted, duplicate or foreign-channel row. Canonical targetEntityMetas is built from those exact resolved IDs/titles with isDeleted:false after absence/deletion checks. A missing optional resolver flag is not exposed as evidence of broader lifecycle eligibility. Caller-provided labels/metadata are not accepted. Conditions without a selector reject nonempty targetEntityIds. At most one exhaustible coupon/discount condition is allowed across both trees, and it must be alone in its OR group.

The source value slot must match valueType. The composer uses the observed definition name for itemName and the selected option name/description for selectedOptionName/selectedOptionDescription for every supported value type, including NUMBER. Canonical nondeleted entity metadata and explicit conditions form the four-depth source trees. Full-tree equality remains required; arbitrary returned metadata is not ignored and no raw caller tree is trusted.

{"channelCode":"selected-channel-code","conditions":{"include":[{"anyOf":[{"classificationCode":"SGMT_FINALIZED_NONE_ENUM_USER_A001001"}]}]}}

{"channelCode":"selected-channel-code","conditions":{"include":[{"anyOf":[{"classificationCode":"SGMT_FINALIZED_NONE_ENUM_USER_A001001"}]}],"exclude":null}}

The classification in these shape examples comes from source demo fixtures. Replace it with an actually observed option; it is not a recommended all-user selection.

Count and limitations

FINALIZED composition invokes the source count POST after initial guards, then repeats composition and context checks. Success SEGMENT_COUNT contains countResult {total,matched}, nonnegative safe integers with matched <= total, and warnings. writesPerformed:false and verification {confirmed:true,atomicSnapshot:false,memberEligibilityVerified:false} concern that observation.

MUTABLE returns action_required/SEGMENT_COUNT_NOT_SUPPORTED, countResult:null and verification.confirmed:false. No count request is sent in that path, but definition reads, selected entity-resolution POSTs and context checks may already have occurred. Do not turn null into zero.

No save, job, member export, reservation or benefit issuance occurs. Only entity resolution accepts HTTP 200 or 201 with the required data envelope; count still requires 200. These response rules retain channel and credential continuity checks. A count is neither individual entitlement nor future delivery/eligibility.

Current observations use the bounded response and recovery rules. An oversized response is not a successful empty result. If a write was already sent, retain its original task and reconcile; the failed read does not authorize repeating the change.

Inputs