- 21 May 2025
- 1 Minute zum Lesen
- Drucken
- DunkelLicht
- pdf
How do the conditions in the Event trigger page URL work?
- Aktualisiert am 21 May 2025
- 1 Minute zum Lesen
- Drucken
- DunkelLicht
- pdf
Event trigger page URL enables you to filter data based on where the event is launched. For example, analyze the number of users who closed a Survey on the Leads (https://salesforce.com/leads) page.
The following conditions are supported for the Event trigger page URL:
Condition | Description |
---|---|
Contains | The set value is present anywhere in the URL. |
Starts with | The set value is at the beginning of the URL. |
Ends with | The set value is at the end of the URL. |
Is equal to | The set value is an exact URL match. |
Not contains | The set value is not present anywhere in the URL. |
Note:
Whatfix enables you to add multiple URLs for a single condition. Example: Event trigger page URL contains salesforce and leads.
Use a comma to separate the URLs.
Understand how Whatfix evaluates multiple conditions added to the Event trigger page URL
Whatfix enables you to add multiple conditions to the Event trigger page URL. This is how Whatfix evaluates the different conditions:
Whatfix uses an OR condition for Contains, Starts with, Ends with, and Is equal to.
Whatfix uses an AND condition for Not contains.
Example: Consider that you want to filter data on Salesforce URLs.
Scenario 1: Event Trigger Page URL contains leads, accounts
Whatfix includes any engagement on the following pages:
https://salesforce.com/leads/details
https://salesforce.com/accounts/view
Scenario 2: Event Trigger Page URL not contains leads, accounts
Engagements are included only if the URL contains neither leads nor accounts.
So, Whatfix excludes the following URLs:
https://salesforce.com/leads/details
https://salesforce.com/accounts/view
But includes this URL: https://salesforce.com/opportunities/view
Scenario 3: Event Trigger Page URL with mixed conditions
Whatfix does not include engagement from the URL, https://salesforce.com/leads/archive/view.
The URL satisfies two out of the three conditions, contains leads, starts with https://salesforce.com, but contains archive, which is false. Since it uses an AND logic, the condition fails, and data is not displayed from the page.