Smart Tip does not appear based on the set Triggers

Issue

You have configured Smart Tip segments to appear based on Triggers, but they are not appearing in your application.

Probable Causes

• The data type selected for the Trigger condition (text, number, or date) does not match the type of data in the application. For example:

  • The Trigger is set to show a Smart Tip based on text input, but the text condition might be case-sensitive or does not match the exact text entered by the user.

  • The Trigger is set to a specific number (for example, 3). If the value changes, the Smart Tip does not show up because the condition is tied to the original value.

  • The date condition is set incorrectly, or the date format does not match the value in the application.

• The element you selected to create the Trigger condition is not present on the page.

• Triggers might have difficulty reading text or data in dropdowns due to changes in the page's structure.

• The underlying application has UI changes.

If you're using the Whatfix Browser Extension for content delivery

• Content may be delayed due to extension-based deployment. If you use an extension-based deployment, you may have to wait up to 30 minutes before the content appears for your end users. The duration may vary based on the store where the extension is hosted, such as the Chrome Web Store, Microsoft Store, or another store.

Suggested Solutions

• Ensure the Smart Tip Trigger condition matches the data type in the application.

• Create separate Trigger conditions for both uppercase and lowercase variations of the text. This ensures the Smart Tip appears regardless of how the text is entered.

• For number-based Triggers, check that the value matches the expected input. If the value changes, update the condition accordingly.

• Verify that the date condition is correct and that the date format matches the one used in the application.

• If there are UI changes in the application, reselect the element. For more information, see Reselect Smart Tip Elements to Manage UI Changes.

If you're using the Whatfix Browser Extension for content delivery

• If you use an extension-based deployment, you might have to wait up to 30 minutes for the content to appear after pushing to production. The time may vary depending on the store where the extension is hosted. To reduce this delay, Whatfix recommends that you host your extension on the Whatfix Store. Updates typically reflect within a few minutes. For more information, see Whatfix Store: Our recommended choice to host Whatfix extensions.

Note

If the issue persists, contact support@whatfix.com.