Audiences. Segments that keep up.
Reusable segments built from customer attributes, behaviour, consent, and usage.
Rules become a roster.
Membership is recalculated as traits and behaviour change.
One segment definition, reused everywhere, so targeting cannot drift between tools.
Five ways to draw a line.
Lifecycle segmentation
Users can be grouped by configured stages such as onboarding, active use, or re-engagement.
Behavioural rules
Segments can evaluate events.
Product usage rules
Eligibility can reflect configured usage of relevant features or services.
Location and attributes
Rules can use supplied location data.
Consent-aware eligibility
Consent states can be included when deciding whether a user is eligible or reachable.
Rules in, a segment out.
Connect the REST API
Connect customer systems through the REST API to supply the attributes and events permitted for audience decisions.
Define identity fields
Choose stable identifiers, attribute names, value formats, and update rules across contributing systems.
Map consent controls
Map consent records, channel preferences, and internal exclusions into the eligibility data supplied to ContentFlow.
Build audience rules
Create audience conditions, inspect expected membership logic, and publish them for use by approved content.
Who ends up on the list.
Payroll Customer Guidance
A Saudi bank could define an audience using a payroll relationship attribute supplied by its own systems.
New Wallet Users
A fintech could distinguish newly registered wallet users from established users using supplied account dates and activity events.
Eligible Renewal Groups
An insurer could define an audience for policies approaching renewal without an open cancellation request.
Only as good as its data.
Source Data Determines Quality
Accurate segmentation requires stable identifiers, current attributes, and consistent events from the customer's systems.
Compliance Remains Customer Owned
Audience controls are consent-aware, but lawful processing and regulatory compliance depend on the customer's own implementation.
Before you build one.
How current are audience memberships?
Segments are recomputed from the data available to ContentFlow, so freshness depends on how and when the source systems provide updates.
Does Audiences replace a customer data platform?
No. It applies segmentation rules to connected data but does not replace every identity, storage, governance, or data unification function of a customer data platform.
Can non-technical teams create segments?
Yes, once engineering and data teams have connected and governed the required attributes and events.
Every segment targets something.
Campaigns
Campaigns use audience membership to control who receives a scheduled content deployment.
Audiences is one of eight.
Production integration today uses the REST API. Native SDKs for React Native, iOS, Android and Web are in preview and are not generally available. The @contentflow/cli package is not published yet.