Skip to main content
News

PX Newsletter April 2026

  • April 23, 2026
  • 0 replies
  • 20 views

Sumalatha
Gainsight Employee ⭐️

 

Product Experience April 2026

 

This month we're giving a fan favorite a fresh identity, and shining a light on the moments your users are silently screaming at your product. Insights just got a whole lot more telling. Plus, community highlights, a customer spotlight, and office hours worth adding to your calendar.

Let's dig in! 😀

 

 

Configure Product Score Your Way in Accounts Explorer

PX admins can now customize the Product Score Health KPI with new inputs like Session Duration, NPS Survey data, and Custom Account Attributes — with full control over weight distribution. New parameters default to 0% so your existing dashboards remain unaffected.

Learn More

 

 

Customize How Users Close a PX Dialog Engagement

By default, users can close a PX Dialog Engagement using the small "X" icon or the Esc key — but the "X" can be easy to miss. A simple no-CSS fix is to add a custom button to the Engagement that acts as a close option, with the added ability to control whether the page refreshes when clicked or not.

See the full tip here

 

 


 

Read the full story here

 

 

How Does 'Ignore Throttling' Impact Your Overall Throttling Quota?

Danny Pancratz raised a great question about PX engagement throttling — specifically, whether engagements set to 'Ignore Throttling' still count toward the throttling quota for other regular engagements.

The community weighed in and the answer is clear: any engagement that is viewed — whether it follows default throttling settings or is set to 'Ignore Throttling' — counts toward the overall throttling quota.

A handy clarification for anyone managing multiple time-sensitive and standard engagements side by side!

Read the full discussion here

 

 

Controlling PX Engagement Visibility for Renewal Workflows

Jessica Adkins shared a smart renewal workflow question — when a JO triggers a PX engagement for past due renewals, how do you prevent a user from seeing the same engagement again if they qualify under audience rules a second time?

The community shared a practical approach: use a conditional wait in the CS JO so that once the wait time is exceeded, the PX engagement is de-queued for that user automatically. Additional Audience Rules such as Renewal Date can also be layered in for more precision.

A great thread for anyone building renewal workflows across CS and PX!

Read the full discussion here

 

 

PX Office Hours: Improve your engagement 

Tuesdays at 8:00 AM ET and Thursdays at 12:00 PM ET

Have questions about Gainsight PX or looking to improve adoption and engagement? Join our weekly Office Hours—open to all PX customers.

What to expect:

  • Live answers from PX experts
  • Peer discussions on real-world challenges
  • Practical tips to optimize engagement and drive adoption

Register Here