Growth Flows and Automation

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.

Follow the recipient through the flow

Use the individual flow workspace to configure triggers, sequences, delays, quiet hours, eligibility, suppression, tests, queue activity, and reports. Supported families include cart, review, cross-sell/upsell, onboarding, promotion follow-up, Winback, updates, new releases, and special promotions.

Recipient rows show the relevant cart or recommended product when known. Use Check delivery to persist a provider-outcome review. Failed recipients can be retried when eligible; uncertain outcomes stay under review rather than being blindly resent. Serial-redemption events can feed supported flows, while historical backfill is reviewed rather than treated as a fresh automatic send.

One bundle purchase, one review invitation

A configured review flow can send one consolidated invitation for a bundle purchase. The customer chooses an eligible included product to review; SoundSync does not send a separate invitation for every member or create a new whole-bundle rating from those reviews.

A review reward is issued at most once per eligible invitation, after a qualifying sent invitation and approved product review. Creating a flow or submitting any review is not a guarantee of a reward.

Recover an unconfirmed send deliberately

Check delivery first. A confirmed provider acceptance marks the recipient sent without sending it again. A known failed, unsent recipient uses the ordinary retry action.

Retry unconfirmed is a separate guarded action. It requires a complete unconfirmed provider-history review at least 125 minutes after the recorded attempt, no provider message or transaction ID, no sent/opened/clicked activity, and an active flow. The request reviews the outcome again before requeueing; changed or incomplete evidence leaves it on hold.

Explicitly acknowledge the risk of a duplicate message. Provider history can be incomplete even when no matching event was found. Consent, suppression and queue eligibility are checked again before a queued retry sends.

Read Growth Flow reporting in the selected range

Choose a day window or All time. GET /api/developer/marketing/growth-flows/summary?range=all returns range:"all" and rangeDays:null. A bounded report returns range:"days" and an integer rangeDays; the default is 30 days. The list endpoint also accepts range=all. The ordinary flow list hides archived flows.

Archiving stops a flow from appearing in the ordinary list without erasing its history. Summary totals include archived activity; totalFlows includes that history, while activeFlows counts active entries. archivedFlows and archivedActivity identify the archived contribution. Do not expect summing only the visible flow cards to reproduce every historical total.

emailsSent, conversions and revenue use the selected reporting window. queuedNow, sentTotal, failedTotal and unresolvedTotal are current queue-lifecycle snapshots, with queueSnapshotAt showing when they were read. They are not alternative names for the ranged send count.