Build and Publish a Rule-Based Audience Segment
Define a reusable audience by composing attribute and behavioral rules against unified profile data, then publish it for downstream activation.
A rule-based audience segment defines the population of profiles that satisfy a set of declared logical conditions. The key output is a named, versioned segment definition that the platform continuously evaluates against the live profile store. Practitioners must decide which combination of profile attributes (demographics, computed scores, consent flags) and behavioral event patterns (viewed product, abandoned cart, clicked email) best identifies the population they want to reach, and whether freshness requirements demand streaming or batch evaluation.
Critical decisions include the evaluation mode trade-off: streaming evaluation delivers millisecond latency membership updates but consumes more platform resources and is best reserved for high-stakes real-time use cases (website personalization, triggered messages); batch evaluation is more cost-efficient for scheduled exports to email or paid media. Segment definitions should also account for identity resolution — a well-structured segment will qualify the full merged profile, not just one device or channel identity.
Parallel viability note: Rule-based segmentation is one of the most widely supported capabilities across CDP vendors. Composable-stack alternatives include dbt-style SQL cohort definitions materialized in a data warehouse, with Hightouch or Census syncing membership lists to activation destinations. Pure-play CDPs (Segment, mParticle, Lytics) all offer visual segment builders with streaming or micro-batch evaluation. The AEP implementation is notable for its tight coupling with the XDM event schema and the Real-time Customer Profile, enabling profile-attribute conditions and event conditions to be composed in a single canvas without a separate SQL layer.
Side-by-side implementations
In AEP Real-time CDP, the Segment Builder canvas allows practitioners to define audiences using drag-and-drop XDM ExperienceEvent and XDM Individual Profile fields. Rules can combine attribute conditions (e.g., product name equals a specific value) with behavioral event frequency and recency constraints. Segments can be evaluated in batch or in streaming mode; enabling streaming evaluation means that a profile enters or exits the segment within seconds of the qualifying event, making the audience immediately available for real-time personalization. After saving, the segment appears in the Segments browse list with an estimated population count.
Capability: Audience Segmentation
Parallel implementation not yet available.
Hightouch Audience Hub provides a visual audience builder where practitioners define rule-based audience segments without writing SQL directly. Audiences are composed from a primary model (a Hightouch Model backed by a Snowflake query) using AND/OR condition groups. Attribute conditions filter on profile column values (equals, contains, greater than, is not null); event conditions leverage separate event models joined by user ID, supporting "performed X event at least N times in the last Y days" patterns that mirror AEP Segment Builder's event-frequency rules. Audiences are published with a sync destination and cadence (hourly by default; sub-minute lag with Hightouch Live Syncs). The estimated population count is computed via a COUNT(*) preview query on the warehouse before publishing. Rule-based audience definitions are stored in Hightouch and can be cloned, versioned, and shared across the organization — equivalent to AEP's saved segment library.
Capability: Audience Segmentation
Task-level sources
- technical-training/module6/index.md
- technical-training/module6/ex1.md
How is this implementation?
Sign-in-gated. Tomorrow morning's curriculum-ingestor consumes your feedback: "Inaccurate" queues the task for re-review, "needs update" queues it for a refresh, and "one vendor panel is wrong" re-drafts just that panel.