Choose the audience, then check who is still eligible to receive.
Build from a Knownry segment or explicit audience rules. Every campaign names an eligible consent class, and suppressions apply on top of any segment.
Maya Chen
Knownry profile · example data
Known identifiers
Verified through signup form
Useful context
Each attribute keeps its workspace source and recorded time.
Communication choices
In practice
Follow one send from start to finish.
- Stage 01
Select the intended group
Use a saved Knownry segment or narrow the audience by the workspace fields and history available to PostDesk.
- Stage 02
Name the permission
A campaign must use a consent class that allows campaigns, so marketing goes only to people who said yes to marketing.
- Stage 03
Apply the final exclusions
Global suppressions and the current consent state are checked again as the recipient queue is built.
At audience resolution
A segment match is checked again before it becomes a recipient.
A saved customer segment contains 842 profiles. Current consent and suppressions narrow it to an explainable launch queue, tied to the rules that built it.
- Segment
- 842 matching profiles
- Excluded
- Consent + suppressions
- Output
- Eligible recipient queue
The retained record
What stays with the audience decision
- The selected Knownry segment and campaign filters
- The consent class required for that campaign
- A snapshot of the rules used when the run began
- Individual queued recipients, including the version of the message prepared for them
Why keep it
A saved segment can change as people enter or leave it. Keeping the launch-time rules and queue makes it possible to explain why a particular recipient was considered for a particular run.
What you can rely on
A campaign starts only after Knownry confirms current marketing consent for its audience.
Next in the send
Keep following the operation.
Email studio
Reusable campaign and transactional emails.
Explore the featureBrand Profiles
Set your brand once, then start every new email on-brand.
Explore the featureCampaign runs
Review, launch, and follow each send.
Explore the featureProvider results
Delivery events tied to the message.
Explore the feature