Avoid elements not found
Learn how to ensure your in-app experiences in Jimo always find their intended elements. This guide covers common challenges and effective strategies to avoid the 'Element Not Found' issue.
In Jimo's in-app experience creator, precise element selection is vital. While Jimo's element selector is robust, situations may arise where an element isn't recognized, potentially disrupting the user experience.
Common Reasons for Element Not Found
Variable Element Appearance: When elements look different across user accounts, like between trial and paid versions.
Dynamic CSS: When CSS class names change dynamically, typically in response to different user interactions or deployments.
Step-by-Step Solutions
-> If you can't find an adequate target with the automatic selector of the in-app builder, select a dummy target to be able to edit it manually and apply one of the following solutions.
Addressing Variable Appearances:
For non-text variations, select the static part of the element that will be used by our query selector or, as a last resort, resort to manual CSS selection.
Managing Dynamic CSS:
Work with your development team to ensure CSS selectors are stable or to implement data attributes specifically for Jimo to target.
Jimo doesn’t handle dynamic text for now, we only use a query selector on the ID or class to target elements.
Testing before going live
Use Jimo's preview mode to verify that your in-app experiences are correctly triggered.
For complex scenarios that cannot be resolved through the above methods, seek assistance from Jimo's support team.
Accurate element selection ensures seamless in-app experiences. The easiest way is to work alongside your web designer or development team on how you tag elements in your CSS (Class, IDs). You may need to adapt or create specific tags to handle Jimo. By anticipating issues like dynamic content and CSS changes, you can craft robust experiences that engage and assist your users effectively.
Last updated