Skip to content
SoundSyncAudio software platform

Guide

Email Sending Settings

Connect Brand Manager identity, verified sender, reply-to, and compliance footer.

Enablement is a readiness control

Enable developer marketing only after the sender, permitted audience, provider configuration, and required business identity are ready. An enabled checkbox is not a guarantee that a provider will accept every send.

The verified From email is managed by Brand Manager and domain setup, not by typing an arbitrary address into campaign settings. The From name and Reply-To are separate; replies should reach an inbox you monitor.

SoundSync

Keep sender identities distinct

The domain interface separates licensing, notifications and marketing sender names and reply-to settings. The captured values use example.com, not real developer or customer addresses.

Email sender identity - Example data; no live transaction or account change.

The footer comes from your brand

The locked compliance footer uses Brand Manager identity, website, support, and mailing-address details plus the unsubscribe link. Correct those source values rather than removing the footer from a campaign.

Preview the footer on both dark and light mail clients. A marketing footer is not a replacement for your storefront privacy notice or evidence of consent.

Domains are separate connections

A verified storefront domain and SSL connection do not automatically verify email sending. Follow the email-domain DNS records and verification status separately. Provider detection is guidance, not guaranteed registrar automation.

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.

Sending readiness is specific to the email purpose

Use transactionalSendingUsable and transactionalBlockingReasons for receipts/licensing notices; use marketingSendingUsable and marketingBlockingReasons for campaigns and Growth Flows. Legacy combined blockingReasons can include the other provider. A transactional-provider problem alone does not prove verified marketing sending is blocked.

marketingTrackingUsable is separate from sending. If tracking TLS is not ready, the service sets trackClicks:false and trackOpens:false. Marketing can proceed without that tracking only when the configured provider supports explicitly disabling it; otherwise sending remains blocked. A local checkbox cannot bypass provider TLS checks. This guide does not enable or change provider configuration.

Full Brand Domain readiness still requires complete DNS, website SSL, email/tracking and identity checks. A usable single sending purpose is not completion of the whole wizard. A tracking certificate must be trusted and unexpired; missing certificate status is not readiness. Email tracking is separate from GA4.

A provider lookup failure is not a missing DNS record

Read customDomain.providerReadErrors.resend and .elastic with providerVerification, lastError and lastCheckedAt. A timeout or mismatched provider domain is a lookup problem, not proof that existing DNS must be replaced. Retained prior observations are not a new verification result.

Provider reads are bounded and cached. The read helper uses GET without creating domains, starting verification or persisting provider results. Surrounding settings reads can initialize sender profiles, so the endpoint is not a zero-write health probe. Explicit prepare/refresh operations are separate writes. Keep credentials private and retry the intended status read before resetting a working domain.

Transient failures are not a permanent opt-out

Soft bounces, full mailboxes, throttling and temporary connection failures do not by themselves permanently remove a subscriber. Confirmed invalid recipients, hard bounces, complaints and unsubscribes remain blocked. Sender-account or sending-limit problems are delivery issues, not evidence that every recipient is invalid.

The delivery service can reconcile a verified temporary provider-only block when no saved customer restriction applies. It does not submit a second copy of mail already accepted by the provider. An ambiguous outcome is not permission to resend. Correcting a customer email preserves recorded classifications and saved restrictions; it does not clear an unsubscribe.

Blank names can remain blank rather than displaying an email address or inventing a customer name. Current campaign and flow reports are the source for delivery outcomes; removed historical dashboard panels are not a separate reporting feature.

Design the email customers will receive

The shared compact editor supports primary and reward emails, subject and body content, saved design and branded light/dark logos and palette. Preview uses the maintained delivery renderer, including link and background handling. Different mail clients can still render differently.

Previewing does not send, enroll contacts, change consent or consume a message allowance. Review the destination URLs, reward, sender identity and suppression-aware audience before enabling the flow. Purchases and storefront signups remain automatically enrolled in the relevant marketing list; no separate opt-in checkbox is added.

Set an optional marketing budget

Marketing has no monthly spending limit by default. The account owner can enter a USD monthly budget in Marketing Settings, use $0 to stay within the included sends, or clear the budget to return to unlimited. Usage still costs money at the published rate; unlimited is not free sending.

Campaigns and Growth Flows share the budget. Accepted and reserved sends count toward committed spend; the warning starts at 80% of a chosen budget. Lowering a budget does not undo messages already accepted by the provider. A campaign preview is an estimate, and scheduled previews use the scheduled billing month.

Billing readiness and an uncertain send are different holds

Paid marketing needs a verified billing payment method. An unpaid live SoundSync bill or temporarily unavailable billing verification can pause new marketing, including otherwise included sends. Resolve the displayed billing requirement before resuming.

An accepted send settles once. A definite pre-acceptance failure releases its reservation; an uncertain outcome stays held for review and must not be resent automatically. These marketing controls do not themselves revoke existing licenses, downloads or necessary transactional messages.