> For the complete documentation index, see [llms.txt](https://help.usejimo.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usejimo.com/docs/build/actions/chain-experiences.md).

# Chain experiences

Show a second experience once users are done with the first one, at once on a click, without losing users who skip the click.

Chaining shows a second experience once users are done with the first one: a second checklist once the first one is completed, a survey after a tour, a tour after a checklist. The same pattern works for any experience type.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2Fa2YLoJudlusVjgpqvsmY%2Fexperience-links-17-journey.png?alt=media&amp;token=815b8a9c-0683-42c8-acf6-aeee6e2d974e" alt="A journey of linked experiences: a Resource Center embeds a checklist, a checklist task launches a tour, the tour launches two modals, and an NPS answer launches the same follow-up modal."><figcaption></figcaption></figure>

## When to chain

Chain two experiences when the second one only makes sense after the first: an advanced setup after the basics, a second product after the first one, feedback after a tour.

## Two methods

| Method                                  | How it works                                                                           | When the second experience shows     |
| --------------------------------------- | -------------------------------------------------------------------------------------- | ------------------------------------ |
| Launch experience on the closing button | The button that ends the first experience launches the second one                      | At once, when users click the button |
| Audience                                | The second experience shows on page load and targets users who have seen the first one | On the next page load                |

Each method misses a case on its own. The button misses users who leave the first experience without clicking it and simply reload the page. The audience alone makes users wait for the next page load.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FZnDlXNZCNhOd4wFXbqjX%2Fexperience-links-18-chain-methods.png?alt=media&amp;token=f24f243b-c263-43ec-868d-4b4cae929573" alt="Two ways to chain: Launch experience on the closing button shows the second experience at once but misses users who reload without clicking. An audience on the second experience shows it on the next page load. Use both."><figcaption></figcaption></figure>

## Use both

We recommend both. The transition is instant when users click the button, and the audience still catches users who skip it.

{% stepper %}
{% step %}

### Add Launch experience to the closing button

In the first experience, select the button that ends it: the button of a checklist's completion step, or the last button of a tour. In **Behavior**, choose **Launch experience**, then pick the second experience in the **Start experience** picker.
{% endstep %}

{% step %}

### Target the second experience

Set the second experience to show on page load, on the same pages as the first one, for users who have seen the first one. This is the one case where the second experience keeps On page opening rather than No automatic trigger: users who skip the button still see it on their next page load. If you only want the click, use No automatic trigger. See [Who: target the right users](https://help.usejimo.com/docs/publish/target-right-people-who.md).
{% endstep %}

{% step %}

### Publish the second experience first

A link to a draft experience blocks publishing. Publish the second experience, then the first one, or the changes to it.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FJbUT5cYfIQtQVOrYtcfx%2Fexperience-links-19-publish-order.png?alt=media&amp;token=bcf7edc7-9723-4195-bac7-cfb378f8b24e" alt="Publish the second experience, then the first one, and the link turns green. The other way round, the link points at a draft and publishing the first experience is blocked."><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Check the chain

Open the first experience in the builder. The closing button shows a port. Click it to unfold the link, and check that it is green.
{% endstep %}
{% endstepper %}

## Check the chain with experience links

The builder draws every link around the experience you are editing. The colour of a link tells you whether the second experience will launch:

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FccSVeaa5hYNE55hZ9pxW%2Fexperience-links-02-link-health.png?alt=media&amp;token=13af62ec-bb55-4d75-a2a1-fd78d14982f3" alt="Four links from a button: green for live, grey for paused or draft, yellow for scheduled or expired, red and dashed for a deleted experience."><figcaption></figcaption></figure>

| Colour      | Target state         | What happens for your users                           |
| ----------- | -------------------- | ----------------------------------------------------- |
| Green       | Live                 | The target launches, if the user matches its audience |
| Grey        | Paused or draft      | Nothing launches until the target is live             |
| Yellow      | Scheduled or expired | Nothing launches until the target is live             |
| Red, dashed | Deleted              | Nothing launches                                      |

Every link that won't work is also listed in the **Target & publish** issues, with the button, task or trigger that holds it. Click a row to go to it.

{% hint style="warning" %}
A link to a target that won't launch still ends the experience users are in. The current tour or checklist closes and nothing replaces it. Check the colour of every link in the chain before you publish.
{% endhint %}

## From your assistant

An AI assistant connected through the [Jimo MCP](https://help.usejimo.com/docs/integrations/mcp.md) can set the closing button for you:

> Make the Finish button of the tour "Onboarding" launch the checklist "Advanced setup".

The link it creates shows up in the builder like the others: open the first experience and check that it is green. More prompts in [What to ask](https://help.usejimo.com/docs/integrations/mcp/what-to-ask.md).

## Good to know

* Launching an experience closes the one the user was in.
* When the button launches the second experience, only its Who is checked: its Where and When apply to the page load method, not to the click.
* A button launches one experience at most.
* Pausing, unpublishing or deleting the second experience never removes the link. Check the chain again after you change its state.

## Related

* [Experience links](https://help.usejimo.com/docs/build/actions/experience-links.md): read the links in the builder, link health and publishing rules.
* [Available Actions](https://help.usejimo.com/docs/build/actions/available-actions.md): the Launch experience action.
* [Checklists behavior](https://help.usejimo.com/docs/experiences/checklists/behavior.md): the completion step and its button.
