Platform Module · Activation
Turn unified profiles into precise, reusable, activation-ready audiences.
Customer 360 & Segmentation builds queryable customer profiles from resolved identity, then lets teams define behavior-aware, consent-governed segments and audiences that activate across journeys, campaigns, and media — defined once and reused everywhere.
Direct answer
Customer 360 & Segmentation is the module that maintains unified customer profiles and turns them into precise, reusable audiences. Teams build behavior-, value-, and lifecycle-based segments once, with consent enforced, and activate them across engagement journeys, campaigns, and monetization.
What it is
The module, and the problem it solves.
Customer 360 & Segmentation
A profile and audience layer on top of resolved identity. It exposes attributes, behaviors, and computed traits, and provides a segment builder that produces governed, reusable audiences with reachability and consent baked in.
Why it matters
When every team builds its own one-off lists, audiences conflict, consent is inconsistent, and nothing is reusable. Segmentation needs to sit on one governed profile so an audience means the same thing everywhere.
Who uses it
The teams that operate this module.
CRM & lifecycle
Build retention, win-back, and growth audiences.
Audience & media
Define monetizable, consent-aware audiences for activation.
Analytics
Create computed traits and value tiers.
Governance
Enforce consent and permitted-use on every audience.
How it works
From inputs to governed output.
Profile
Build queryable Customer 360 profiles from resolved identity and signals.
Define
Compose segments from behavior, transactions, lifecycle, and traits.
Govern
Apply consent, reachability, and permitted-use rules.
Activate
Publish reusable audiences to journeys, campaigns, and media.
Data inputs
What the module runs on.
Resolved profiles
Unified identities from Identity Resolution.
Behavioral events
Web, app, and product-interaction signals.
Transactions
Purchase history and value signals.
Computed traits
Scores, tiers, and lifecycle states.
Consent & reachability
Channel consent governing activation.
Operator view
What operators do here.
Build segments
Compose audiences visually from traits and behavior.
Create computed traits
Define value tiers, scores, and lifecycle states.
Manage reuse
Publish audiences once for use across the platform.
Enforce consent
Bind permitted-use and reachability to every audience.
Outputs
What the module produces.
Reusable audiences
Governed segments activated everywhere.
Profile attributes
Queryable traits for journeys and reporting.
Audience sizing
Reach and addressability per segment.
Measurement
How success is measured.
Audience reach
Consented, addressable size per segment.
Reuse rate
Audiences reused across journeys and campaigns.
Activation latency
Time from definition to live activation.
Deployment considerations
How it deploys.
Control boundary
Runs on governed profiles in your environment, with consent enforced at the audience level so activation stays compliant across channels. See Deployment and Trust & Security.
Works with the rest
This module is designed to run standalone or as part of the full Binoban operating layer. Explore the Platform overview to see how the layers connect.
Common questions
Answers for evaluators.
How does Binoban build segments?
On top of resolved Customer 360 profiles, teams compose behavior-, value-, and lifecycle-based segments with consent and reachability enforced, then reuse them across journeys, campaigns, and media.
What is the difference from Customer 360 the outcome?
The module is the engine that maintains profiles and builds audiences; the Customer 360 solution describes the business outcome of a unified customer truth. The module powers it.
Are audiences reusable?
Yes. An audience is defined once and activated everywhere, so it means the same thing across every team and channel.
See this module in your environment.
Tell us your data sources, scale, and the outcome you need. We'll map how Customer 360 & Segmentation fits your architecture and deployment model.