Q2 R1 2025 Release

What is new?

The Event trigger page URL filter in User filters now supports the "Not contains" condition.

Why does it matter to me?

You may want to exclude specific URLs from your analysis due to one of the following reasons:

• Remove pages, such as /login, /signup, or /error that don't reflect meaningful user engagement.
• Focus on specific parts of the user journey by filtering out unrelated or later-stage pages.

 With the introduction of the Not contains condition in Product Analytics, Whatfix enables you to focus on meaningful user engagement by filtering out pages that aren’t relevant to your analysis. For example, if you're analyzing early-stage engagement in Salesforce, you may want to focus on /leads or /accounts pages and exclude /opportunities, which represent later-stage activity. You can now do this using the Not contains condition in the Event trigger page URL filter.

How do I do this?

This capability is available to everyone without any extra configuration. For more information, see Filter Insights data using User Filters and User Breakdown and How do the conditions in the Event trigger page URL work?

Exclude blank filter values in Insights

What is new?

Whatfix enables you to exclude blank filter values from Insights data for more accurate and cleaner analysis.

Why does it matter to me?

There may be instances when Whatfix is unable to capture the city or country value and it appears as a blank (-) in the Insights data. Blank values may appear in Insights data due to configuration issues or missing data. With this update, you can filter out blank values to focus on meaningful insights.

How do I do this?

This capability is available to everyone without any extra configuration. For more information, see How can I exclude blank filter values in Insights?

Edit Page View URL in User Actions

What is new?

You can now edit the URLs for Page View-based User Actions using URL-based Display rules, such as URL, Hostname, or Path. Whatfix triggers the User Action based on the Display rules instead of the exact URL.

Why does it matter to me?

You may need to edit the Page View URL due to the following reasons:

• The base URL stays the same, but the parameters change. For example, tracking visits to a common Leads page regardless of the specific lead selected.
• You created the User Action in a test environment and want to track visits in the production environment.
• The page URL has changed after the User Action is created.

Previously, URLs for Page View User Actions could not be edited. With the new editing capability, you can do the following:

• Group dynamic URLs, such as those with changing IDs or parameters, into a single User Action, improving tracking flexibility and reducing duplication.
• Create and test Page View User Actions in UAT and later update the URL to match the production environment. 
• Modify the page URL after the User Action is created.

How do I do this?

This capability is available to everyone without any extra configuration. For more information, see Can I edit the Page View completion rule for User Actions?