Campaigns
Create, preflight, launch, pause, resume, duplicate, and analyze a bulk email campaign.
A campaign combines an audience, one or more templates, sending accounts, and a send strategy.
Create a campaign
The creation flow follows five decisions:
- Basic information: enter an internal name and the available campaign metadata.
- Recipients: choose a saved segment or import an authorized CSV/TXT audience; review deduplication and suppression matches.
- Template strategy: choose one template, rotate a selected set, or use the available enabled-template strategy.
- Send strategy: inherit the global policy or define the supported campaign-specific rate, time window, and retry behavior.
- Preflight: review domain authentication, sender readiness, unsubscribe access, suppression impact, recipient count, and content.
Resolve every blocking preflight item before launch. A warning should have a documented owner and decision.
Start safely
- Send tests to controlled inboxes across representative providers.
- Begin with a small engaged segment.
- Confirm queue rate and SMTP responses.
- Watch hard bounces, complaints, unsubscribes, and account health.
- Pause promptly if results diverge from the approved operating threshold.
Campaign states
The list can distinguish draft, queued, running, paused, throttled, error, and completed work. Available actions depend on current state.
- Pause stops new work for the selected campaign while retaining progress.
- Resume continues an eligible paused campaign.
- Duplicate creates a draft-like copy for review; recheck audience and content before starting it.
- Delete requires confirmation and should follow retention requirements.
- Export report creates a record for analysis or handoff.
Campaign detail
Use the detail view to review progress, sender and domain breakdowns, queue activity, delivery outcomes, and errors. A high-level completion percentage does not replace response-level investigation.
Imported campaign data
If the interface supports campaign CSV import, validate every imported mapping and state before enabling sending. Import is an operational convenience, not approval to send.
Next: monitor the queue and review reports.
RocketsSend Docs