You know it and your users go by it - successful experiences must be integrated into your interface and respond to their needs.

In this lesson, you’ll learn how to position your Experiences, to be contextual, discoverable, and useful.

🎯 There are 2 important components of setting Experience positioning with Chameleon:

  • controlling the specific page where it displays (using Environments and tweaking with URL rules),

  • and literal, on-page position (using page elements or screen anchoring).


Let's talk elements before seeing how to use them to position Experiences.

Chameleon works great with different types of frameworks and can easily read the different elements on your page. This way, you can position Experiences around key features and behaviors.

Selecting elements occurs in a few different places:

  • setting an on-page element to be present - for a Step or an Experience to display.

  • setting an Experience to be triggered by a user action - a click or a hover onto an element.

👉 Watch the video below to understand how element selection works in Chameleon.

Note: This video does not show the latest version of our product. We will soon update all our videos to fit our new style and improvements. 😊


👉 Next, let's see how to position your Experiences to be discoverable and relevant

There are 2 ways you can position your Experiences with Chameleon:

  • relative to the screen

  • relative to an element.

Watch the video below to see how you can use each option.

Note: This video does not show the latest version of our product. We will soon update all our videos to fit our new style and improvements. 😊


🦎 Chameleon Activity

Use the Position options in the Builder to see how you can guide your users without restricting their access to other features or options. Play around with the point-and-click selector to see how you can adjust the position after selecting an element. Notice the auto-position options and the auto-adjust behavior too.


👉 Go on learning how to control where your Experiences display and what conditions you can set for them to appear to your users.

Did this answer your question?