Get started
Types of emails
Campaign, Journey, or transactional — pick the right one in a minute.
Audryo sends three kinds of email. The right choice depends on one question: what causes the email to be sent?
| Campaign | Journey | Transactional | |
|---|---|---|---|
| Sent because | You decide to send now or at a set time | A person qualifies — joins an audience, triggers an event | Your product calls the API for one person |
| Recipients | Everyone in an audience at send time | Each person individually, over time | One person per call |
| Typical emails | Newsletter, launch, announcement | Onboarding, trial ending, win-back | Receipt, invite, password reset |
| Needs marketing consent | Yes, for marketing content | Yes, for marketing content | No, but suppressions still apply |
| Measures lift vs. holdout | No | Yes | No |
| Guide | Campaigns | Journeys | Transactional |
Quick decision
- "Tell this whole group something today" → campaign
- "Guide each new user through their first week" → Journey
- "This person just did something and expects an email" → transactional
Examples
| Scenario | Type | Why |
|---|---|---|
| Monthly product newsletter | Campaign | Same message, one moment, whole audience |
| Welcome series after signup | Journey | Starts per person, several emails over days |
| "Your trial ends in 3 days" | Journey | Timed to each person's trial |
| Order confirmation | Transactional | Triggered by one purchase |
| Black Friday offer | Campaign | Promotional, one date |
| "Come back" email after 30 days inactive | Journey | Triggered by behavior, measurable against a holdout |
Communication class
Every campaign and Journey has a communication class. It decides which checks Audryo runs for each recipient right before sending.
Pick it under Type when you create a campaign, or in the Journey settings. The campaign form shows right away how many people in the audience can receive that type. You do not need consent rules in the audience itself: the audience says who you mean, the type filters who may get it.
| Class | Content | Consent needed | Stopped by unsubscribe | Stopped by bounce, complaint, block |
|---|---|---|---|---|
marketing | Promotions, upsell, win-back | Yes, marketing | Yes | Yes |
newsletter | Regular editorial updates | Yes, newsletter | Yes | Yes |
product_service | Updates about the product they use: new features, onboarding tips, usage summaries | No | Yes | Yes |
operational | Account notices that are not promotional: security alerts, policy changes, billing problems | No | No | Yes |
transactional | Direct response to an action: receipts, password resets, invites | No | No | Yes |
How the check works
For every recipient and every send, Audryo checks in this order:
- Suppression. A suppression for all email (bounce, complaint, manual hold, blocklist) stops every class. An unsubscribe from marketing email stops
marketing,newsletterandproduct_service. - Consent. Only for
marketingandnewsletter: the latest consent event for that purpose must be a grant. No record, or a revocation, means the email is skipped. - Mailing list. If the email is attached to a mailing list topic, the contact must be subscribed to it.
That is why Record consent only offers *Marketing* and *Newsletter*: the other classes never look at consent. product_service relies on the existing customer relationship instead, but anyone who unsubscribes stops getting it. Every email except transactional carries an unsubscribe link.
One editor for all three
All types use the same editor and the same draft-and-publish flow. An email can even be reused: a published library email can go into a campaign and a Journey.