Guide
Contacts, Segments, and Marketing Choices
Purchases automatically build the developer marketing list; segments, unsubscribes, and suppressions govern the audience.
Read contact status before targeting
Active subscribers, transactional-only contacts, unsubscribed contacts, and suppressed contacts are separate categories. A purchase or entitlement can identify a customer without permission to market to them. Platform-wide customers are not an unrestricted contact list for individual developers.
SoundSync
Preview eligible existing owners for a flow
The historical enrollment dialog explains eligible previous customers, the minimum wait and the configured sequence timing. This example does not enroll or email anyone.
SoundSync
Import and segment
-
Prepare the CSV
Use the provided sample format. Include only records you are permitted to process and contact.
-
Preview first
Review valid/invalid rows, existing contacts, and consent treatment before applying the import. An imported flag cannot manufacture consent.
-
Estimate the audience
Use segment/product filters and the audience estimator to see who is eligible, not just how many records exist.
-
Maintain segments
Create or edit saved segments for the intended campaign. Product interest and ownership must remain within your permitted scope.
-
Suppress when needed
Use individual or bulk suppression to prevent future marketing, and preserve unsubscribe choices across imports.
Unsubscribe and provider failures
Unsubscribe prevents further marketing use. Bounce, complaint, or invalid-address events can suppress a recipient. Do not remove a suppression to retry a campaign without resolving the reason and confirming permission.
Minimal suppression/consent records may need to remain after other contact information is deleted so the system can continue honoring the choice.
SoundSync
Build a segment from current information
| Filter | Interpretation |
|---|---|
| Product ownership | Qualifying ownership can include eligible serial claims; browsing interest alone is not ownership. |
| Purchase date | The date constraint applies to the same qualifying purchase, not an unrelated order. Invalid date filters are rejected. |
| No opens / no clicks | No recorded engagement in the chosen window, not proof that a person did not read a message. |
| Minimum sends | The configured minimum is a lifetime send-count condition. |
| Inactive-contact exclusion | A separate exclusion action requires fresh provider history; matching a saved segment alone does not authorize suppression. |
Segments are dynamic
Saved segment rules are evaluated against current contact and activity data. Membership can change before the next send. Review the current recipient count and sampled eligibility rather than treating a segment as a frozen exported list.
Contact records and marketing permission
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.
SoundSync
Product ownership matching
| Choice | Selection |
|---|---|
| productMatch:any | Matches customers owning at least one selected product. |
| productMatch:all | Matches customers owning every selected product. |
| Does not own | Uses the corresponding inverse ownership test; review the audience estimate with the same product set and match mode. |
| Before sending | An estimate is not a fixed recipient entitlement. Eligibility and suppression are checked again for delivery. |
Duplicate a campaign without sending it twice
Duplicating a campaign keeps its earlier campaign links. The Already sent the original campaign control excludes recipients whose earlier delivery was accepted, is still queued or sending, or has an uncertain outcome. A confirmed failure before provider acceptance can remain eligible. The audience estimate, send snapshot and delivery worker apply the exclusion.
A known customer relationship stays linked to its earlier delivery history even when its contact email is corrected. Matching stays inside the same developer workspace. Email-only contacts still use their recorded addresses; names are never used to guess that two contacts are the same person.
Review the linked campaigns before sending. You can deliberately turn the exclusion off in the duplicate; saved unsubscribes, complaints, hard bounces and other restrictions still apply. Editing the control refreshes the audience estimate. Duplicating a campaign does not itself send mail.
Automatic enrollment and sending permission
Purchases and eligible storefront signups automatically add contacts to the relevant developer marketing list. These automatic account and purchase flows do not currently offer a separate marketing opt-out at collection. Saved unsubscribes, complaints and suppressions remain protected; necessary service messages are separate from marketing.
Being on a list does not establish affirmative consent or permission for every audience or location. A later unsubscribe link is not evidence that a choice was offered when details were collected. Before sending where permission or a collection-time choice is required, establish the applicable permission and keep its evidence. Automatic enrollment is not a promise of universal marketing-law compliance.
SoundSync
Marketing contacts and exclusions
Recover delivery problems without clearing customer choices
Verified historical temporary or sender-side failures can be distinguished from permanent recipient restrictions. A full mailbox, deferral or sender configuration failure is not automatically a customer unsubscribe. Unknown failures, invalid recipients, hard bounces, complaints and opt-outs stay protected; a later purchase must not erase them.
The eligibility read does not itself rewrite a contact. An ordinary eligible activity/enrollment write may clear a proven stale recoverable provider restriction after all identity and historical checks pass. Sender-side failures also have operational notices. Recovery does not resend an already accepted message, guarantee inbox delivery or change automatic enrollment policy.
A slow count must not lose your draft
Campaign creation, duplication and draft saves can retain a valid draft when its optional audience estimate times out. audienceEstimateStatus:unavailable means the count is unavailable, not that the audience is empty. Refresh the count before sending. Scheduling and sending retain fresh eligibility, suppression, sender and funding checks; a saved draft is never send approval.
