Skip to main content
New Idea

Product-wide URL Exclusion Rules for Engagements

Related products:PX Engagements
  • July 25, 2025
  • 2 replies
  • 44 views

DannyPancratz
Forum|alt.badge.img+9

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

  1. Product has multiple entry points / users might go straight to a specific URL, rather than always land on home page
  2. Want to show a certain engagement when users begin their session, regardless of which page they start on (minus certain exclusions)
    1. NPS and other surveys
    2. Alerts and info (ex. product upgrades, issues, etc)
    3. Marketing (webinar promotion, etc)
    4. 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)
         
  • 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

2 replies

DannyPancratz
Forum|alt.badge.img+9
  • Author
  • VIP ⭐️⭐️⭐️⭐️⭐️
  • July 25, 2025

Possible solutions: 

  • Admin setting at the product-level
  • Global Template settings similar to the Branding/Styling rules across templates that’s on the roadmap

rschlette
Forum|alt.badge.img+2
  • Expert ⭐️
  • July 25, 2025

In the PX mobile SDKs we can call the Enable method on any screen load to enable/disable all events except session int, or enable/disable PX engagements.

GainsightPX.shared.engagements(enable: Bool)

Adding a runtime function like that to the JS SDK would allow dev teams to enable/disable engagements conditionally.

 

Optionally, a JS SDK config in the PX tag could facilitate a static engagement block list, like

“disableEngagements”:urlsList

Those types of configs are usually added to the SDK settings UI in PX as well, so there would be a field similar to the block/mask fields to add urls where engagement should be disabled.