Create and Run an Email Campaign

A prepared cart is not a purchase

The link uses the configured storefront cart URL and an ss_cart query parameter containing comma-separated positive product IDs. It contains no customer session, serial, entitlement or private credential. Link creation does not apply a coupon or promise a discount; checkout recalculates current prices, offer eligibility and tax.

The customer reviews the cart and completes the normal account and checkout steps. Existing cart items are not replaced. If any selected product is unavailable or not checkout-eligible, the link adds none of its selected products and keeps the existing cart. A merge that would exceed 100 cart items is also rejected without changing that cart.

Hosted, branded and embedded storefront destinations

Use the builder-generated URL for the configured storefront, including its hosted path or custom domain. Do not replace its destination with an arbitrary website URL. Other existing query parameters can be retained, but ss_cart must appear only once.

For an embedded storefront, use the current full storefront loader and a host route that actually serves the embedded cart page. The parent forwards ss_cart to the permitted storefront frame; after successful application, the frame and parent clear the parameter to avoid replaying it on refresh. If the external site does not serve the generated cart path, use a reachable hosted storefront destination instead. Standalone page embeds are not a full cart package.

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.