Guide
Growth Flows and Automation
Configure triggers, sequences, delays, eligibility, rewards, and queue visibility.
SoundSync
Template families
| Flow | Purpose |
|---|---|
| Cart recovery | Follow up on an eligible abandoned checkout |
| Review request | Invite feedback after the relevant customer event |
| Cross-sell / upsell | Recommend eligible related products |
| Product onboarding | Send product access/setup guidance |
| Promotion follow-up | Continue an eligible offer conversation |
| Winback | Reconnect with an eligible inactive audience |
| Product update | Explain a release and its change information |
| New product release | Announce a relevant launch |
| Special promotion | Prepare a selected campaign sequence |
SoundSync
Configure before activating
-
Select a trigger
Use the template's supported event, API event, or manual segment. A template existing does not mean every event source is firing.
-
Set the audience
Apply consent, suppression, product scope, ownership exclusions, and eligibility filters.
-
Design the sequence
Review each email, merge tag, delay, product link, and optional offer/reward.
-
Review timing
Use available quiet-hours, timezone, and smart-window controls. Do not assume a daily cap or cooldown is active merely because older documentation mentioned one.
-
Preview and test
Preview the selected sequence step and send its test only to the signed-in developer account. Sender and compliance-footer readiness still apply.
-
Inspect activity
Review queued, sent, failed, and delivery-unknown recipients and conversion records; pause or archive flows deliberately.
Manage the sequence without losing context
Create or duplicate a flow, review every step, activate or pause it, and use the supported manual run for its eligible audience. Reward messages and primary sequence messages are reported separately. Inspect step metrics, queue snapshot, and recipient history rather than assuming every scheduled item was delivered.
An unknown delivery outcome is not a confirmed failure. Check provider acceptance before resending. If no new audience members are eligible, running the flow does not create permission to contact suppressed or unsubscribed people.
Rewards need their own rules
Where supported, a flow can issue an eligible offer. Check scope, expiry, eligibility, stacking, and the paid-price floor. A review incentive must not depend on a positive rating or be represented as an independently verified purchase review.
An API-triggered flow must not accept arbitrary external recipients as permission to market. Trigger context and consent still apply.