Guide
Create and Run an Email Campaign
Draft, preview, test, schedule, send, and reconcile recipient outcomes.
SoundSync
Prepare, test, and schedule
-
Set the audience
Choose current contacts or a saved dynamic segment; inspect consent, suppressions, product ownership, and date filters.
-
Write the message
Review subject, preview text, HTML/text content, links, and generated brand footer.
-
Test delivery
Use the saved developer support recipient and inspect sender/provider readiness. A test is not an arbitrary audience send.
-
Choose the time
Select send now or a schedule with its timezone. Check daylight-saving transitions; give a duplicated campaign a new intended date.
-
Read the report
Separate provider acceptance, delivery, bounce, open, click, and unsubscribe events.
Keep the campaign list useful
Rename a campaign, including one already sent, without changing its historical message. Duplicate a campaign for a new send. Delete with confirmation only when it is not sending. Deletion removes the recipient report, not billing records, suppressions, or the validity of old unsubscribe links.
A scheduled deal can prepare a campaign draft; it does not authorize an automatic marketing send. Review its audience, content, and schedule separately.
Usage follows provider acceptance
Drafting, scheduling, and a skipped suppressed contact are not billed campaign sends. Provider acceptance records usage even if a later bounce occurs. Campaign test-send accounting is separate; consult the usage guide rather than assuming all tests are charged.
Retry the failed send, not the whole campaign
SoundSync automatically retries eligible failures that happened before provider acceptance, within a bounded retry policy. Retry failed sends handles the remaining safe failures without resending successful recipients.
If a connection fails after the provider may have accepted a message, its outcome needs review. An uncertain-send retry requires a separate confirmation because it can duplicate a message. Provider acceptance is not proof of inbox delivery.
Current email services
Marketing campaigns and growth-flow messages use Elastic Email. Resend delivers supported transactional messages, including account verification and security, purchase and redemption notices, licensing and activation codes, program verification, and subscription billing and recovery. Transactional messages do not consume the marketing-email allowance.
SoundSync
Campaign action errors: recover without duplicate sends
| Operation / code | Next step |
|---|---|
| send-now: CAMPAIGN_SEND_STATE_INVALID, CAMPAIGN_STATE_CHANGED | Reload the campaign. Only send from a supported current state; do not repeat a completed send. |
| send-now: CAMPAIGN_SCHEDULED_NOT_DUE | Wait for the scheduled time or deliberately change the schedule through supported controls. |
| send-now: MARKETING_AUDIENCE_EMPTY | Review the eligible audience and exclusions. Do not override suppression or unsubscribe choices. |
| test, send-now, schedule, retry-failed: MARKETING_PROVIDER_DISABLED / MARKETING_PROVIDER_LOCKED / DEVELOPER_MARKETING_DISABLED | Resolve the named sending configuration or account readiness condition. These 409 responses do not authorize bypassing a gate. |
| MARKETING_FROM_EMAIL_REQUIRED / MARKETING_REPLY_TO_REQUIRED / MARKETING_BUSINESS_ADDRESS_REQUIRED / MARKETING_BRANDING_REQUIRED | Complete the verified sender, reply-to and required business identity/footer before trying again. |
| MARKETING_SUBJECT_REQUIRED / MARKETING_CONTENT_REQUIRED | Complete the message, preview it and then deliberately retry the intended action. |
| schedule: CAMPAIGN_NOT_SCHEDULABLE; INVALID_SCHEDULED_AT / INVALID_DELIVERY_TIMEZONE | Reload state for a 409 conflict. For a 400 input error, use a future date and a valid IANA timezone. |
| resume-send: CAMPAIGN_NOT_SENDING | Reload progress. Resume is for an existing sending campaign, not a resend command. |
| retry-failed: CAMPAIGN_RETRY_STATE_INVALID | Reload. Retry supports campaigns that started sending, not a new draft or analytics repair. |
| retry-failed: CAMPAIGN_RETRY_SCOPE_INVALID / CAMPAIGN_RETRY_CONFIRMATION_REQUIRED | Use safe or uncertain scope; uncertain requires confirmUncertain:true and accepts duplicate-delivery risk. Both input errors are 400. |
| cancel: CAMPAIGN_NOT_CANCELABLE / delete: CAMPAIGN_NOT_DELETABLE | Reload current state; an active send cannot be erased by deleting its campaign. |
| test: TEST_RECIPIENT_REQUIRED | Save the developer support recipient before testing. This 400 response does not allow arbitrary bulk recipients. |
SoundSync
