Mirror and Guidance Segmentation

Note:

Enhanced Guidance Deployment on Mirror is a Beta feature and is being enabled in batches. For more information, contact support@whatfix.com.

To ensure consistency and flexibility across environments, all Guidance content and widgets, such as Flows and Task Lists, must use the base application’s URL instead of the Mirror URL. This approach enables you to create content once and use it across multiple stages, which minimizes duplication. It also ensures that visibility rules work reliably by avoiding issues caused by stage-specific URLs.

Guidance Usage Scenarios

Guidance content and widgets may be created in the base application or on the Mirror, depending on the use case. Regardless of where it's created, always configure it using the base application’s URL.

The following scenarios highlight when content is created in either environment and why using the base URL is essential:

• Content Created on the Base Application, Intended for Mirror

  Guidance content might be created in the base application and later used in a Mirror, such as a simulation embedded in a Learning Management System (LMS). Even in such cases, the content must use the base application’s structure to ensure that visibility rules and segments function correctly.

  For example, a Flow is captured on the base application’s settings page but appears on the corresponding Mirror Screen embedded in an LMS.

• Content Created on the Mirror, Intended for the Base Application

  In some cases, Guidance content might be created in Mirror during early development or staging, when the live environment is not yet available. Content created in Mirror is used in the base application, so it must follow the base application’s structure to prevent rework.

  For example, a Flow built on a Mirror screen during staging is later used in the production environment.

• Content Created for Use on Both Mirror and Base Application

  Onboarding widgets such as Task Lists need to work across both environments, for testing, or live deployment. Using the base application eliminates the need to duplicate or maintain multiple versions.

  For example, a Task List created on the Mirror is reviewed by internal teams and later deployed in the base application for production use.

  Use the base application’s URL regardless of where you build or use the content. This ensures consistency, avoids stage-specific errors, and supports reuse across environments.

Why Use the Base Application Instead of the Mirror?

Guidance content and widgets must align with the structure of the base application to ensure accuracy, reusability, and consistent behavior across environments. Using the base application provides the following benefits:

• Ensures Guidance content and widgets work seamlessly across staging and production environments without duplication.

• Simplifies maintenance by avoiding issues caused by environment-specific URLs or configurations.

• Improves accuracy of visibility rules and segments across both Mirror and base application contexts.

Note:

• To display content exclusively on a Mirror, use the Window Variable _wfx_mirror_mode in the Visibility Rules. For assistance with configuration, contact support@whatfix.com.

• All Guidance content must rely on well-defined visibility and display rules to ensure accurate display of the content on your application. For more information, see Visibility Rules and Display Conditions.