Campaign operations
Operate live and queued campaigns from Overview, Campaigns, and Reports.
Use this manual after a campaign exists. It covers queue monitoring, campaign actions, state changes, and report interpretation.
- Goal
- Keep campaigns moving safely while understanding throughput, failures, retries, and performance trends.
- Best for
- Operators actively sending, pausing, resuming, checking failures, or reviewing delivery trends.
- Outcome
- A cleaner daily rhythm for monitoring sends and acting on issues without guesswork.
Section 1
Read the send queue on Overview
Overview is the workspace pulse, not the deep control rail.
Surfaces
Overview
How to use it
- 01Use the send queue cards to scan active or upcoming campaigns quickly.
- 02Watch the audience label, throughput, delivered count, queued count, and any pause or failure indicators.
- 03Use Overview to decide whether you need to jump into Campaigns or Reports next.
Operator notes
- Overview is intentionally compact. For real operational action, move into Campaigns or Reports once the queue tells you something needs attention.
Section 2
Use the Campaigns rail for real actions
Campaigns is where state transitions and operational controls live.
Surfaces
Campaigns
How to use it
- 01Open Campaigns to send, pause, resume, schedule, switch route, cancel, duplicate, or delete depending on the campaign state.
- 02Use the details view when you need to inspect run history or message-level status.
- 03If a campaign is paused or partially failed, review the current scope before resuming so you know whether you are retrying failed recipients, remaining recipients, or pending ones only.
Operator notes
- Campaign actions are state-aware. If an action is unavailable, check the current campaign state instead of assuming the button is missing by mistake.
Section 3
Use Reports for trends and drill-down
Reports answers performance questions that Overview cannot.
Surfaces
Reports
How to use it
- 01Use the headline metrics to understand current delivery, bounce, open, and click posture.
- 02Switch chart perspectives when you want to compare delivery, opens, clicks, or bounces across time.
- 03Open a campaign drill-down when the top-level trend suggests a specific send needs deeper review.
Operator notes
- Reports is the place to analyze. Campaigns is the place to act. Overview is the place to notice.
Section 4
Use a simple daily operating rhythm
A predictable review loop keeps the workspace calmer than reactive jumping between screens.
Surfaces
Overview · Campaigns · Reports · Notifications
How to use it
- 01Start on Overview to scan queue state, provider health, imports, and recent activity.
- 02Move to Campaigns if anything is paused, retrying, or needs an explicit state change.
- 03Move to Reports when you need to explain performance trends or validate that a launch actually behaved as expected.
- 04Finish with Notifications for a compact audit of what changed while you were operating the rail.
Operator notes
- This rhythm usually surfaces issues earlier than waiting for a user or teammate to report them from outside the app.