Back to all articlesAudience segmentation

Resolve overlapping audiences without losing the reason someone qualifies

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A contact qualifies for replenishment because of a previous purchase, accessory interest because they requested compatibility information, and product education because they have not completed onboarding. Counting that person three times inflates a combined audience total. Moving them into just one audience and deleting the other labels solves the counting problem by creating a context problem.

The better approach is to separate eligibility from primary assignment. Keep every supported reason a contact qualifies, then apply a documented priority rule wherever the business needs one exclusive audience. If no exclusive decision is needed, retain multiple memberships and report distinct contacts separately from membership counts.

This article works through that choice and provides a filled, fictional overlap decision table. It addresses audience membership and priority only—not send calendars, frequency policy, message sequencing, or delivery deduplication.

1. Decide what actually needs to be exclusive

Before removing any overlap, identify the decision that requires a single answer. A planning report might need each contact assigned to one audience so category totals add up to a distinct-contact total. An analyst investigating customer needs might need all valid memberships instead.

Those are different views of the same underlying information. They do not require competing versions of the contact record.

  • Use exclusive assignment when a defined decision requires one category per contact. Preserve the underlying eligible memberships, but select one primary audience for that decision.
  • Use retained multiple membership when the purpose is to understand all qualifying needs or interests. A contact may legitimately appear in several audience counts.
  • Use both views when teams need exclusive reporting and a complete eligibility history. Name the views clearly so nobody mistakes membership totals for people.

A useful decision statement is: “For this planning report, every eligible contact receives one primary audience. All other currently valid eligibility reasons remain available for review.” The phrase “for this planning report” matters. A primary assignment is a decision within a defined context, not a permanent description of the person.

If the team cannot explain why it needs exclusivity, do not introduce it merely to make overlap disappear. Multiple membership is not inherently a data defect.

2. Store the reason separately from the winning label

A primary label tells a reviewer which audience won. It does not explain why the contact qualified, why another audience lost, or whether the decision still makes sense.

Use a small decision record that preserves those distinctions. The following is a recommended record design, not a claim that any particular product provides these fields.

  • Contact identifier: the stable record being classified.
  • Eligible audiences: every audience whose current entry conditions are satisfied.
  • Eligibility evidence: the relevant event, date, product, or explicit preference supporting each membership.
  • Primary audience: the selected audience for the named decision context.
  • Secondary eligibility labels: valid memberships not selected as primary.
  • Decision explanation: the priority rule or documented exception that determined the outcome.
  • Evaluation details: when eligibility was checked and which rule version was applied.

Keep secondary labels specific. “Accessory interest: compatible case requested” is more useful than “other audience.” Where one contact owns several products, attach the relevant product context so evidence for one item does not silently become evidence for another.

Also distinguish currently eligible from previously eligible. Retaining reasons does not mean keeping expired memberships active indefinitely. Historical evidence can remain available while the current eligible set changes.

3. Set a priority order with explicit exceptions

A priority rule should explain a business choice, not hide one inside a filter. Start by deciding which evidence best supports the purpose of the assignment.

For the fictional example below, the team is assigning a primary audience for a customer-needs planning report. It chooses this hypothetical order:

  1. Replenishment: a consumable purchase is within the team's estimated replenishment range, with no later purchase recorded.
  2. Accessory interest: the contact has explicitly requested information about an accessory compatible with a product they own.
  3. Product education: the contact has an incomplete onboarding milestone for an owned product.

The team places replenishment first because the report prioritises an estimated recurring need. It places explicit accessory interest ahead of incomplete education because the former records an expressed interest, whereas an incomplete milestone alone does not prove the person needs help.

This order is a hypothetical business judgement, not a universal recommendation. A team focused on successful product setup might put education first. A team prioritising explicit requests might put accessory interest first. The important requirement is that reviewers can explain and reproduce the choice.

Define exception handling before applying the order. If a product association is uncertain, hold that candidate membership for review rather than treating it as established. If the contact explicitly says that setup help is their current priority, a documented override may select education while retaining the other valid memberships.

For ties within an audience, define how to retain the evidence. Two qualifying accessory requests need not become two contact memberships. Keep both reasons beneath one accessory-interest membership. If the business also needs a single product-level primary assignment, that is a separate tie-break decision and should be documented separately.

4. Use a filled overlap decision table

Fictional worked example: Every contact, event, threshold, and count in this section is hypothetical. At a single evaluation point, the team checks three audiences using the priority order above.

For this exercise, replenishment requires a consumable purchase made 45–60 days earlier with no later purchase recorded. Accessory interest requires an explicit compatibility request within the previous 30 days. Product education requires an incomplete onboarding milestone for a confirmed owned product. These are illustrative definitions, not validated buying-cycle predictions.

The compact table uses R for replenishment, A for accessory interest, and E for product education. A dash means no secondary label is retained because no other current membership qualifies.

Hypothetical overlap decision table

Contact | Eligible | Selected primary | Retained secondary labels
C-101   | R, A, E  | Replenishment    | Accessory interest; Product education
C-102   | A, E     | Accessory interest| Product education
C-103   | R, E     | Replenishment    | Product education
C-104   | E        | Product education| —
C-105   | A        | Accessory interest| —
C-106   | None     | Unassigned       | —

Evidence and decision explanations

  • C-101: Bought a consumable 52 days earlier with no later purchase recorded; requested a compatible carry case 8 days earlier; has an incomplete setup milestone for the owned device. Replenishment wins by priority. Retain “Accessory interest: carry-case compatibility request” and “Product education: setup milestone incomplete.”
  • C-102: Requested a compatible mount 6 days earlier and has an incomplete onboarding milestone. No qualifying consumable purchase exists. Accessory interest wins; retain “Product education: onboarding milestone incomplete.”
  • C-103: Bought a consumable 48 days earlier with no later purchase recorded and has an incomplete maintenance tutorial. Replenishment wins; retain “Product education: maintenance tutorial incomplete.”
  • C-104: Has a confirmed owned product and an incomplete setup milestone, with no qualifying replenishment purchase or accessory request. Product education is the only eligible audience.
  • C-105: Requested a compatible stand 12 days earlier. Education milestones are complete, and no consumable purchase qualifies. Accessory interest is the only eligible audience.
  • C-106: Has completed education, made no accessory request, and bought a consumable only 10 days earlier. None of the hypothetical conditions is met. Leave the contact unassigned rather than forcing a category.

C-101 is the critical test case. An exclusive report counts this contact once under replenishment. A membership review still shows all three qualifying reasons. Nothing about choosing a primary audience requires deleting the accessory request or education evidence.

5. Reconcile people, memberships, and primary assignments

The hypothetical table contains six contacts, but only five qualify for at least one audience. Across those five contacts, there are nine memberships: three for C-101, two each for C-102 and C-103, and one each for C-104 and C-105.

The two useful reporting views are:

  • Retained membership view: replenishment has 2 contacts, accessory interest has 3, and product education has 4. These counts sum to 9 memberships, not 9 distinct people.
  • Exclusive primary view: replenishment has 2 contacts, accessory interest has 2, and product education has 1. These counts sum to 5 assigned people.

Four of the nine memberships are secondary memberships. They are not duplicate contact records; they are additional supported classifications.

Name report columns accordingly: “Distinct eligible contacts,” “Audience memberships,” and “Primary assignments.” Avoid an unlabeled “Total audience” number that could mean any of them.

For an exclusive view, test two conditions: every assigned contact has exactly one primary audience, and that primary is present in the contact's eligible set. Then confirm that the sum of primary audience counts equals the distinct assigned-contact count. Keep unassigned and review-pending contacts visible separately rather than hiding them in a miscellaneous audience.

6. Recover when the rules or evidence change

Overlap decisions become unreliable when eligibility changes but assignments do not. Re-evaluate the primary from the current eligible set rather than treating yesterday's winner as permanent.

In the hypothetical example, a newly recorded repeat purchase would remove C-101 from replenishment under the stated rule. Accessory interest would become primary, provided the compatibility request still qualifies. Product education would remain secondary. The earlier replenishment evidence can remain historical without remaining an active membership.

Common failure cases need distinct remedies:

  • Secondary labels were deleted: rebuild eligibility from supporting records where available. Mark unsupported reasons as unknown; do not reconstruct them from memory.
  • Different teams use different priority orders: identify the decision context and rule version on each output. If both reports serve the same purpose, agree on one rule and regenerate the assignments.
  • Evidence is missing or contradictory: hold the affected candidate membership for review. Do not interpret missing data as either confirmed eligibility or confirmed ineligibility.
  • An override never expires: record its reason, owner, and review condition so it does not silently outlive the situation that justified it.
  • A priority change produces unexpected movement: compare old and proposed assignments on the same contact snapshot before adopting the new rule.

For that comparison, inspect which contacts changed primary audience and why. A rule change should produce explainable movement, not merely a different distribution of totals.

7. Review a small batch before adopting the model

Start with a hypothetical pilot of 25 contacts, including single-audience contacts, overlapping contacts, and contacts with no supported membership. This is a proposed review size, not a benchmark. Have one reviewer check evidence and another reproduce the primary assignments from the written rules.

  1. Write the purpose of the exclusive view in one sentence, or confirm that multiple membership is sufficient.
  2. Define each audience's entry and exit conditions, including how missing evidence is handled.
  3. Fill the decision table with actual internal records in an appropriately restricted workspace.
  4. Check that every eligible but non-primary audience remains visible as a secondary label.
  5. Reconcile membership counts with distinct contacts and primary assignments.
  6. Record disagreements, repair the rule wording, and rerun the same batch.

Measure the number of unexplained assignments, missing secondary reasons, and count-reconciliation failures. Also record how many decisions the second reviewer can reproduce without verbal clarification. These observations reveal whether the model is usable; a tidy audience chart alone does not.

Keep one boundary explicit: audience eligibility is not permission to contact someone. Retaining an interest label does not override an opt-out. For WhatsApp use, recipient permission and opt-outs must be handled separately in line with the current WhatsApp Business Messaging Policy.

The next practical step is to complete one overlap table for a small real batch. The result should let a reviewer answer three questions for every contact: what qualifies, which audience is primary for this decision, and which valid reasons remain available even though they did not win.

Audience segmentationCRM operationsData qualityAudience reporting

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications