Good segmentation changes a decision. A repeat buyer may need a different invitation than a first-time customer who has not received the product yet. If two groups should receive the same timing, placement, offer, and message, they probably do not need separate campaigns.
Use this playbook to choose a small set of useful customer experiences, define the data behind them, and test whether the differences matter.
Choose dimensions that change the experience
- Lifecycle
- First-time buyer, repeat buyer, active subscriber, or lapsed customer. Use this to decide when a referral request is credible.
- Value
- Purchase frequency, spend, or contribution margin over a defined period. Choose a defensible measure and a refresh schedule. High spend does not prove willingness to recommend.
- Affinity
- Product category, declared preference, or membership tier. Use this to make creative relevant without exposing private customer information in a share message.
- Advocacy
- Never shared, shared without conversion, successful advocate, or repeat advocate. This can change the instruction, reminder, and recognition the customer needs.
- Context
- Delivery, renewal, product launch, or support recovery. A timely trigger can matter more than a narrowly defined audience.
Start with the customer experience you want to change. Then find the smallest reliable set of data needed to deliver it.
Six audience examples
These are illustrative planning choices, not tested customer results. Incentives, timing, and eligibility need review against your own program economics and integration.
First purchase, after delivery
Moment: after delivery and a reasonable product-experience window. Message: a simple invitation to share the product with a friend. Keep the offer easy to explain. Suppress unresolved delivery or support issues and avoid calling a first-time customer a VIP.
Repeat buyer
Moment: a repeat purchase or account visit. Message: acknowledge the customer’s preference and use relevant category creative. Begin with the standard incentive, then test a change only if there is a clear economic reason.
High-value customer
Moment: a genuine membership or relationship milestone. Message: recognition, access, or convenience. Do not automatically increase cash value. Define the value window and eligibility so support can explain the offer consistently.
Active subscriber
Moment: a successful renewal or usage milestone. Message: the benefit the subscriber can recommend from experience. Exclude failed payments and cancellations. Confirm how subscription status changes reach the referral system.
Lapsed customer
Moment: only when the relationship still supports a recommendation. Message: a relevant reason to reconnect, not an assumption of enthusiasm. Service recovery or a winback may need to happen before a referral request.
Successful advocate
Moment: after a confirmed referral outcome. Message: thank the customer and make another share easy. Test recognition or simpler sharing before increasing rewards. Apply contact limits across the whole lifecycle program.
Write the data contract before the campaign
Each segment should have a field definition, source system, refresh schedule, owner, and fallback. Avoid sending unnecessary personal data. Use the minimum fields needed for eligibility and an appropriate customer experience.
Example: repeat-buyer segment
Definition: a customer with more than one completed, non-cancelled order in the agreed lookback period.
Source: the commerce system is authoritative for order history; the marketing platform supplies communication eligibility.
Refresh: update after a qualifying order or reversal, using a documented integration schedule.
Fallback: missing or stale values receive the general eligible experience, not a privileged reward.
Exclusions: unresolved support issues where that signal is available, disallowed accounts, and customers already assigned a higher-priority campaign.
Resolve overlap explicitly
A subscriber can also be a VIP and a successful advocate. Choose a precedence rule rather than letting whichever message fires first decide the experience.
- Apply legal, consent, fraud, and customer-service exclusions first.
- Select one eligible campaign using an agreed priority order.
- Apply contact limits across referral and lifecycle campaigns.
- Keep the offer consistent through the customer’s active referral journey.
- Log the assigned segment and campaign version for reporting and support.
Test a customer who belongs to several groups, one who changes groups, and one whose data is missing. Check that a later data update does not silently change an offer already promised.
How this maps to Talkable
Custom properties can be used in join, incentive, and placement criteria. Talkable documents that a new value overwrites a previously defined property for that user. Preserve the cohort used for an experiment in your reporting process instead of assuming a current profile value is historical evidence.
The segments documentation distinguishes reporting segments from campaign eligibility. Its SKU-based join-criteria example requires product IDs to be passed through the integration. See including product items for that data requirement. A reporting label by itself does not restrict an offer.
Prioritize segments you can operate reliably
Assess reach, advocacy likelihood, economic fit, and operational clarity. Start with a broad segment with a credible customer moment and dependable data. A complicated audience is not automatically a better audience.
- Reach: is the eligible population large enough to support a useful comparison?
- Experience: has this group had enough positive product experience to recommend?
- Economics: can the offer be funded without unacceptable discount or reward cost?
- Operations: can marketing, engineering, and support keep the rules accurate?
Measure within the segment
Compare the new experience with the existing experience inside the same eligible segment when possible. Do not compare VIP conversion with first-time-buyer conversion and attribute the difference to creative. Their starting behavior is different.
Define the primary KPI before launch, such as qualified referred customers per exposed advocate. Track participation, friend conversion, issued reward cost, returns, and contact complaints as supporting measures. Keep assignment and observation windows consistent, and leave time for approvals and returns to mature.
If a group is too small for a useful test, simplify the segmentation or treat the result as directional. Do not report a small-sample difference as a proven lift.
Copy-ready segment campaign brief
Audience: [definition, lookback window, source field, refresh owner]
Customer reason: [why this group needs a different experience]
Experience: [trigger, placement, creative, friend message, incentive]
Eligibility: [exclusions, priority, missing-data fallback, contact limits]
Implementation: [required fields, criteria, test accounts, reporting labels]
Evaluation: [comparison, primary metric, costs, observation window]
Operations: [support explanation, owner, review date, retirement rule]
Pre-launch checklist
- Confirm source values arrive correctly on real test records.
- Test eligible, excluded, overlapping, stale-data, and missing-data cases.
- Check advocate and friend copy together on desktop and mobile.
- Verify the reward matches the customer-facing promise.
- Confirm opt-outs and contact limits across channels.
- Document how to stop the campaign without confusing active participants.
Frequently asked questions
How many segments should we start with?
Start with a small number that changes actual decisions. Two broad experiences you can measure and maintain are more useful than many audiences with nearly identical offers.
Should VIP customers always get a higher reward?
No. Test recognition, access, convenience, or timing before assuming the incentive needs to be larger.
Can declared preferences help?
Yes, when they are reliable and used in a way customers understand. Preferences can inform creative without becoming confusing eligibility restrictions.
Does Talkable infer these segments automatically?
This playbook does not assume that. Define the data and criteria with your implementation owner. Available segmentation depends on the information your integration supplies and the campaign configuration.