Do not only list customers. Define why they belong in an audience.
Pika helps combine customer attributes, transaction history, behavioral context and Customer Intelligence signals through explicit rule logic to create customer segments that can be evaluated again.
The purpose of segmentation is not only to answer “who is on the list?” but to define clearly which conditions make a customer belong in the audience.
What is customer segmentation in Pika?
Customer segmentation is the practice of defining, through explicit rules, which customers should belong in the audience for a specific marketing decision or controlled action.
Audience Manager can evaluate customer attributes, transaction and behavioral context, signals produced by Customer Intelligence and other available customer rules together.
Customer context → rule → audience → controlled action.
Define the conditions that create the audience, not only a static result.
Customer Context
Available customer attributes and Customer Intelligence context can become segmentation inputs.
Transaction & Behavior
Transaction history and available behavioral signals can participate in audience-rule context.
Rule Logic
Conditions can be combined through explicit AND / OR logic to define an audience.
Re-evaluation
When source customer context changes, the rule definition can be evaluated again to determine which customers satisfy the conditions.
A static list stores the result. A rule-based audience defines the conditions that create that result.
Audience definition is not campaign delivery.
Audience Manager answers “who?” Campaign Manager or Journey Manager manages the action; Consent Management evaluates available communication-eligibility context; and Email, SMS or WhatsApp can be used as execution channels when eligible.
Audience membership does not replace communication permission or the delivery decision.
Evaluate segmentation within the correct product responsibility.
Audience Manager's role is not to understand the customer itself, but to turn understood customer context into explicit audience rules.
Related Pika Layers & Use Cases
Frequently Asked Questions
How does customer segmentation work in Pika?
Customer Intelligence and available customer, transaction and behavioral context can be evaluated through explicit Audience Manager rules to define which customers should belong in a particular audience.
Are Audience Manager and Customer Intelligence the same thing?
No. Customer Intelligence is the analytical layer that calculates customer context. Audience Manager uses this and other available context inside explicit audience rules.
What is the difference between a static list and a rule-based audience?
A static list stores the result at a point in time. A rule-based audience defines the conditions that make a customer belong and can be evaluated again when source context changes.
Does Pika select customer segments with generative AI?
C28 makes no such claim. Audience Manager's verified public model is based on explicit rules and available customer context.
Does audience membership mean communication permission?
No. Audience membership and Consent Management communication-eligibility context are separate product responsibilities.
Does segmentation guarantee campaign success?
No. Audience definition does not guarantee conversion, sales or revenue outcomes.
Define customer context. Build explicit rules. Connect the right audience to controlled action.
Evaluate how Pika can use customer, transaction and behavioral context inside explicit audience rules using your own data structure.