- 06 Jan 2026
- 6 Minutes To Read
- Print
- DarkLight
- PDF
Configure Global Settings using Technical configurations
- Updated On 06 Jan 2026
- 6 Minutes To Read
- Print
- DarkLight
- PDF
The Technical configuration section enables you to configure specific Whatfix settings directly from the Guidance dashboard at a global level. Any changes made here apply across the entire Whatfix deployment, ensuring consistency in settings and behaviors.
The following table provides a list of all the configurations that can be set up:
Analytics
Preference Title | Description |
|---|---|
When enabled, this preference reduces data sent to Google Analytics using smaller and more secure GET calls, potentially avoiding data loss from blocked POST requests due to large payloads. However, this might result in some data being omitted. | |
When enabled, set up a forward proxy on your network using a custom domain to receive Analytics calls. These calls are then forwarded to the |
Common Properties
Preference title | Description |
|---|---|
Detect app on url change | When enabled, Whatfix detects changes in the application URL, enabling it to adapt to the new page or application state without requiring a full page reload. |
When enabled, Whatfix uses the | |
When enabled, Whatfix improves Smart Detect performance by reducing multiple element detection calls when an element selector is provided. | |
When enabled, Whatfix ensures that all the Whatfix content appears where they should, even when the underlying application has relative body positioning. | |
When enabled, Whatfix ensures that the Mutation Observer's callback executes at a fixed interval, even when ongoing DOM mutations continue to occur. | |
When enabled, Whatfix monitors mutations whose type matches this configuration. This preference is used by Smart-Tips, Beacons, and Launchers. | |
Injects script on demand in both src and no src iframes | When enabled, Whatfix injects scripts on demand for Studio extensions in iframes, regardless of whether the iframe has a |
When enabled, Whatfix evaluates hidden elements that become visible only on a scroll action. | |
When enabled, Whatfix captures the | |
When enabled, Whatfix monitors mutations whose type matches this configuration. This configuration is used by Smart Context to re-evaluate all widgets if Page Tags have changed due to these mutations. | |
When enabled, Whatfix re-evaluates all widgets only if the page is stable for a certain time interval. By stable, it means there is no change in page structure for that time interval. This time interval can be changed using this preference. | |
When enabled, Whatfix provides immediate feedback while using the new Visibility Rules during content and widget creation in Studio. Visibility Rules are evaluated directly within the application context, showing whether each condition is valid or invalid as it is added. This reduces trial-and-error cycles and ensures rules function as intended during content creation. | |
When enabled, Element reliability indicators help you determine whether selected elements in the application are reliable for content creation. They are particularly useful when multiple similar elements exist on a page or when it is difficult to identify a reliable element. These indicators help you to detect weak or unreliable elements early in your workflow, ensuring that content attaches to the correct element and displays as intended. | |
When enabled, Whatfix considers the current application as a single page application. | |
When enabled, apply global configurations to tooltips in Flows, Smart Tips, or Beacons. | |
When enabled, Whatfix supports content creation on dialog boxes that appear above the main application interface. This ensures Whatfix content is displayed correctly on these overlay elements, without being hidden or obstructed. | |
When enabled, Whatfix supports content creation on popovers that appear above the main application interface. This ensures Whatfix content displays correctly on these overlay elements without being hidden or obstructed. | |
When enabled, set the desired z-index for Whatfix elements. The Z-index property is related to the order in which various HTML elements on a page show up, either in front or behind. If tooltips are showing up behind the HTML elements, then they can be brought to the front by using the z_index property value with a higher value. |
Flows
Preference title | Description |
|---|---|
When enabled, Whatfix automatically hides Flow tooltips when their selected element is hidden. This configuration is applicable only when the selected element is within an iFrame. | |
When enabled, this parameter determines the number of retries Whatfix will perform to find the selected element before continuing with the running Flow. This is useful when waiting for a new page, redirect, or page refresh to occur. | |
When enabled, Whatfix delays the Flow end state, especially when the subdomain remains the same or when dealing with different domain states. This enables Whatfix to hold Flow progress during page navigation and reloads. | |
When enabled, Whatfix manages cross-domain Flows in JS Embed cases. This prevents steps from failing when a Flow is created across multiple domains. | |
When enabled, this preference, in conjunction with Handle Domains, stores the Flow state when it is active within the same domain but different subdomains. This means that if a Flow is created across multiple subdomains, then Whatfix is able to prevent the steps from breaking. | |
When enabled, Whatfix ignores the scrollbar on the application body and automatically scrolls to the element where the Flow step is created. | |
When enabled, a Flow end message is always shown when the Flow is closed midway or exited. | |
When enabled, Whatfix waits for the specified duration to see if the end user performs an action before moving to the next step. If the action is not performed within the specified time, Whatfix continues to the next step. By default, Whatfix checks for the next step at regular intervals of 500 milliseconds. | |
When enabled, set the time allocated to locate the next step. If Whatfix cannot find the step in the allocated time, it advances to the next step or fails. |
Self Help
Preference title | Description |
|---|---|
When enabled, Whatfix provides a JWT token for repository content. This token is automatically added as a query parameter whenever repository content is accessed. | |
When enabled, the search history popup in Self Help does not appear. | |
When enabled, the search suggestions in Self Help do not appear. | |
When enabled, the chatbot configured in Self Help opens in either the same tab or a new tab. | |
When enabled, clicking outside the Self Help widget anywhere on the underlying application closes the Self Help widget. | |
When enabled, the exit feedback pop-up no longer appears when end users close the Self Help widget. |
Smart Tip
Preference title | Description |
|---|---|
When enabled, Whatfix maintains continuous element detection to ensure that any Smart Tips loading within an iframe do not break. | |
When enabled, Whatfix ignores application attributes during mutations of the application. | |
When enabled, Whatfix assesses the visibility of the select element on the screen. If the element is obscured, hidden, or scrolled out of the viewport, the content is not displayed. This is also applicable to Beacons, and Launchers. |
User Action
Preference title | Description |
|---|---|
When enabled, Whatfix captures end users’ click actions on the application using Autocapture, only for specific users based on their User IDs.
| |
Display widgets by default | When enabled, Whatfix ensures that any widget visibility remains unaffected in the presence of any User Action related issues. |
When enabled, Whatfix monitors mutations whose type matches this configuration. | |
When enabled, Whatfix re-evaluates User Actions only if the page is stable for a certain time interval. By stable, it means there is no change in page structure for that time interval. This time interval can be changed using this preference. |