# Journey builder for behavior-triggered campaigns

> Product · Orchestration

Design multi-step flows with triggers, waits, branches, and channel steps — visual and no-code for growth, with approvals when brand needs a checkpoint.

Canonical URL: https://tappd.io/product/journeys

## The problem

One-off pushes don’t compound. Spreadsheet “campaign calendars” miss the user who abandoned mid-checkout at 2am. Engineering-built state machines work — until the third edge case and the next hire can’t edit them.

## How Tappd helps

Tappd’s journey canvas turns product behavior into durable campaigns: start from an event or segment, wait, branch, message, webhook, and exit when the outcome hits. Growth ships the logic; engineers keep the SDK stable.

## At a glance

- **No-code** — Visual canvas
- **Multi-step** — Waits & branches
- **Human** — Optional approvals

## Capabilities

### Triggers that match product reality

Start from segment entry, custom events, or schedules. The same events your app already emits become campaign fuel.

### Logic without a ticket queue

Waits, conditions, and branches keep each user on the path that matches their behavior — edited in the UI, not a redeploy.

### Channel steps in one flow

Push and in-app today, webhooks for your stack, email coming soon — sequenced in a single journey instead of three tools.

### Approvals where it matters

Pause on steps that need a human before send. Ship fast on routine nudges; gate the offer that touches brand or pricing.

### Exit on the outcome

When the user converts — first action, purchase, re-open — leave the journey so you don’t keep pinging winners.

### Iterate from analytics

See where people stall. Fix the step, not the entire program. No overnight batch redesign to test a new wait.

## Example: cart recovery in four nodes

A shopper adds items, hits checkout, and leaves. You want a fast push, then an in-app offer if they return without buying.

### 1. Trigger

Event: checkout_started. Wait 45 minutes. If order_completed, exit.

### 2. Push

Send a reminder with cart deep link. Respect quiet hours and frequency caps.

### 3. Branch

If they open the app within 4 hours without purchasing, show an in-app offer card.

### 4. Close the loop

On order_completed, exit and attribute revenue to the journey in analytics.

## Who it’s for

- Lifecycle marketers who think in flows, not blasts
- Growth PMs partnering with mobile engineering
- Teams escaping brittle homegrown orchestration

## FAQ

### Do I need engineers to change a journey?

No. After the SDK is installed, growth and product teams can build and publish journeys. Approvals are optional for sensitive steps.

### Can journeys call my backend?

Yes — webhook steps let you notify your systems when a user hits a milestone in the flow.

### How is this different from a push scheduler?

Schedulers send on a clock. Journeys react to behavior, wait, branch, and stop when the outcome happens — across push and in-app together.

## Related

- [Push & in-app](https://tappd.io/product/push-in-app)
- [Cart recovery](https://tappd.io/solutions/cart-recovery)
- [Agent Studio](https://tappd.io/product/agent-studio)

---

[Get started](https://tappd.io/) · [Contact sales](https://tappd.io/sales) · [Docs](https://docs.tappd.io)