Use Customer Intelligence context to include customers who satisfy relevant value conditions in an audience definition.
AUDIENCE MANAGER
Build the right audience
from customer context.
Pika Audience Manager brings customer attributes, transaction history, behavioral signals and rule logic together to help create reusable audiences for campaigns and journeys.
The objective is not simply to produce a customer list. It is to define, through explicit rules, which customers belong in a specific decision context and why.
RULE GROUP
01
AND / OR
CUSTOMER CONTEXT
02
AUDIENCE PREVIEW
03
WhatsApp Business API
Official Meta API
Email & SMS
Verified Channels
Pika Opportunity Engine
Daily Discovery
İYS & KVKK
Consent Verification
Rule-Based
Transaction Context
Behavioral Context
Reusable
Campaign & Journey
THE SHORT ANSWER
What is Audience Manager?
Audience Manager is Pika's rule-based segmentation layer for defining 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.
Audience Manager answers one central question:
“Which customers
should belong in the audience
for this decision?”
should belong in the audience
for this decision?”
Audience Manager is not the analytical engine that calculates customer behavior, and it is not the layer that sends the campaign. It turns calculated customer context into explicit audience rules and answers the “WHO?” between decision and action.
FROM LIST TO RULE
A customer list captures a moment. A rule defines the context.
The moment a customer list is exported, it becomes a snapshot of a specific point in time.
When a customer makes another purchase, their behavior changes or a condition no longer applies, the static list cannot explain that change by itself.
For marketing, the more important question is not only:
“Who is on the list?”
The more important question is: “Which conditions make this customer belong in this audience?”
Audience Manager defines the audience through rules before defining it through individual people.
This turns the audience from a one-time file into a customer definition that can be evaluated again.
A static list stores the result.
A rule-based audience also defines why that result exists.
AUDIENCE CONTEXT
An audience does not have to be defined by one attribute.
Audience Manager can bring different customer contexts together within the same rule definition. Available context depends on relevant customer data present in Pika.
Customer Attributes
Available customer profile and descriptive attributes can form part of audience conditions.
Transaction History
Purchase history, transaction frequency or purchases from particular products and categories can be used in audience definitions.
Behavioral Context
Behavioral change and purchasing context derived from transaction history can enrich audience rules.
Customer Intelligence Signals
Calculated value, rhythm or other relevant customer signals from Customer Intelligence can provide context for audience decisions.
Product / Category Context
Products or categories purchased by the customer can help define audiences around relevant needs or product behavior.
Permission / Reachability Context
Available permission or communication-reachability context can form part of an audience rule or downstream action evaluation where appropriate.
None of these contexts alone defines the “right audience.”
The role of Audience Manager is to combine the required context through explicit rules.
RULE LOGIC
Define the audience through explicit conditions.
Real targeting requirements rarely consist of one condition.
One customer attribute may be enough for one audience, while another audience may require several conditions to be true at the same time.
Audience Manager helps define how those conditions combine through AND / OR logic inside rule groups.
AND
Represents the part of the definition where the customer must satisfy conditions that are required together.
OR
Allows customers to be evaluated when they satisfy one of the relevant alternative conditions.
For example, an audience definition may evaluate:
A relevant product or category behavior
AND
an appropriate customer behavioral signal
AND
permission / reachability context that should be considered for action.
This example is not a fixed Pika segment.
The value of Audience Manager is that users can define their own business rules explicitly.
Define the audience not only by its name, but by the rules that create it.
DYNAMIC AUDIENCES
Instead of exporting the audience once, reuse the rule that defines it.
The value of an audience definition does not come only from the customer list it produces today.
The greater value is that the same business rule can be evaluated again later.
As customer data and behavioral context change, the same audience rule can be evaluated again.
Customers may begin to satisfy those rules or may no longer satisfy them.
“Dynamic audience”
does not mean: “every change is processed instantly and in real time.”
Dynamic here means:
membership is based on rules that can be re-evaluated rather than on a permanently fixed file.
A defined audience can later be reused across different campaign or journey workflows.
Instead of rebuilding the list, reuse the audience logic.
FROM ANALYSIS TO AUDIENCE
Customer Intelligence creates context. Audience Manager defines an audience with it.
Customer Intelligence and Audience Manager do not perform the same role.
Customer Intelligence produces calculable customer context such as value, purchase rhythm and behavioral change from transaction and behavioral history.
Audience Manager is the segmentation layer where that customer context can be used in audience rules.
Customer Intelligence:
“What is happening in this customer's behavior?”
Audience Manager:
“Which customers match this context?”
A calculated customer signal is not a campaign by itself.
Inside Audience Manager, that signal can contribute to an audience definition together with other conditions.
Customer context is calculated first.
That context can then help define who belongs in the audience.
WHAT CUSTOMERS PURCHASE IS CONTEXT TOO
An audience is defined by more than customer attributes.
What a customer purchased, which categories they transacted with and how their purchase history developed can also provide context for audience decisions.
By using transaction and purchase data in rule definitions, Audience Manager can address not only “Who is the customer?” but also “What has the customer done?”
Product Intelligence is a separate layer that establishes meaning beyond the product's catalog code.
Audience Manager and Product Intelligence are not the same product.
Product Intelligence:
“What does this product represent?”
Audience Manager:
“Which customers match this product or category behavior?”
When product meaning and customer purchase behavior are considered together, the audience can sit within stronger commercial context.
AUDIENCE ≠ PERMISSION TO SEND
Matching an audience does not mean the customer can be contacted through every channel.
Audience eligibility and communication permission are different concepts.
A customer may satisfy audience rules, while consent, reachability and channel controls still need to be evaluated for actual communication.
Available permission or reachability context can be considered within an audience definition where appropriate.
That does not mean Audience Manager replaces final pre-send consent controls.
Audience Manager answers:
“WHO?”
Consent / delivery controls separately evaluate:
“Can this action be executed through this channel?”
This distinction prevents audience logic and delivery safety from being treated as the same control.
CHECK BEFORE YOU USE THE AUDIENCE
Evaluate what the rule produces before using the audience.
Writing an audience rule and confirming that the rule produces the intended customer group are not the same thing.
Audience Manager supports previewing the rule result and evaluating the resulting audience size, giving users a control point before using the definition.
Audience preview is not a performance or conversion forecast. It helps evaluate which customer group the rule covers within the available data context.
RULE GROUP
AUDIENCE PREVIEW
RULE GROUP
CUSTOMER CONTEXT
AND / OR
AUDIENCE PREVIEW
Audience preview:
Helps validate the rule result.
It does not guarantee:
“This audience will produce a particular campaign conversion.”
Review the rule first. Use the audience next.
Define customers through rules based on relevant transaction, product or category behavior.
Evaluate appropriate signals relative to the customer's own history within audience conditions.
Create audience rules using purchase-rhythm and relevant product context.
Evaluate relevant opportunity or decision context in downstream audience workflows.
Include available permission or channel-reachability information in audience evaluation where appropriate.
FROM “WHO?” TO ACTION
Audience Manager defines the audience. Campaign and journey layers manage the action.
Audience Manager is the audience layer within Pika's decision chain.
01
INTELLIGENCE / OPPORTUNITY CONTEXT
Customer, product or opportunity context provides the reason behind the decision.
02
AUDIENCE MANAGER
Defines through rules which customers fit that decision context.
03
CAMPAIGN MANAGER
Manages the campaign and controlled delivery process for the selected audience.
04
JOURNEY MANAGER
Can connect the audience to multi-step conditions, sequence and timing logic.
05
CONTENT STUDIO
Supports preparation of the content used in communication.
06
EMAIL / SMS / WHATSAPP
Appropriate communication is executed through confirmed channels after relevant control layers.
Audience Manager:
WHO?
Campaign Manager:
WHICH CAMPAIGN / SEND?
Journey Manager:
WHICH SEQUENCE / CONDITION / TIMING?
Content Studio:
WHAT CONTENT?
Audience Manager does not send the action.
It defines the customer group for the action.
CLEAR BOUNDARIES
Put Audience Manager in the right place.
Audience Manager is not a CRM.
CRM systems may manage customer records and operational relationship processes. Audience Manager does not exist to store customer records; it creates audience rules from available customer context.
Audience Manager is not Customer Intelligence.
Customer Intelligence calculates customer behavior and produces analytical context. Audience Manager can use that context in audience rules.
Audience Manager is not Daily Opportunities.
Daily Opportunities makes commercial opportunities worth evaluating visible. Audience Manager defines which customers belong in the audience for a specific decision or action.
Audience Manager is not Campaign Manager.
Audience Manager answers “WHO?”. Campaign setup, management and controlled delivery are the separate product role of Campaign Manager.
Audience Manager is not a consent-management system.
Permission or reachability context can be considered in audience definitions, while final consent and delivery controls are managed by separate control layers.
Audience Manager is not an AI segmentation black box.
Audience definitions are based on explicit rule logic. Generative AI is not positioned as the sole source that places customers into audiences through unexplained decisions.
Audience Manager is more than a static list builder.
Audience definitions can be based on reusable rules and re-evaluated as underlying customer context changes.
The role of Audience Manager is not:
To create more customer lists. It is: To define the right customer group for a specific decision through explicit rules.
Frequently Asked Questions
What is Audience Manager?
Audience Manager is Pika's segmentation layer for defining, through customer attributes, transaction and behavioral context and explicit rules, which customers should belong in the audience for a specific marketing decision or controlled action.
What data can Audience Manager use for segmentation?
Depending on available Pika context, customer attributes, transaction history, behavioral signals, relevant calculated Customer Intelligence context, product or category purchase information and available permission or reachability information can contribute to audience rules.
What is a dynamic audience?
A dynamic audience is an audience definition whose membership is based on rules that can be re-evaluated rather than only on a one-time exported customer list. As underlying customer data or behavioral context changes, the same rules can be evaluated again.
What is the difference between Audience Manager and Customer Intelligence?
Customer Intelligence produces analytical context such as value, purchase rhythm and behavioral change from customer transaction and behavioral history. Audience Manager can use that and other customer context inside rule-based audience definitions.
What is the difference between Audience Manager and Daily Opportunities?
Daily Opportunities makes commercial opportunities worth evaluating today visible. Audience Manager defines which customers should belong in the audience for a specific decision or action.
Does Audience Manager send campaigns?
No. Audience Manager defines the audience. Campaign setup, controlled delivery, journey flow and channel execution are managed separately by Pika's relevant action and delivery layers.
Does Audience Manager guarantee communication permission?
No. Available permission or reachability information may be considered in audience rules where appropriate, but inclusion in an audience does not guarantee that communication permission is valid for execution. Pre-send consent and channel controls are separate processes.
Does Audience Manager use AI to create segments?
The core audience logic in Audience Manager is based on explicit customer data and rule definitions. Generative AI is not the sole decision source that places customers into an audience through unexplained logic.
WHO?
Define your audience
Define your audience
through context and rules,
not only through a list.
Let's explore how Pika Audience Manager combines customer attributes, transaction and behavioral context with explicit rules to help create reusable audiences.
Pricing is tailored to your requirements and scope of use.
GDPR Compliant
Enterprise Security
Dedicated Support