RecipientTarget

RecipientTarget, often written as recipientTarget, is a term used in messaging and notification systems to describe the set of recipients to whom a message or event should be delivered. It is distinct from the message body and delivery method; it encodes who should receive the payload and under what conditions.

A RecipientTarget generally comprises a target type, identifiers, channels, and optional criteria. Target types may include user, group, role, or external audience. Identifiers specify the actual recipients, such as user IDs, email addresses, phone numbers, or group IDs. Channels indicate delivery channels (email, SMS, push, in-app). Criteria allow filtering, such as attributes (locale, opt-in status, subscription tier) and constraints (maximum count, time window).

Use cases: In a CRM, a RecipientTarget can define “VIP customers with verified emails” or “sales reps in North America after-hours.” In event-driven architectures, a target may be resolved at runtime by a policy engine to route events to appropriate services or queues. In marketing platforms, targets enable segmentation and personalized delivery.

Design and considerations: RecipientTarget should be resolved deterministically, with clear privacy and consent handling. It may be realized as a data structure, API object, or configuration stanza. Related concepts include recipient, targeting, segmentation, and delivery policy.