PX Release Notes October 2025

Capture Richer Context from User Interactions with Tracking Properties

We are excited to launch Tracking Properties, a new capability in Gainsight PX that enables you to capture richer context from user interactions, without relying on engineering. This enhancement offers you more flexibility in analyzing how users engage with your product, helping you uncover deeper insights and make data-driven decisions faster. Tracking Properties can be analyzed in PX Query Builder to filter, group, and report on user behavior with greater precision. 

Example Business Use Case:  If your web app includes forms with radio buttons or checkboxes where the selected states are stored within form containers, you can use Tracking Properties to capture those selections. This allows teams to collect and analyze user choices directly in PX, without requiring additional custom events from engineering. Ensure the data is present at the time the event occurs for PX to capture the property value successfully.

Tracking Properties include the following property types:

• URL Property: Capture URL path segments, query parameters.
• UI Element Property: Record details such as placeholder text, selected options, or entered values from form fields and buttons.
• Advanced JS Property: Fetch simple values (string, number, boolean) from browser objects such as window or document.

Note 

• PX also provides out of the box system properties such as page title, screen width, browser and device type, UTM tags, and more. 
• Tracking Properties can only be created in the in-app Product Mapper
• Tracking Properties can only be created at the feature level, and each feature requires at least one matching rule (URL, UI element, or text Element).
• Each feature can have up to five properties, and each product in a subscription supports up to 1,000 properties .

For more information, refer to the Instrument Your Product using In-App Mapper article.

Exclude Users with Not In Segment Condition 

We have enhanced how PX Segments can be used across Analytics, Dashboards, Engagements, and Audience Explorer. In addition to the existing in condition, you can now apply a not in condition to exclude users or accounts that belong to a segment. This makes it faster and easier to focus on the right audience, especially when individual selection is a longer list.

Note: This filter condition can be used for all types of segments (Real-Time, CSV, and External).

Example Business Use Case: Analyze all users except trial users by applying a not in Trial Segment filter, or target all users except internal employees when setting up reports and dashboards.

For more information, refer to the Segments article.