Skip to content
SoundSyncAudio software platform

Guide

Create and Run an Email Campaign

Draft, preview, test, schedule, send, and reconcile recipient outcomes.

Start with getting startedExplore API docs

SoundSync

Prepare, test, and schedule

  1. Set the audience

    Choose current contacts or a saved dynamic segment; inspect consent, suppressions, product ownership, and date filters.

  2. Write the message

    Review subject, preview text, HTML/text content, links, and generated brand footer.

  3. Test delivery

    Use the saved developer support recipient and inspect sender/provider readiness. A test is not an arbitrary audience send.

  4. Choose the time

    Select send now or a schedule with its timezone. Check daylight-saving transitions; give a duplicated campaign a new intended date.

  5. 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. Subscription billing and recovery notices use Resend for the supported transactional workflow. Transactional access messages do not consume the marketing-email allowance.