Feature Adoption Signals

Gainsight PX tracks how many users open and return to a specific feature after release. A Beam agent reads adoption numbers against an approved target set for that feature and, when adoption lags, notifies the product manager and logs the gap for the next review. This gives the product team a consistent read on every feature launch instead of someone pulling a usage report by hand each week. Features still within their early rollout window, missing a comparable prior release, or affected by a known tracking gap are routed to a human before any adoption flag is raised.

In-App Guide Engagement

Gainsight PX in-app guides walk users through a feature and record whether each step was completed or skipped. A Beam agent reads completion data for a guide and applies an approved rule, such as notifying the team when a guide's drop off point stays high across a set period, so the guide can be revised. This applies the same check across every active guide rather than one team member reviewing each guide in turn. Guides with too little traffic to judge fairly, a recent unrelated product change, or conflicting completion data are routed to a human to interpret first.

Product Usage Segmentation

Gainsight PX groups users into segments based on how they use the product, such as by plan tier or feature usage pattern. A Beam agent reads segment membership changes and, following an approved rule, notifies the account's customer success manager when a user moves into a segment tied to churn risk or expansion potential. This flags every relevant account move as it happens rather than waiting for a manager to notice during a periodic review. Segment changes based on incomplete usage data or a recent account merge are routed to a human to confirm before any notification is sent.