As an Admin
I want to set a “global” rule to exclude certain URLs from ALL engagements
In order to
- Ensure specific pages of the UI do not trigger engagements
- Login/log out pages
- {other pages specific to customer products and UX}
- Ensure consistency / avoid human error
- Especially when working with a team of partial-admins who can launch engagements
- Avoid repetitive/duplicative work to always exclude the same URLs for each engagement
Use Case Example
- Product has multiple entry points / users might go straight to a specific URL, rather than always land on home page
- Want to show a certain engagement when users begin their session, regardless of which page they start on (minus certain exclusions)
- NPS and other surveys
- Alerts and info (ex. product upgrades, issues, etc)
- Marketing (webinar promotion, etc)
- Intentional Friction / Customer Journey (ex. “you haven’t completed your onboarding yet, click here”)
Current State Pain Points
- Engagements had been showing on our login/logout authorization pages
- Users were previously identified from earlier sessions
- Users initiated a session that the began with a log-in page, but engagement triggered based on user attributes from previous identify call / PX cookies fitting them into audience criteria
- May be identified from session in same browser in a different instance/environment (ex. Partners/Consultants working with multiple Customers)
- May be identified from session in same browser in a different instance/environment (ex. Partners/Consultants working with multiple Customers)
- To avoid this for the many use cases above, we have to remember to / audit whether each engagement is set to exclude these URLs. Thus:
- Added effort to set up and/or audit
- Risk of human error, especially across teams