> 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/publish/trigger-on-the-right-spot-show-on.md).

# Show on: trigger at the right moment

Pick what starts an experience: opening a page, leaving it, an event, a shared link, your own code, or another experience.

**Show on** is the trigger: the moment an experience starts for a user who matches the other settings. It is the first section of Target & Publish, and it decides whether Where, Who and When apply at all.

**You will have at the end:** the right trigger for your case, and no confusion between No automatic trigger and On manual trigger.

***

## Which trigger for which case

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FnlHZ0ytyiNS4r8MdH7oY%2FB-02-trigger-decision-tree.png?alt=media" alt="Decision tree: started by another experience leads to No automatic trigger, by your code to On manual trigger, by a link you send to On shared URL; otherwise the user arrives (On page opening), leaves (On page leaving) or acts (On event)"><figcaption></figcaption></figure>

| You want it to start                                               | Trigger                                     | Typical use                                                                                              |
| ------------------------------------------------------------------ | ------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| When users arrive on a page                                        | **On page opening**, with an optional delay | Welcome message, feature announcement, a tip every user should see                                       |
| When users are about to leave the page                             | **On page leaving**                         | Exit survey, last help offer                                                                             |
| When users click an element, an element appears, a field is filled | **On event**                                | Help at the moment of use, a view in a single-page app                                                   |
| When users open a link you sent them                               | **On shared URL**                           | Email or chat campaign, an announcement sent outside your app                                            |
| When your app decides, from its own code                           | **On manual trigger**                       | After a sign-up succeeds, on a state only your app knows                                                 |
| Only when another experience launches it                           | **No automatic trigger**                    | The second step of a journey: a tour launched from a checklist task, a modal launched by a survey answer |

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FbksbypNzzKY588kZJ0bg%2FB-s02-show-on-triggers.png?alt=media&amp;token=84212145-256a-44d5-9185-418e6662a689" alt="Show on section with six triggers and their descriptions: On page opening, after 2 seconds (selected), On page leaving, On event, On manual trigger, On shared URL and No automatic trigger"><figcaption></figcaption></figure>

## Triggers on user actions

These three triggers start the experience from what the user does in your app. Where, Who and When all apply.

#### On page opening

The experience starts when users load a page that matches Where. Set a delay in seconds to let them look at the page first: `0` starts it at once, any other value waits that long after the page loads. The delay exists only for this trigger.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2F2v9l0f3XkKvAuy8KwKRl%2FPageOpenParam.png?alt=media&amp;token=c3402341-19a0-4fd1-8830-920667c0b310" alt="On page opening settings with the delay in seconds"><figcaption></figcaption></figure>

#### On page leaving

The experience starts when the pointer leaves the page area, usually towards the browser's tabs, address bar or close button. Use it to save a session that is about to end, or to offer help before the user goes.

#### On event

The experience starts when an event happens on the page. Pick an event already created in Jimo, or create one on the fly.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2F9c8d5OZJ3miXEik5TthL%2FB-s12-on-event-dialog.png?alt=media&amp;token=75193165-5297-476c-b673-d3cd0c6ba1c2" alt="On event dialog: Event to trigger your experience, with Create an event on the fly, a search field and the list of existing events grouped by source, and Cancel and Save"><figcaption></figcaption></figure>

An event combines conditions of three kinds:

| Condition | Fires when                                |
| --------- | ----------------------------------------- |
| Element   | An element is present, clicked or hovered |
| Input     | A field is being filled                   |
| Page      | A page with a given URL is opened         |

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FwarwTtLSCByAcUTSSCxw%2Fimage.png?alt=media&amp;token=7e10ce0a-f26f-47e8-a0bf-1ed82323482f" alt="Event conditions on an element, an input or a page"><figcaption></figcaption></figure>

Element conditions need a selector that stays stable from one deploy to the next. How to build and test an event is in [Events](https://help.usejimo.com/docs/analyze/success-tracker/events.md).

{% hint style="info" %}
**Single-page apps.** When the URL changes without a page reload, On page opening may not fire again. Trigger On event on the presence of an element that only exists on the target view. See [Targeting on dynamic apps](https://help.usejimo.com/docs/build/positioning/targeting-on-dynamic-apps.md#spa-navigation).
{% endhint %}

## Triggers that start from outside

#### On shared URL

The experience starts when someone opens a page of your app through a link that carries `?jimo_poke=<experience id>`, whatever the Where rules say, each time the link is opened. Who and the devices still apply: a user outside the audience opens the link and sees nothing.

The settings of the trigger include a link builder: paste the address of a page of your app, and Jimo adds the parameter to the end of it.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FjVcSdA6EA5HimtghBZ0i%2FB-s13-share-your-experience.png?alt=media&amp;token=206d3ca5-a76b-4f8f-a0c2-9bf2cdd8f2e5" alt="Share your experience dialog: the page address https://b2b.usejimo.com/dashboard followed by the ?jimo_poke= parameter of the experience, and the Copy url button"><figcaption></figcaption></figure>

#### On manual trigger

The experience starts when your app calls the Jimo SDK, or when another experience launches it. When your app starts it, all the other settings keep applying: Where, devices, Who and the frequency in When. When another experience launches it, only Who is checked, as for any experience launched by an action. Keep it for flows that only your code can detect, and plan it with your developers.

Selecting the trigger opens a dialog with the code to copy, already filled with the id of the experience:

```javascript
window.jimo.push(['do', 'boosted:trigger', [{ evolutionId: "<your-experience-id>" }]])
```

Paste it wherever your app should start the experience. The method is documented in [SDK Methods](https://help.usejimo.com/docs/for-developers/for-developers/sdk-methods.md#trigger-an-experience-formerly-poke).

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2F1GpJp2r4iYiPTUkDwwwZ%2FB-s03-show-on-manual-trigger.png?alt=media&amp;token=787f18ac-f0fa-4ee5-a623-64239fccecb5" alt="On manual trigger dialog: Copy the code below and paste it wherever you want to trigger this experience, with the window.jimo.push boosted:trigger code and a copy button"><figcaption></figcaption></figure>

#### No automatic trigger

The experience never starts on its own. It shows only when another experience launches it: a tour button, a progress trigger, a checklist task, a survey answer, a Resource Center action. Target & Publish keeps only **Goal**, when the experience has one: there is no Where, Who or When to set, and it shows each time it is launched, on the page the user is on.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FAzRiZA8Jmkh4Nl8ddzqq%2FB-s04-show-on-no-automatic-trigger.png?alt=media&amp;token=1df3503e-faca-4256-abd1-d84b361b34ae" alt="Show on section with No automatic trigger selected, described as Triggered by other experiences actions, never on its own, with the Goal section below"><figcaption></figcaption></figure>

With No automatic trigger, the summary keeps only Show on and Goal.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FOOFa127dRQkwusdsX8Cy%2FB-s04b-summary-no-automatic-trigger.png?alt=media&amp;token=ce27dd20-99d9-4cb5-b3bc-6787847b69ff" alt="Target Experience summary with No automatic trigger: only Show on (No automatic trigger) and Goal (Experience completion) are listed, next to a preview of the modal"><figcaption></figcaption></figure>

## No automatic trigger or On manual trigger

{% columns %}
{% column %}
**No automatic trigger**

* Started only by another experience.
* Where, Who and When do not apply.
* The usual choice for the second experience of a [chain](https://help.usejimo.com/docs/build/actions/chain-experiences.md).
  {% endcolumn %}

{% column %}
**On manual trigger**

* Started by your app's code, or by another experience.
* Where, devices, Who and frequency apply when your code starts it.
* Needs a developer to add the SDK call.
  {% endcolumn %}
  {% endcolumns %}

{% hint style="info" %}
**Launched by an action, only Who counts.** Whatever its trigger, an experience that a button, a task, a trigger or a survey answer launches checks only its Who: a user outside its audience sees nothing, and its Where and When are ignored. With No automatic trigger there is no Who to set, so the experience that launches it decides who sees it.
{% endhint %}

{% hint style="warning" %}
**Part of a journey only? Use No automatic trigger.** With On page opening, an experience that other experiences launch also starts on its own, on every page that matches Where.
{% endhint %}

The link between the two experiences, its state and what blocks publishing are in [Experience links](https://help.usejimo.com/docs/build/actions/experience-links.md).

<details>

<summary>Best practices</summary>

* **Match the moment.** Greet users when they arrive, and keep On page leaving for feedback or a last offer before they go.
* **Let the page load first.** A popup the second a page opens interrupts. A delay of a few seconds on On page opening gives users time to look around.
* **Stay relevant.** The experience should match what the user is doing right now, or where they are in their journey.
* **Combine with Who.** A trigger says when; a [segment](https://help.usejimo.com/docs/publish/target-right-people-who.md) says for whom. The two together make the message personal.
* **Use clicks and hovers for feedback loops.** An On event trigger on a click or a hover asks for input at the exact moment of use.
* **Test, then iterate.** Try different triggers and delays, read the [Analytics](https://help.usejimo.com/docs/analyze/analytics.md), and keep what engages.

</details>

## From your assistant

Ask: *"Set the Follow-up modal to No automatic trigger."* The preview says it will only show when another experience launches it. Or: *"Show the Welcome modal 2 seconds after the dashboard page loads."* More in [What to ask?](https://help.usejimo.com/docs/integrations/mcp/what-to-ask.md)

## Verify

* In the Troubleshoot tool, an experience that waits for its trigger is listed as **Waiting** with the trigger among the conditions. See [Why my experience does not show](https://help.usejimo.com/docs/getting-started/publish-your-first-experience/why-my-experience-does-not-show.md), cause 6.
* For No automatic trigger, open the experience that launches it in the builder and check that the link is green. See [Experience links](https://help.usejimo.com/docs/build/actions/experience-links.md#link-health).

## Go further

* [Chain experiences](https://help.usejimo.com/docs/build/actions/chain-experiences.md): show a second experience after the first one.
* [Events](https://help.usejimo.com/docs/analyze/success-tracker/events.md): build the event a trigger listens to.
* [Stable selectors on a dynamic front-end](https://help.usejimo.com/docs/getting-started/create-your-first-experience/stable-selectors-on-a-dynamic-front-end.md): keep element-based triggers working after a deploy.
* [In-app tour of Show on](https://i.usejimo.com/tours?jimo_poke=8419daab-0b13-4af2-b8ff-0b6e97768d74): opens a guided tour of the section in your Jimo dashboard.

**Next page:** [Where: target pages and domains](https://help.usejimo.com/docs/publish/target-specific-urls-domains-where.md)
