Review and launch a campaign
Before launching, save your group, template, landing page, sending profile, and domain. Use a test message to inspect the output in a controlled inbox.
- Create or resume a draft and select the resources.
- Choose an enabled owned public origin and any path beneath it. Verification is required only when enabled in company settings.
- Set an immediate or future schedule.
- Review the resolved audience, personalized preview, and effective tracking/redirect settings.
- Choose Launch campaign or Schedule campaign.
Check the audience
Section titled “Check the audience”The launch audience is resolved from the selected groups. Review shows the number of unique recipients, duplicate entries, and conflicts where the same address carries different attributes. First-occurrence precedence makes group order meaningful; inspect the retained details rather than assuming every group row becomes a separate message.
Revisions of the selected groups, email template, landing page and sending profile are checked at launch. If one changed after review, refresh the review so you approve the current content. Missing resources or an ineligible domain must be corrected first.
Choose Custom redirect or a reusable Learning page as the post-submission destination. The destination remains fixed after launch. See learning pages for authoring, public availability and content-edit behavior.
Check the policy
Section titled “Check the policy”Submission and password-presence tracking are always enabled. Review shows the campaign’s redirect and advisory page warnings. A launch does not enable entered-value capture. See participant data.
If the response is lost
Section titled “If the response is lost”Launching a saved draft creates the campaign transactionally. Retrying that same draft launch resolves to its existing campaign rather than creating another one. Refresh the saved draft to find the linked execution.
This launch identity does not promise exactly-once email delivery. Read delivery recovery before acting on an uncertain SMTP outcome. The legacy API has its own idempotency mechanism.