Gainsight PX

What it is

Gainsight PX is Gainsight’s product-experience module: product analytics, in-app guides and checklists, in-app surveys, an embedded help widget, and adoption scoring for a SaaS product your customers log into. It began as Aptrinsic, which Gainsight bought in 2019, and it is sold as its own subscription — you can run PX without Gainsight CS, and most of the value case assumes you don’t stop there.

This page covers PX only. If the question is health scores, renewal forecasting and CSM playbooks, that is the Gainsight CS page. The question PX answers is narrower: does a CS-tilted adoption tool cover what you need, or do you need a product-analytics-first platform like Pendo?

Why it shows up in Customer Success stacks

• Usage data that lands where CSMs work. PX has a native PX-CS integration: account and user usage, adoption scores and PX survey responses flow into Gainsight CS health scores and timelines without a reverse-ETL job. This is the single reason most teams pick PX over a stronger standalone analytics tool.
• Engagements a CS team can ship without engineering. Guides, tooltips, onboarding checklists, native email campaigns and NPS/CSAT/CES surveys, with throttling so one user doesn’t get three pop-ups in a session. The help widget is now called In-App Hub (formerly KC Bot) and can search Zendesk, Salesforce Knowledge, Thought Industries, Coveo and other knowledge sources.
• An MCP server on live PX data. Gainsight’s MCP page lists the PX MCP server as generally available (the PX support index still labels the LLM-connection article “Beta” as of 2026-10-27). Combined with the Gainsight MCP Prompt Library launched in the August 2026 PX newsletter, a CSM can ask Claude or ChatGPT which accounts stalled on a feature and draft the follow-up — the “find, understand, fix, verify” loop Gainsight teaches in its PX in Practice sessions.
• Analytics that recently got deeper. Query Builder now has a Metrics mode (pre-built and custom metrics plus a formula builder) alongside the Cohort view, and Path Analyzer shows average time between steps. Still not Amplitude-depth, but the gap narrowed in 2026.

Pricing reality

Gainsight does not publish PX prices; the pricing page offers “Request Pricing” and a free trial. Price is set mainly by monthly active users (MAU) on the tracked product. Two packages exist in Gainsight’s documentation:

• PX Essentials — one product plus up to 3 additional product tags, 100K emails/month, a single active In-App Hub, basic integrations.
• PX Enterprise — up to 30 product tags with cross-tag tracking, 500K emails/month, multiple In-App Hubs, advanced integrations, enterprise security.

Both include unlimited MAU on paper, a cap of 1K events per MAU per month, 36 months of data retention and 1M public API calls per day.

Real-world band, from third-party data (Userpilot and Oliv.ai cost write-ups, both vendor-adjacent): small single-product deployments start around $13K–$14K a year, the median contract sits near $50K a year, and multi-product enterprise deals run past $100K. For comparison, our Pendo page puts mid-market Pendo at $30K–$150K a year. The real lever is the bundle: teams buying CS and PX together report negotiating 15–25% off the combined suite (see our Gainsight vs ChurnZero comparison).

Best for

• CS operations leaders at B2B SaaS companies already on Gainsight CS who want product usage inside health scores and CSM timelines without building a data pipeline.
• Onboarding and adoption programs run by CS, not product — checklists, feature announcements and in-app NPS owned by the post-sale team.
• Teams that want to query adoption data from an AI assistant today, through a vendor-supported MCP server rather than an export.

Versus the alternatives

• Pendo — the market-share leader for customer-facing product adoption, with deeper analytics, a roadmap module and a far larger review base (238 GetApp reviews to PX’s 7). Pick Pendo when product management owns the tool and analytics depth matters more than the CS handoff. Pick PX when CS owns it and Gainsight CS is the system of record.
• WalkMe (SAP) and Whatfix — the two largest digital adoption platforms, built mainly for guiding employees through software you bought. Pick them when the target is internal apps like Salesforce or Workday; PX is for the product you sell.
• Userpilot, Appcues and Chameleon — self-serve adoption tools with list prices from about $249–$299 a month. Pick one when you have no Gainsight CS and need guides plus light analytics under $10K a year.
• Guidde — the fastest-growing entrant in adoption content, on a $50M Series B led by PSG Equity in February 2026. Pick it when what you actually need is fast how-to video, not targeted in-app engagement.
• Amplitude or Mixpanel — pick these when the need is analytics only; neither replaces in-app guides.

Watch-outs

• PX without Gainsight CS loses most of its edge. On analytics alone, Pendo and Amplitude are stronger, and the review base is thin. Guard: if you aren’t on Gainsight CS or committed to it within the contract term, run a side-by-side trial against Pendo or Userpilot before signing.
• The 1K-events-per-MAU cap bites chatty products. Auto-tracking plus custom events on a high-frequency app can hit it. Guard: pull 30 days of event volume per active user from your current analytics before negotiating, and get the overage terms in the order form.
• No native HubSpot or Snowflake connector. The integrations index lists Salesforce (bi-directional), Segment, S3/Google Cloud Storage, Slack and Zendesk; HubSpot needs the PX Data Loader or REST API, and Snowflake needs a third-party reverse-ETL tool. Guard: map every system that must receive PX data before the deal and price the middleware into the total cost.
• MCP status differs by page. Marketing says GA; the support docs still say Beta. Guard: confirm in writing that the PX MCP server is covered by your support SLA before you build CSM workflows on top of it.
• Bundle discounts lock renewals together. A 15–25% CS + PX discount makes it costly to drop either module later. Guard: negotiate separate renewal caps per module so PX can be removed without repricing CS.