Campaigns and audiences
Marketing teams message filtered audiences and inspect delivery and unsubscribes.
Marketing teams message filtered audiences and inspect delivery and unsubscribes.
Settings
Options, screen paths and defaults.
Browse this area
Marketing — modules and detailed settings
Where to find it
Web: open Marketing. Desktop: Business → Marketing, using the same record paths. Disabled modules or missing read permission remove the navigation entry.
| Screen / tab | Web path | Usage | Desktop |
|---|---|---|---|
| Campaigns | /campaigns | List, view or tab | Native screen |
| Audiences | /campaigns/audiences | List, view or tab | Native screen |
| Unsubscribes | /campaigns/unsubscribes | List, view or tab | Native screen |
| Record details | /campaigns/[id] | Record or editor | Native screen |
| Record details | /campaigns/[id]/design | Record or editor | Native screen |
Start working
Step 1
Create a customer/tag audience.
Step 2
Choose campaign, audience and channel.
Step 3
Design text/email blocks and review a test.
Step 4
Schedule/start or stop.
Step 5
Inspect recipients, opens/clicks and unsubscribes.
Settings
Option-by-option configuration and screen paths: Settings guide.
- Campaigns ·
/settings/campaigns
Permissions and limits
Before you start
Pace is 1–500 messages/minute. Tracking applies to designed block emails. Image blocking makes opens a lower bound. Sender details belong to the notification email channel.
Role capabilities: Read (read), Write (write), Delete/archive (delete), Manage (manage), Handle automated delivery/jobs (handle), Export (export), Comment (comment).
Own-record restrictions apply equally to lists, records and Era. Record state or missing data can refuse an otherwise permitted action.
Ask Era
Draft a VIP campaign and show recipients/copy first.
Select relevant records for Era context. Era respects modules/roles; external or confirmation-sensitive work can stop for approval. Use era tools in the terminal to inspect currently available tools.
Automation and events
These declared events are available to module-event triggers. Subscribing does not configure the next operation; choose recipients, conditions and actions separately.
Operation details
The inventory includes record, configuration, visitor and background flows. IDs support Era/automation; not every row is a menu button. Asterisks mark required inputs. Unmapped rows do not imply a visible control.
| Operation and ID | Inputs | Permission | Screen or flow |
|---|---|---|---|
Create an audience · campaigns.create_audience | — | Write | /campaigns/audiences |
Edit an audience · campaigns.update_audience | Audience *, Name, Description, Match, Rules | Write | /campaigns/audiences |
Delete an audience · campaigns.delete_audience | Audience * | Delete/archive | /campaigns/audiences |
Draft a campaign · campaigns.create | — | Write | /campaigns, /creative |
Edit a campaign · campaigns.update | Campaign *, Name, Send by, Format, Subject, Subject B (A/B test), Preview line, Message, Email blocks, Audience | Write | /campaigns, /campaigns/[id], /campaigns/[id]/design, /creative |
Delete a draft campaign · campaigns.delete | Campaign * | Delete/archive | /campaigns/[id] |
Send a test · campaigns.send_test | Campaign *, Send to *, Subject | Write | /campaigns/[id] |
Schedule or send · campaigns.schedule | Campaign *, Send at | Write | /campaigns/[id] |
Back to draft · campaigns.unschedule | Campaign * | Write | /campaigns/[id] |
Stop sending · campaigns.cancel | Campaign * | Write | /campaigns/[id] |
Start a due campaign · campaigns.start | Campaign * | Handle automated delivery/jobs | Background routine |
Record a sent batch · campaigns.record_batch | Campaign *, Entries * | Handle automated delivery/jobs | Background routine |
Unsubscribe an address · campaigns.unsubscribe | Link token, Email, Phone, Reason | Write | /campaigns/unsubscribes |
Take off the unsubscribe list · campaigns.resubscribe | Email or phone * | Manage | /campaigns/unsubscribes |
Stop campaign messages to me · campaigns.unsubscribe_me | — | Write | Record/API/visitor flow; no separate screen button mapped |
Send me campaign messages again · campaigns.resubscribe_me | — | Write | Record/API/visitor flow; no separate screen button mapped |
Related guides
Settings
Options, screen paths and defaults.
Workflows
Operations managers connect triggered blocks on a canvas with conditions, loops and approval waits.
Marketing
Marketing — modules and detailed settings
Technical sources
packages/os-kernel/src/modules/campaigns.ts, packages/os-kernel/src/modules/index.ts, apps/studio/lib/os/navigation.ts, apps/studio/lib/os/settings-groups.ts, apps/era-station/apps/web/src/era/business/screens.ts.