Workflow Blueprints: Copy, Adapt, Launch

Each blueprint is production-ready and includes: start/stop conditions, audience, event payload, message personalization, timing, channels, and success metrics. Use this schema for any workflow. It maintains logical consistency, avoids overlap, and ensures results are comparable.

Start/Stop conditions

• Start when a user reaches the qualifying state/event.
• Stop at the target success event.

Audience: qualifying cohort + exclusion rules (recent converters, complainers/bounces, users in mutually exclusive lifecycle programs).

Event payload: parameters included in the start event.

📘

Note

All SDK events contain standard parameters:

• country
• externalCustomerId
• appVersion
• contactId
• locale
• deviceId
• deviceCategory
• osVersion
• appId
• osType
• occurredDate

Message personalization: Velocity variables referencing contact fields and event parameters.

Timing: when the first message goes out and how follow-ups are spaced (e.g., T+30–90m → T+24h → T+72h).

Channel mix: primary and secondary channels by funnel type (e.g., email-first for Web2App; in-app/push for Direct Install when email is absent).

As you deploy, anchor each flow to the Next Best Action — move the user one step forward at a time (Subscribe → Install → Core action #1 → Core action #2 → Core action #3 …) so small wins compound into durable retention and revenue.