Sequences

Control the order and timing of notifications across channels with channel sequencing.

Sequences let you define the order in which notification channels fire and the conditions that stop the sequence early. Instead of broadcasting the same message across all channels simultaneously, you deliver in a prioritised chain where each step waits for a result before deciding whether to proceed.

Why use sequences

• Reduce cost. Start with low-cost channels (in-app feed) and only escalate to higher-cost channels (push) when the user has not engaged.
• Improve deliverability. Target the channel most likely to reach the user based on their prior engagement pattern.
• Avoid notification fatigue. Stop the chain as soon as the user has seen or acted on the message, rather than hitting them on every channel.

How it works

Sequences are configured at the template level. When you create or edit a template in the Dashboard:

1. Add two or more channels to the template.
2. Enable the Sequence toggle in the template settings (config.sequenceEnabled = true).
3. Arrange the channels in the desired delivery order. The first channel fires immediately at send time.
4. For each subsequent step, configure:
   • Stop condition. The engagement signal that halts the sequence: delivered, viewed, or clicked.
   • Wait window. How long to wait for the stop condition before moving to the next step: 5, 10, 30, 60, 240, or 1440 minutes.

If the stop condition is met within the wait window, the remaining steps are skipped. If the window expires without the condition being met, the next channel fires.

Example

A template with two channels configured as a sequence:

Step	Channel	Stop condition	Wait
1	In-app	delivered	30 min
2	Push	(terminal)	n/a

At send time, the in-app notification is dispatched immediately. If the item is marked delivered within 30 minutes, the sequence stops and push is never sent. If 30 minutes pass without a delivery signal, push fires as a fallback.

Metrics

When a template uses sequencing, per-step delivery metrics are available through the Dashboard and the analytics API. Which metrics are reported depends on the channel:

Channel	Requested	Delivered	Viewed	Clicked
In-app	✓	✓	✓	✓
Push	✓	✓	n/a	✓

Viewed is in-app only. Push notifications do not emit a viewed signal because there is no in-feed render to scroll into view; use Clicked to gauge engagement on the push step.

These metrics help you evaluate whether your sequence order and wait windows are tuned correctly, and where users are dropping off.

Limitations

• Sequences require at least two channels on the template.
• The stop condition applies per step, not globally. A clicked on step 1 stops the chain, but a delivered on step 1 only stops if delivered is the configured condition for that step.
• Wait windows are fixed increments (5, 10, 30, 60, 240, 1440 minutes). Custom durations are not supported.
• Sequences are not available for CSV-batch campaigns in the current release. They apply to transactional sends and scheduled campaigns.