Could an operator explain why this person qualifies?

InclusionExclusionFreshnessReason to care

A useful segment answers all four. Start with declared preferences and current product state. Use inferred behavior cautiously, suppress people who already completed the action, and keep a control group when measuring incremental value.

Begin with the event, not the audience size

Write the change that makes the message useful: a saved item changed price, a followed topic has a new article, an order changed state, or a requested reminder is due. Then identify which subscriptions have both an expectation for that event and a current reason to act. “All active subscribers” is not a segment definition unless the event truly applies to everyone.

Rank signals by how well they express intent

SignalTypical strengthRisk to manage
Declared topic or alert preferenceStrong: the person explicitly selected the subject or event.Preferences can become stale; provide review and removal controls.
Saved object or tracked thresholdStrong: the message can refer to a specific requested item.Suppress after deletion, purchase, completion, or an expired object.
Current account or order stateStrong for transactional messages.Recheck state close to send time so the alert is not already obsolete.
Recent content or product behaviorModerate when the action is repeated and recent.A single page view may be accidental; apply freshness and minimum-evidence rules.
Inferred demographic or broad personaWeak unless independently validated and appropriate.Can be inaccurate, intrusive, discriminatory, or impossible to explain.

Write a segment contract

For every reusable segment, document:

  • the business and subscriber purpose;
  • the exact inclusion query in plain language;
  • exclusions for opt-out, frequency, completion, invalid endpoints, and legal or product constraints;
  • the maximum age of every behavior signal;
  • the minimum audience size needed for privacy and reliable analysis;
  • the fallback when data is missing; and
  • the owner and review date.

A label such as “likely buyer” or “high engagement” is not a contract. Another operator should be able to reproduce membership from the definition.

Re-evaluate state at send time

Audience selection and actual delivery can be separated by minutes or hours. Before queueing each endpoint, recheck the conditions most likely to change: current preference, endpoint status, purchase or task completion, stock or content state, recent sends, and whether a newer event supersedes the message. This avoids sending reminders after the action is done.

Control overlap across campaigns

One subscription may qualify for several segments. Assign message priorities and conflict rules. A requested security alert can take precedence over a promotional cooldown, while two promotional automations should not each send because they evaluated separately. Use a subscriber-level send ledger so frequency policy sees the whole channel.

Use a worked segment definition

Illustrative saved-search alert

Include active subscriptions that explicitly follow the search, have received a new matching result since their last alert, and have not opened that result. Exclude unsubscribed or invalid endpoints, people who paused the topic, and anyone at the applicable frequency cap. Require the match to remain available at send time. This example describes logic, not a claim about expected performance.

Measure incremental value with a control

Clicks among recipients show response, not causation. When audience size and risk permit, hold out a randomly selected eligible group that does not receive the message. Compare the defined downstream action over the same window. Also compare opt-outs, later engagement, and endpoint loss. A segment that creates immediate clicks but damages subscription retention may not be useful.

Keep experiment assignment stable for the measurement window and decide the primary outcome before seeing results. Avoid slicing a small audience into so many groups that ordinary variation looks meaningful.

Protect privacy and explainability

Collect only signals needed for the subscriber promise, retain them for a stated period, and restrict access. Avoid including sensitive traits in notification text or segment names. Make preference-based segments visible to the subscriber where practical. If an operator cannot explain why a person was included without exposing an uncomfortable inference, reconsider the rule.

Connect segmentation to the rest of the channel

If the team is still deciding where the Web Push platform fits, start with one requested event and one explainable audience rather than importing every available attribute. The commercial service boundary and this segmentation contract should describe the same eligibility rules.

Segmentation is only one layer. The frequency-cap framework protects attention across overlapping groups, the how to write push notifications guide turns the event into an actionable message, and the metrics guide defines honest denominators. When those rules are explicit, AI push notification drafting with human review can help operators produce variants without deciding who is eligible. MDN’s Web Push best practices provides the baseline expectation that each notification be useful and time-sensitive.