Journeys
Journeys
Build, localize, dry-run, and activate lifecycle automations.
A Journey is a lifecycle automation: people enter through one or more triggers, walk a graph of steps, and either convert (goal), exit, or sit in a holdout. Nothing sends until you Start after Review is green.
Create one
Journeys → New journey:
- Template — onboarding, reactivation, nurture against a chosen
audience.
- Describe with AI — a sentence of intent; Audryo drafts a graph.
You still edit and approve.
You always land on a real canvas, not a black box.
Design, then copy, then go live
- Structure: entries, steps, goal, holdout, frequency.
- Emails: confirm every locale on every email node.
- Review checklist + dry run.
- Start. Pause anytime.
Structure approval and email confirmation are separate gates. You can accept a graph without blessing AI copy in the same click.
Canvas overview
| Step | Role |
|---|---|
| Start | Who enters and why (audience, event, field, signup, birthday) |
| One message document | |
| Wait / Wait until | Time or “until this happens” |
| If / else | Branch on field, event, or tag |
| A/B split | Random email test |
| Set field / Tag | Write the profile for later segments |
| Webhook | POST this moment to your stack |
| Exit | End with a reason |
Full behavior: Journey steps. Triggers and reentry: Triggers. Holdout, pause, dry run: Holdouts.
Ask AI
Describe a change in plain language. You review a diff. Nothing applies until you accept.
Event data in emails
When entry is an event, that event’s properties are {{ data.<key> }} for this enrollment only, snapshotted at entry. Audience triggers have no data. Details: Personalization.
Blocked is working as designed
People blocked on Insights or the runtime panel failed eligibility (consent, suppression, blocklist, unverified domain). Fix the cause; Audryo retries. Do not re-add them manually.