Stopping a sales tunnel branch after payment and redirecting the subscriber
UA | US | RU |
|---|
1. Introduction
When using multiple parallel branches of a sales tunnel, you may need to stop one branch after a purchase is made in another. This is important to prevent subscribers from receiving repeated offers after payment — which causes negative reactions. After a payment or a missed purchase, you can also automatically redirect a subscriber to a different branch or tunnel.
From this guide you will learn:
how to stop another tunnel branch after payment;
how to automatically redirect a subscriber to another branch after payment;
how to send a subscriber to a different tunnel if no purchase was made.
2. Key terms
Term | Definition |
|---|---|
Tunnel branch | A parallel sequence of blocks within one sales tunnel, running independently of other branches. |
Action block | The red block in the tunnel builder. Performs defined actions on other blocks or the subscriber: stop, start, redirect, etc. |
Stop action | Stops message delivery for a specific block or tunnel branch. |
Start action | Launches another branch or tunnel for the subscriber. |
Trigger block | Monitors an event (e.g. an offer purchase). Has two outputs: if the event occurred and if it did not (with a wait). Default wait delay — 365 days. |
Delay block | Postpones delivery of the next block by a specified amount of time. |
3. Feature overview
Below are three typical scenarios for managing tunnel branches after payment or a missed purchase.
3.1. Stopping another branch after payment
There are 2 tunnel branches. The top branch needs to stop sending content once the subscriber makes a purchase in the bottom branch (in the Block 1 block).
For this setup, use the Action block (red block). In the action block named «New block», set the action Stop on the delay block named «delay1».
3.2. Stopping a branch and redirecting to another after payment
After payment, you can simultaneously stop the top branch and send the subscriber to another tunnel branch. This is also configured through the Action block: one action — Stop for the current branch, another — Start for the new one.
3.3. Redirecting to another tunnel if no purchase was made
If the subscriber has not made a purchase within the specified time, they can be automatically redirected to a different sales tunnel. Use the Action block connected to the red output of the trigger block (condition: «purchase did not occur»).
Note: the wait time in the Trigger block must be set explicitly — the default delay is 365 days.
After configuring the trigger, set up the Action block with the Start action — following the same approach as the examples above.
Note: the examples above are not a reference or optimal business model for a sales tunnel — they are a brief description of the feature with specific use cases.
4. Related guides
Guide | Purpose |
|---|---|
Overview of tunnels: structure, how they work, block types. | |
What happens when editing a running tunnel: block content and structure. |