Q3R2 2026 Release

	Q3 R1 2026 Release Last updated: October 19, 2026

The following are the updates for DAP on Web:

Whatfix Popup templates is available to allGA

What is new?

Whatfix now enables you to create pop-ups using a library of professionally designed templates, combined with an intuitive drag-and-drop editor for layout and customization.

Instead of starting from a blank canvas, you can select a template based on your use case and modify it by adding text, images, GIFs, and buttons directly within the editor. You can also control layout using side-by-side placement, resize elements and pop-ups, and configure appearance, positioning, and behavior, all without relying on CSS or custom code-based workarounds.

Why does it matter to me?

You can now create pop-ups faster using a ready-made library of 50+ professionally designed templates for common use cases such as outage alerts, feature updates, training, and announcements.

These templates provide a structured starting point and enables you to quickly customize content, layout, and styling to match your requirements. This enhancement improves the editing experience and makes it easier for you to iterate and refine pop-ups quickly.

How do I do this?

The template-based Popup creation experience is now available to all users without additional configurations. For more information, see Create Popups with Templates.

Whatfix Popup EnhancementsGA

The following enhancements are available with this release:

Reposition elements with the grab handle: You can now move an element only with its grab handle. Selecting or clicking text inside an element does not move the element.
Replace text and retain its formatting: You can now paste text into a text or button component and keep the existing formatting of that component. Use Cmd + Shift + V on Mac or Ctrl + Shift + V on Windows to paste.
Spacer label and tooltip: The space in between elements now shows a label, and a tooltip appears when you hover your cursor over it. Use the Drag to adjust spacing handle to adjust the space in between elements.
Border Radius for images: Image components now stay within the rounded corners of the Popup or adjust to fit the rounded corners when you set a Border Radius.
Web on Mobile experience: Popups created with the new templates now fit mobile browser screens. Images keep their original aspect ratio, and buttons automatically adjust based on width. For more information, see Web on Mobile experience for Popups.
DAP on OS support: The new Popup templates experience is now available for DAP on OS.
Discard returns to the template library: When you discard your changes, Whatfix returns you to the Templates page.
Slides support for Carousel Popups : You can now add upto 12 slides in a Carousel Popup.

How do I do this?

These enhancements are available to all users without additional configuration.

End User Display NamesGA

What is new?

Whatfix now enables you to show a Display Name to your end users, instead of the Content Name. Use Content Title for your internal use and reference, such as release codes, naming conventions, region and more.

You can add a Display Name to Flows, Smart Tips, Beacons, Launchers, Articles, Links, Videos, Images, and PDFs from the Whatfix Guidance Dashboard or Whatfix Studio.

With Display Names, you can:

show users a clear name in Self Help while you keep your internal naming conventions
view the Display Name column in the All content and All widgets lists on the Dashboard
search for content by Display Name on the Dashboard
export Display Names with your content and widget data
translate Display Names the same way as Titles, including with Translate all

Note:
Existing content shows the Title to users until you add a Display Name.
The Content Title Shown value in analytics logs the Display Name in the language configured by you.
Exports and Download PDF show the Display Name instead of the Title when you add one.
To add a Display Name to content in the Production stage, use the Edit in draft workflow.

Why does it matter to me?

Previously, the Title of your content was both the internal Name and the label users read. Internal codes for region, release, and module appeared to users. Users saw these codes in Self Help, Task List, and search.

Now, you keep a structured Title for content management and show users a name that describes the task.

How do I do this?

End-User Display Names is available to all users without additional configurations.

For more information, see Add a Display Name to Whatfix Content.

Export and View Content Performance Data in DiagnosticsGA

What is new?

Whatfix Diagnostics now enables you to export your diagnostics logs together in one place and download them as a CSV report. The report shows the following details for every content item on the page:

whether Whatfix evaluated and displayed it
how its Visibility Rules and Element Precision rules evaluated
how long Whatfix took to evaluate it, find its element, and display it
what to fix when something fails or runs slow

Each download contains two CSV files. The content information file gives you the details of each content item. The meta data file summarizes the whole session, including the browser details and every threshold breach. A threshold is the recommended maximum evaluation time for content, a component, or a rule.

Note:
Diagnostics exports the logs for the page you have open.
Exporting the report doesn't affect how your application performs for your users.
The report measures how long Whatfix takes to evaluate your content, not the overall performance of your application.

Why does it matter to me?

Previously, you had to collect debugging details from three places: Diagnostics, debug commands, and browser developer tools. No single view showed what Whatfix evaluated on a page or how long each part took. You also had no report to share with another team.

With the CSV report, you can identify the content that takes the longest to display and fix it before you move it to the Production stage. You can then share the report with your IT or security team as evidence for their approval. For any performance or content-related issue, you can attach both files to your support ticket, which gives Whatfix Support the details required to investigate the issue, often without a call.

How do I do this?

The diagnostics logs export is available to all users without additional configurations. For more information, see Export and View Content Performance Data in Diagnostics.

Simplified Role Segmentation with the All Users Role TagGA

What is new?

Whatfix now attaches the All users Role Tag to new Flows and Static Content that you create, so your content is visible to all your users by default. You add a Role Tag only to restrict who can see a piece of content.

With the All users Role Tag, you can:

create content that all your users see without adding a Role Tag
restrict content to users with specific roles by adding the required Role Tags and then removing the All users Role Tag
check the Role Tags field on a Flow or Static Content item to know whether all users, only users with a specific role, or no users see it

files

Note:
The All users Role Tag applies only to Flows and Static Content, such as Articles, Links, PDFs, Videos, and Images, that you add to Self Help and Task List. The behavior of Role Tags on other content types and widgets remains unchanged.
You can't edit or delete the All users Role Tag. However, you can remove it from individual Flows and Static Content items to restrict who can see them.
When you remove the All users Role Tag without adding another Role Tag, your content isn't visible to any user, and Whatfix doesn't display a warning.

Why does it matter to me?

Previously, the visibility of content without a Role Tag depended on whether your account had any Role Tags. If your account had no Role Tags, content without a Role Tag was visible to all your users. If your account had at least one Role Tag, content without a Role Tag wasn't visible to any user, and Whatfix showed no warning or reason.

With the All users Role Tag, Role Tags only restrict content and never hide it by default. Your content reaches all your users unless you choose to restrict it.

How do I do this?

Whatfix attaches the All users Role Tag to every new Flow and Static Content item without additional configurations. Whether Whatfix adds the All users Role Tag to your existing content depends on your account:

If your account has no Role Tags, starting October 19, 2026, Whatfix adds the All users Role Tag to all existing and new Flows and Static Content. This addition doesn't change what your users see.
If your account already has Role Tags, Whatfix displays a banner on the Whatfix Guidance Dashboard, where you can review and update your content. Nothing changes until you choose to switch from the banner.

For more information, see Understand the All Users Role Tag.

Content Throttling: Temporarily Disable Content That Slows Your ApplicationBeta

What is new?

Whatfix now detects content that slows down your application and disables only that content, only for the affected users, in the session where the issue occurs. All other Whatfix Inhalt keeps working for the affected users and for all your other users.

With Content Throttling, Whatfix:

checks how its content performs on your application against performance thresholds while your users work
identifies the specific content item that causes the performance issue
disables that content item for the affected users, in the session where the issue occurs

Whatfix treats content as a performance issue when any of its conditions exceeds its threshold. The threshold is 100 ms for element-based or Finder conditions, and 10 ms for each other Visibility Rule condition.

Note:
Content Throttling works at the content level and never disables Whatfix as a whole.
Content Throttling applies only to the live experience of your users and doesn't apply in Preview Mode.

Why does it matter to me?

Previously, when a single piece of content slowed down your application, it was hard to tell which content was responsible. To protect your application, you had to disable Whatfix for all your users, including users who had no issue, and wait for a fix.

An issue in one content item affects only that item, and only for the users who experience the issue. Your other users and the rest of your content continue as usual. You can now use the diagnostics logs export in Diagnostics to find slow content before it reaches the Production stage, and rely on Content Throttling once your content is live.

How do I do this?

Content Throttling is a Beta feature. To enable it for your account, contact your Customer Success Manager. For more information, see Understand Content Throttling in Whatfix.

Updated Event Names and Descriptions for Guidance AnalyticsGA

What is new?

Whatfix now displays updated names and descriptions of Guidance events across DAP content types and widgets. The updates cover content types such as Flows, Pop-ups, Smart Tips, Launcher, Beacons, Blockers, and Surveys. They also cover widgets such as Self Help and Task List.

Event names now follow a consistent pattern. For example, Launcher Loaded is now Launcher Shown, and Blocker Loaded is now Blocker Shown. Updated descriptions state more precisely when each event triggers.

Note:
The Extension installed, Chrome extension installed, and Extension check events are no longer available in the event list.

Why does it matter to me?

Previously, similar events used different terms, such as Loaded and Shown. Some descriptions also did not match when the event triggered. Consistent names and accurate descriptions enable you find the right event and interpret your insights data correctly.

How do I do this?

The updated event names and descriptions are available to all users. They appear in the Summary or content specific engagement from the Guidance analytics page.

For more information, see Analytics Summary - Guidance analytics Dashboard and the Content or Widget specific articles, such as Flow Analytics - New Guidance Analytics Dashboard or Metrics on the Self Help Analytics Dashboard.

Updated Event Groups for DAP for Web and DAP on OSGA

What is new?

Whatfix reorganizes event groups so each event appears under the product or content type it belongs to. This release includes the following event group updates to DAP for Web and DAP on OS:

DAP for Web

Hub: The Self Help (New) event group is now called Hub. Hub contains all Self Help (New) events, such as Explorer and QuickRead events.
Flow: The following Flow related events are updated with names or descriptions:
- Flow Shown as Pop-Up (moved from Popup event group to the Flow event group)
- Flow Step (automated) Closed
- Flow Completed with Feedback
- Flow switch to manual
- Flow closed without feedback
- Flow closed with feedback
Content types and widgets: Pop-up, Survey, Beacon, Blocker, Smart Tip, Cue, Task List, Self Help, Launcher, and QuickRead events have updated names or descriptions within their existing event groups.
Others: The Page View event is now Whatfix for Web Loaded.
Extension events removed: Whatfix no longer displays Extension installed, Chrome extension installed, and Extension check events, in the event list.

DAP on OS

All DAP on OS events now appear under the DAP on OS event group instead of the Hub event group.

Note:
The DAP on OS event group now contains Self Help (New) events. To analyze DAP on OS events on the Product Analytics dashboard, use the DAP on OS event group.

Why does it matter to me?

Previously, the Hub event group contained DAP on OS events, while Self Help (New) events appeared under a separate event group. Event group names did not match the product or widget that generated the events.

How do I do this?

The updated and new event groups are available to all users without additional configurations.

For more information, see List of Whatfix-related Events and List of Whatfix-related Events on DAP on OS.

Control Whatfix Content Availability from the DashboardGA

What is new?

Account Managers can now disable and re-enable all Whatfix Inhalt for an account’s production environment from the Whatfix Guidance Dashboard.

Info:
After Whatfix content is disabled, Content can take up to 10 minutes to disappear.
Whatfix pauses the analytics collection until the content is re-enabled.
Whatfix content can be re-enabled only after a 30-minute cooldown period.
This feature is supported only in Player Extension and JS Embed mode of deployment.

Why does it matter to me?

Previously, only Whatfix Support Team could disable Whatfix content. Now, Account Managers can act during performance issues or emergencies on their live application.

How do I do this?

Whatfix Content Availability is available to all customers who have enabled Player Extension and enhanced environment mapping for JS Embed mode of deployment. For more information, see Control Whatfix Content Availability from the Dashboard.

Environment and Map Stages in JS Embed Mode of DeploymentBeta

What is new?

Whatfix now supports advanced environment and stage mapping for the JS Embed mode of deployment. Content authors can map Draft stage content to any application environment, such as User Acceptance Testing (UAT), and validate it directly in that instance.

Info:
Once the feature is enabled for your account, Whatfix transitions your existing configuration to the new experience. Your existing setups and deployment scripts continue to work without any migration.

Why does it matter to me?

Previously, authors had to move content to the Ready stage or use Whatfix Studio Preview mode to validate Draft content in JS Embed mode of deployment. Now, they can validate it directly in the environment they choose.

How do I do this?

Environment and Map Stages in JS Embed Mode of Deployment is a Beta feature. For more information, see Configure Environments and Map Content Stages for JS Embed.