Segment launch planner

Define who a message is for, decide which exclusions win, test the boundary cases and record who owns the next step. A completed worked example comes first so you can see the whole plan before editing your own.

Worked example Who remains after each rule

These are sequential counts from a worked example, not current merchant data. Each step keeps part of the step before it, so every removed group is separate and counted once. The tool cannot verify that events are complete or that anyone is eligible.

350

shoppers remain

of SMS eligible

350 shoppers remain, 7.0% of the 5,000 who are SMS eligible. 4,650 were removed across five steps, and the largest removal was at Relevant click.

Count kept and removed at each step
Step	Kept	Removed here
SMS eligible	5,000	Starting count
Relevant click	800	4,200
No later purchase	620	180
Current product or journey match	500	120
Outside recent-contact exclusion	420	80
No unresolved support issue	350	70

This is arithmetic on the counts entered. It does not approve a launch; the boundary checks and the launch owner do that work.

Audience counts

Enter the shoppers left after each rule, in order. Whole numbers only. Each count must be the same as or smaller than the one above it. The worked example is loaded; clear it before entering store numbers.

SMS eligibleCurrent SMS marketing permission on the snapshot date

Relevant clickOf those, clicked the named event and product in the window

No later purchaseOf those, no purchase of that product after the click

Current product or journey matchOf those, product still live and journey still fits

Outside recent-contact exclusionOf those, not contacted inside the contact policy window

No unresolved support issueOf those, no open case, return or complaint

Remaining 350, 7.0% of SMS eligible.

Plan Worked example text

Each field holds example text for a pack-size and ordering message about DailyMix (DM-200), an illustrative generic product. Replace it with your own decisions. Boxes grow as you type.

Message purposeThe one question this message answers for the shopper

Exact event and productEvent name and product or collection identifier as they appear in your data

Recency window, timezone and boundaryStart, end, timezone and whether each end is included

Later purchase stop conditionWhich purchase removes a shopper, and when it is checked

Support stop or defer conditionWhich open issues stop or delay the message

Cross-channel contact policyLimits across email, SMS and other channels

Overlap priorityWhich message wins when a shopper qualifies for more than one

Expected answer source and reply ownerWhere replies go, who answers and what they answer from

Launch ownerThe person who decides whether this message sends

Next reviewWhen and what you will look at after sending

Boundary checks

Test each case against the real preview before launch. Write what you actually saw, then choose a result. A pass without a written observation is counted as unresolved. A fail stays visible until you retest and change that row.

0 pass with an observation, 0 fail, 8 unresolved, of 8 checks. Unresolved checks still need a preview observation.

Boundary cases, expected outcome, observation and result
Case	Expected outcome	Actual observation	Result
Eligible matching shopper	Include	Actual observation for eligible matching shopper	Result for eligible matching shopperUnresolved.
No SMS permission	Exclude	Actual observation for no SMS permission	Result for no SMS permissionUnresolved.
Purchase after click	Exclude	Actual observation for purchase after click	Result for purchase after clickUnresolved.
Open service case	Defer until the case is closed	Actual observation for open service case	Result for open service caseUnresolved.
Competing journey	One message only, chosen by the overlap priority	Actual observation for competing journey	Result for competing journeyUnresolved.
Event at the cutoff timestamp	Included or excluded exactly as the documented window says	Actual observation for event at the cutoff timestamp	Result for event at the cutoff timestampUnresolved.
Missing product or timestamp	Review or exclude; never send by default	Actual observation for missing product or timestamp	Result for missing product or timestampUnresolved.
Permission revoked after preview	Do not send	Actual observation for permission revoked after preview	Result for permission revoked after previewUnresolved.

Passing checks are evidence for these cases only. They do not cover every shopper or approve the launch.

Definitions

SMS eligible: Shoppers with current, documented SMS marketing permission on the snapshot date.
Relevant click: Of those, shoppers who triggered the exact event and product named in the plan inside the chosen window.
No later purchase: Of those, shoppers with no purchase of that product after their click.
Current product or journey match: Of those, shoppers whose product is still live and who still fit this message rather than another journey.
Outside recent-contact exclusion: Of those, shoppers not contacted inside the cross-channel contact policy window.
No unresolved support issue: Of those, shoppers with no open support case, return or complaint.
Remaining: The last count: the audience these rules produce.
Share: Remaining divided by SMS eligible.
Removed here: The count before a step minus the count after it. Because each step keeps part of the step before, each shopper is removed at most once, and the removals add up to SMS eligible minus remaining.
Overlap priority: The written rule for which message a shopper gets when they qualify for more than one.