Before you start
Growth workflow docs are marked Preview while the API reference for every growth surface is completed. Use these pages to configure growth from the Lamba console, consume public events, and keep campaign, loyalty, notification, and analytics work tied to the same identity model as auth.
What you build
Lamba growth workflows connect identity facts to product growth actions:
| Source fact | Growth use |
|---|---|
| Lamba User | Account continuity across projects |
| Project membership | Audience eligibility and access-aware messaging |
| Session activity | Activation, return, and security context |
| Webhook events | Downstream automation and reconciliation |
| Plan limits | Campaign, notification, loyalty, and analytics boundaries |
Implementation steps
1) Configure growth in the console
Use the selected Workspace, Project, and environment before creating segments, campaigns, loyalty workflows, notifications, or analytics exports. Keep sandbox experiments out of production audiences and reports.
2) Keep identity as the source of truth
Segments, campaigns, loyalty, analytics, and notifications should reference the same Lamba User and Project context used by auth and access control.
3) Choose event-driven integration
Use webhook and audit events for downstream workflows. Public events such as campaign.sent and sms.sent should be treated as immutable facts and deduplicated by event ID.
4) Apply plan-aware limits
Campaigns, loyalty, notification channels, analytics export, retention, and usage limits should render current plan boundaries clearly.
5) Separate sandbox and production
Growth tests should not affect production audiences, usage, or audit history.
API coverage note
Use the Customer API reference for documented public endpoints. When a growth workflow is described before a dedicated public API page exists, configure it through the Lamba console and rely on webhooks, audit events, and plan-limit responses for integration.
Security and operational notes
- Avoid sending lifecycle messages to users whose membership or session state no longer qualifies.
- Keep consent and unsubscribe decisions in the channel system that owns delivery.
- Log campaign, notification, and loyalty actions with Project and environment context.
Related docs
- Segments and Audiences:
/docs/growth/segments-audiences - Campaigns:
/docs/growth/campaigns - Loyalty:
/docs/growth/loyalty - Webhook Events:
/docs/reference/webhook-events