SHOW ON - Trigger on the right spot
Define precise moments for experiences to activate with Jimo's diverse trigger options.
Quick access
Understanding Show On
Click on this link to get an in-app tour of the "Show on" options:
Display Triggers in Jimo act as the starting point for user experiences. They define how an experience will be initiated, directly influencing user engagement and satisfaction. It's the first thing to select in your targeting settings in the Show On section.
What is a Display Trigger?
A trigger is an event or condition that initiates an experience within Jimo. The Display Trigger is the first touchpoint in the user's journey, determining how and when an experience begins. These triggers can be chosed and set up in the Show On section to react to user actions like page visits, clicks, or even exiting a page, ensuring that the right message is delivered at the right time.
Interaction with Targeting Options
While triggers determine how an experience starts, other targeting options define where, when, and who sees it.
Triggers can sometimes override other targeting settings if they are set to advanced modes. For example, a trigger set for 'after a user has completed an action' could bypass the need to check for other conditions like user segments or page URLs.
Filtered vs Independent Triggers
Jimo provides a range of triggering options, from basic to advanced, to suit different use cases:
Filtered Triggers: These triggers require "Who," "Where," and "When" fields to specify the conditions for showing experiences. They include common triggers like page load, element click, and page exit, making them ideal for straightforward user engagements.
For more complex requirements, Jimo offers advanced triggering options that allow for greater precision and control with the manual trigger SDK command.
Independent Triggers: Designed for specialized scenarios, these bypass the "Who," "Where," and "When" fields. They include triggers that activate solely through other experiences or custom URLs, providing more flexibility for linking and sub-experience flows.
Setting Up Filtered Trigger
On Page Opening
When to use it: This is the most straightforward trigger, ideal for welcome messages, feature announcements, or essential tips that you want every user to see upon arrival.
How it works: Set the experience to appear immediately as the page loads. You can also introduce a delay to allow users time to orient themselves within the page before the experience begins.
Customization: Specify the number of seconds after page load when the experience should trigger. This can be set to 0 for an immediate trigger or any other value to delay the start.
On Page Leaving
When to use it: Capture the user's attention just before they exit a page, which can be effective for saving a user session or offering assistance.
How it works: The experience is triggered when the user's cursor moves to leave the page area, typically towards the browser's toolbar or close button.
On Event
When to use it: Activate an experience when a user triggers a specific event on the page. This is useful for more advanced and precise control over when your experiences are shown, such as when a user hovers over an element, clicks a button or performs any other predefined action.
How it works: The experience is triggered by an event selected or created within Jimo. This can include a variety of user interactions or conditions being met on the page. The flexibility of on-event triggers ensures that the content is relevant to the user's actions and enhances their interaction with the application.
(You can also directly reuse previously created Jimo events or create new ones on the fly.)
Customization: Choose the event conditions that will serve as triggers. These can be:
Element Conditions: Trigger when an element is present, clicked, or hovered over.
Input Conditions: Trigger when input fields are being filled.
Page Conditions: Trigger when a specific page URL is opened.
By consolidating multiple interaction types into a single, more advanced on-event option, Jimo allows for greater customization and precision in defining how and when your experiences are triggered.
For advanced configurations, technical knowledge may be required to manually set specific event conditions. For more detailed instructions on creating and using events, visit our Events Page.
On Manual Trigger
When to use it: This advanced option is for experiences that need to be triggered by custom logic in your web application.
Reserve these for intricate user flows where standard triggers do not suffice. Engage with your development team to integrate these smoothly into user actions.
Activating this option allows you to directly copy the SDK method with the appropriate experience ID.
Customization: Implement custom logic within your application's codebase to define precisely when the experience is initiated and paste the given code wherever you need.
Independent Trigger Options
On Shared URL
When to use it: Great for marketing campaigns or special announcements where you distribute a link to users outside your app.
How it works: The experience triggers when a user visits your application through a specific URL that you share. We provide a link builder that will add the experience trigger to the end of any URL path.
Customization: Generate URLs that include a trigger for the specific experience. This will be the only way to trigger the experience, it bypasses any other targeting fields so that the link always displays it.
For all other triggers, you can also generate a similar public URL that will work alongside the selected trigger to share the experience.
No Automatic Trigger
When to use it: Ideal for creating sub-experiences or linking multiple experiences in a flow. Use this setting when you want the experience to be live but accessible only through actions from other experiences.
How it works: Selecting "No Automatic Trigger" disables all other targeting options except for the goal. The experience won’t show automatically; instead, it becomes available exclusively through specific actions, making it perfect for secondary steps in a larger sequence.
Last updated
