Marketing guide
Email Marketing
Campaigns, contacts, growth flows, reports, sending identity, consent, and usage in one developer workspace.
SoundSync
Find the right workspace
| Tab | Responsibility |
|---|---|
| Home | Subscriber status, send activity, automation queue, and opportunities |
| Campaigns | Draft, preview, test, schedule, send, duplicate, cancel, and report |
| Contacts | Developer-scoped audience, CSV imports, segments, consent, and suppressions |
| Growth Flows | Trigger, sequence, delay, audience eligibility, and flow activity |
| Analytics | Campaign engagement, recipient outcomes, and attribution where collected |
| Settings | Marketing enablement, sender identity, reply-to, and generated compliance footer |
Purchases build your developer audience
A product purchase automatically adds the customer to that developer's marketing list for product news, related updates, and offers. Existing unsubscribe and suppression choices stay protected. Active, transactional-only, unsubscribed, and suppressed contacts mean different things; necessary receipts and security messages remain separate. Automatic enrollment does not establish affirmative consent where that is required.
Campaigns and growth flows share the monthly allowance: 1,000 marketing emails included, then $1 per started block of 1,000 additional sends. Transactional emails are included separately. See usage documentation for provider-accepted sends, exclusions, and monthly reset rules.
AI helps prepare the message
Draft generation, subject and preview-text ideas, rewrites, and promotion planning are assistance. Review product facts, links, audience, consent, and schedule yourself. AI output does not authorize a send or guarantee revenue.
SoundSync
Detailed guides
Campaigns
From audience selection to recipient reporting.
Contacts and segments
Imports, eligibility, suppression, and unsubscribe.
Growth flows
Triggers, sequences, timing, and rewards.
Settings
Brand identity and sending readiness.
Reports
Accepted sends, provider events, and delayed metrics.
Usage
Included quantities, resets, and billing.
SoundSync
Email marketing dashboard
The email workspace shows campaign totals, draft/scheduled/sent state, audience context, reports, and recent performance from the developer dashboard.
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.
Review permission before sending
When a customer purchases a product, SoundSync automatically adds them to that developer's marketing list for product news, offers, and related updates. Eligible account and serial activity can also automatically enroll contacts for the associated developer. Existing unsubscribes, complaints, and suppressions remain protected; a new purchase does not re-subscribe an opted-out customer. Marketing messages include an unsubscribe option, separate from necessary receipts, account security, and access messages. Automatic enrollment is not evidence of affirmative consent: developers must follow the consent or other permission requirements that apply to their audience and location, and must not treat their list as an unrestricted platform-wide audience.
Who can read, change and send a campaign
Campaign reads require marketing.view. Creating or editing a campaign, previewing it, duplicating it, sending a test, scheduling, sending now, resuming or canceling requires marketing.manage as well. Product Managers with view-only marketing access can inspect permitted campaigns but cannot send or change them. Both /marketing and /email-marketing API mounts enforce these checks.
Selected-product teammates can access only campaigns whose primary product and complete product-ownership audience are within their assignments. Workspace-wide audiences, negative-ownership audiences and mixed assigned/unassigned campaigns are not exposed through a matching primary product. New scoped campaign audiences are limited to assigned-product owners. AI product and scheduled-deal context must be assigned before generation; a client-supplied product list cannot expand scope.
Workspace sender-setting writes, contact imports and previews, contact-consent changes and segment archival require marketing.manage and all-products scope. Existing automation, growth-flow and bulk-suppression restrictions remain. Permissions do not bypass suppression, sending readiness, approval or provider checks.