Site Settings

Modified on Wed, 3 Jul at 3:27 PM

This is a more technical tab, which  contains some options to control the search for page elements when Journeys are playing. Ideally, these settings should be defined by your IT administrator, as technical knowledge is required.



You can specify label names and assign those labels to the Journeys, Steps, Tips and Playbooks in Editor in order to organize the created guidance, especially when dealing with large volumes of content.

Extend wait time for Steps attached on Complex Elements

Optionally specify how much extra time, in seconds, the system should have in order to find references to complex page elements of the given application or website. Enter an integer (no decimal numbers). Increasing this setting means increasing the waiting time before the Launcher opens.

Element search attempts count

Specifies how many attempts the system will make in order to find the page element associated with a given step at the Journey’s creation. Enter an integer (no decimal numbers). Minimum value: 1. The default value is 3.

Element search attempts interval

Specifies a time interval in milliseconds which the system will wait between the single attempts to find page elements.The default value is 500.

Continuous element search

When selected, the system ignores the setting in Interval between Element search attempts and executes the number of page element searches specified in Element search attempts count without pause.

Journey Step URL is based on current browser location

Step URL auto fill - All new Journey Steps will have the Step URL field automatically filled in, based on the current browser location. To disable it, scroll the button. 

Rules for Excluding Element IDs 

Here you can define whether Element IDs are to be trusted or not, or if they can be trusted with some exception. In order to define which elements should be the exception, you should ask a technical person (for example, your IT administrator), who has knowledge of the target application.

Rules for Excluding Classes

Here you can define whether Classes are to be trusted or not, or if they can be trusted with some exception. In order to define which elements should be the exception, you should ask a technical person (for example, your IT Administrator) who has knowledge of the base application.

Site Administrator’s email

You can optionally type in the Site administrator’s email address. This can be useful, for instance, when end users find issues with Journeys - for example, if they click on a Journey link which does not work. A dialog bubble containing this address, as shown below, will come up, and the end user can thus notify the administrator to fix the issue.

 From the 20.0  version, you will be able to access this page also from the editor, as show in the screenshots below:


Relative URLs

Overlay will use only relative path for Journey navigation


The original site is and the Tip is set on The Tip will have the stored URL Id pointing to and path #/project/bubbleGuide.
In this case, the Tip is only visible on the URL starting with In case of active Relative URL, on every URL with path /polarion like for example "" or also on "

Only the Site URL is applied as filter.

When the Tip has no URL set then it's evaluated on every page.

Default Overlay Language and Default Application Language

Default Overlay and Application language can be set from here.

Skill Levels

You can set custom skill level names here.

Launcher position

You can set the launcher position to bottom left or right here.

Auto-hide progress bar

If enabled, then progress bar is hidden while journey is playing.

Overlay Design

In this section you can choose the most suitable overlay design for your appli.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article