Setup and Instrumentation
  • Product instrumentation shouldn’t take weeks
  • Visualizing your product’s features should be intuitive – and easily maintainable
User Analytics
  • Don’t compromise on feature-level and day-level user retention analytics
  • Don’t miss out on the ability to track and trigger actions based off of granular custom events
Application Performance
  • In-app product guides and engagements shouldn’t come at the cost of application performance
Product and Success Alignment
  • Your Success team is working hard to drive adoption and deepen relationships with customers; your strategy — and systems — should be aligned
Product Engagement
  • Building product engagements off of multiple pages and setting up multiple knowledge centers should be out-of-the-box
  • Ensuring users don’t get inundated with product engagements should be automatic & cross-product
  • The quality of in-app feedback shouldn’t be compromised by lack of survey types
  • The ability to paywall features should be a given
Cross-Channel Onboarding and Release
  • Triggering emails off of usage to drive a true cross-channel onboarding and release experience shouldn’t require an integration
  • Users should have the flexibility to limit the provision of usage data in order to comply with local standards
  • Support should exist for hardened host setup in order to reduce vulnerability

Fast Setup & Instrumentation

To start analyzing usage data and building engagements, you first need to tell your tool what features or ‘events’ you want to track—that is, what are those things (clicking on a button, filling out steps in a form, etc.) you want to capture usage about. This process should be intuitive and automated, and shouldn’t require engineering resources.

Automatic Product Instrumentation

Alternative solutions gap: Other solutions don’t support automatic mapping into a product hierarchy, resulting in a more manual and time-intensive process to get up and running. In many cases, this also means requesting valuable engineering time and resources to help and / or leads to human error or unmaintainable naming conventions.

PX approach: The PX auto-mapping capability will map your entire product into a structured module and feature hierarchy (with readable names) straight from your usage data. Any new feature introduced will also be detected and marked as new, allowing you to import the mapping with one click.

This process greatly reduces initial implementation time, can be done without coding or engineering support, and also ensures that you always have the most up-to-date usage as your product evolves and new features and URLs get added.

Intuitive Organization of Product Features

Your application likely has dozens if not hundreds of features or events that you want to collect usage insights on. Visualizing these events as a ‘flat list can quickly become overwhelming and unmaintainable, especially when you need to add new features or distinguish one from another.

Alternative solutions gap:

Other solutions don’t support nesting or grouping of features. This creates a challenging “flat list” approach where the organization of features relies on human adherence to data syntax rules and structures.

PX approach:

PX allows you to model your product in a hierarchy, which reflects how you view it. It doesn’t require coding and you can easily change this structure at any time and the reporting will follow suit—enabling you to scale easily. This purpose-built approach for SaaS products saves developer resources and QA cycles. Gainsight PX also deploys by eliminating the “technical debt” associated with sticking to rigid tagging and naming conventions.

Superior User & Retention Analytics

As a first step, product leaders want to deeply understand what’s going on with their users—what features they are (and aren’t) using, how they move through the product, where they get stuck—and develop hypotheses on how and for whom to drive more awareness or build new features. That means your tool needs the ability to dig in very granularly into usage as well as be able to track a wide variety of event types.

More Nuanced Retention Analytics

Understanding the usage of your “Golden Feature,” and the impact it has on users coming back into your application is table stakes for most Product Managers. Additionally, having the ability to drill down to daily trends provides more meaningful insights for companies.

Alternative solutions gap:

Alternative solutions only show retention based on whether a user logs in or not. Additionally, they are only capable of showing cohorts by week or by month. Both of these limit a true understanding of user behavior as well as actionability.

PX approach:

Gainsight PX supports many nuanced retention-related analytical needs, including:

  • Feature-level retention analytics: allows you to answer if a given feature, or grouping of features  (e.g., a module), is sticky or not
  • Cohort retention comparisons: : allows you to graphically compare and benchmark retention in a custom cohort with a baseline
  • Engagement retention analytics: enables you to investigate and measure how well a given  engagement has driven retention in a set of users
  • Day-level granularity: enables you to investigate new user dropoffs at a detailed level as well as  align analytics with highly valuable but short time periods of interest (like a trial period)
  • Robust metrics reporting: session, user, and account metrics show % as well as absolute

Tracking and Triggering of Actions Based Off of Granular Events

An example of a granular or “custom” event is the ability to track form progress. When a user is presented a series of options in a form, or objects to fill out, a custom event could track not only which options are selected or what goes into a field, but where drop-off might occur on that form. This event data is valuable because oftentimes you need a granular view to understand how well your core features are driving towards outcomes as well as exactly where issues are coming up.

Alternative solution gap:

While others claim to have the ability to capture custom events (or track events), it is only available in a report tracking the specific usage of that event. In addition, the properties associated with the custom event cannot be leveraged in analytics or targeting. This means one cannot create engagements based off of these events, which limits the ability to drive user behavior at a more granular level.

PX approach:

In addition to automatically tracking pageviews and click events, Gainsight PX can capture this valuable ‘custom’ event data, and make it available to target engagements (for example, to encourage users to finish the aforementioned form). These custom events, as well as their attributes, are available throughout the platform and can also be used for filtering reports.

Hypercontextual In-App Engagement

In-app engagements are a primary means of driving product and feature adoption. There are many different types of engagement types with various associated use cases. Gainsight PX offers many differentiated features when it comes to in-app engagements that enable you to drive a more targeted and a personalized user experience at scale.

Multi-page Guides

In many cases, the full workflow of a feature you wish to guide a user through exists on multiple pages or on different areas outside of the immediate scope of the screen. This requires a guide to be able to jump to different pages or scroll automatically to ensure that the user can be fully enabled and sees the value.

Alternative solutions gap:

Many alternative solutions were originally built for websites and not web apps, so their guide infrastructure does not support common scenarios such as multi-page guidance and auto-scrolling of users to locations that are not currently in view.

PX approach:

Gainsight PX supports both single page and multi-page guides. This means we enable onboarding guides spanning multiples pages in your application, auto-scrolling to different locations on the page, and initiating ‘next step’ activities in a variety of ways (user clicks next, engages with the element highlighted, hovers over element, or enters text). In general, supporting multi-page applications are more challenging since the page reloads. However, this is made possible by our modern architecture and the fact that PX is 100% server side.

Advanced Engagement Nurturing

Similar to throttling, there are times when you may want to attempt an engagement multiple times. The user may have dismissed it already once, but there is so much value it is worth bringing the engagement up again. Another use case is recurring engagement needs. Some examples of this include:

  • Feature activation campaigns where you are trying to raise awareness of a feature, but the guide or banner was dismissed at first view. In this case, you’d want the  engagement to try again at a later date (essentially get snoozed) versus completely stop
  • NPS or CES collection which should occur monthly / quarterly
Alternative solutions gap:

Many alternative solutions simply do not have the capability to handle throttling for ‘nurture’ type engagements. It’s not possible to set time intervals between attempts or cap the number of attempts.

PX approach:

PX can set number of guide attempts within an interval. This includes the ability to set recurring reminders and cap the number of occurrences. For example: you configure the system to show a guide, try once per day, up to 3 tries. In the event the user follows the guide you can stop nurturing or trigger it again within X days / months. You can also cap the number of completions.

Multiple Personalized Knowledge Center Bots, Knowledge Base Integrations, and Analytics

Knowledge Center Bots (“KC Bots”) are resource guides that “live” on every page of your site. Users can always access the KC Bot and search for relevant help content like how-to articles, feature guides, or even use it to submit feedback.

KC Bots are particularly useful for onboarding, as they can contain checklists with self-trigger guides to help users learn about the product and its features. They can also contain articles from your knowledge base and present these directly inside the bot, so users don’t need to leave your app to view this information.

There are many instances in which you might want to personalize the experience of a bot. A classic example is that you might want to show one KC Bot to new users with content specific to onboarding, whereas you might want to show a different KC bot with different content to more “mature” users

Alternative solutions gap:

Alternative solutions require significant development resources to create personalized KC Bots (or the equivalent), which limits your ability to tailor this valuable engagement towards different types of users. Alternatives also do not integrate with existing knowledge bases, nor keep track of the guides or articles that the user has seen before.

PX approach:

Gainsight PX enables many Bot-related features including:

  • Creation of multiple KC Bots directly within the interface, which allows for a targeted and  personalized Bot experience. For example, oftentimes you may have different users with different onboarding goals, and PX can trigger the “right” Bot for that user in real-time
  • Designated analytics: all bots are equipped with full analytics, so product managers can  understand how many times users are accessing certain articles and which features users are most interested in learning more about
  • Embedded feedback option: A feedback tab in the Bot allows users to reach out for assistance and provide feedback at any time
  • Integration with knowledge bases: integration with your existing knowledge base allows you to serve up articles without requiring users to leave the application and go to another site or page

Automatic Engagement Throttling (Including Cross-Product)

Throttling controls how often a given user will see engagements in your application so you don’t overwhelm them. You will likely have multiple engagements (pop-ups, guides, etc.) running at once to different user audiences that could overlap. As a result, it’s critical that your tool be “smart” enough to know if / when to show an additional engagement to a user to minimize inundation. This includes cross-product, where a user may be using multiple products on your platform.

Alternative solution gap:

Alternatives only allow throttling based on time between engagements. To accomplish what is standard with Gainsight PX, you need to manually manage the volume of engagements between timeframes, which quickly becomes cumbersome and / or creates a negative end-user experience.

PX approach:

Gainsight PX allows you to throttle engagements automatically based on the minimum time gap between engagements and / or by the maximum engagements in a day/hour/minute. This gives you the flexibility to ‘set it and forget it’ and not worry that your users are being overwhelmed. This throttling capability extends cross-product as well, which takes into account the fact that a single user may be engaging with multiple products — but demands a unified experience.


Paywalls are used to block access to a premium offering until an appropriate action has been taken. For instance, a paywall disappears after paying for the premium offering. Paywalls are one of the many in-app engagements you can use to introduce product features in order to drive growth for your organization.

Alternative solutions gap:

Alternative solutions do not provide an out-of-the-box paywall solution, making it difficult to encourage action without restricting access to the entire platform.

PX approach:

Gainsight PX enables you to put up paywalls without needing to build them into your codebase. Furthermore, PX gives you the ability to precisely target which users to present the paywall to as well as gives you the flexibility to restrict specific areas of your application rather than the entire platform.

Out-of-the-Box In-App Feedback Options

Capturing user feedback and sentiment is critical to building a better product. In particular, purpose-built survey analytics enable you to derive the most meaningful insight from your surveys, correlating sentiment to feature use and identifying key areas of focus for future product initiatives

Survey feedback can be structured and collected in many different ways (e.g, via NPS, CSAT, multi-question surveys, etc). Each of these has a specific use case, so it’s important to be able to easily create different types of surveys.

Alternative solutions gap:

Alternative solutions require you to piece together surveys out of a format meant for a guide, taking time and increasing the risk for error. This also restricts the ease to analyze the data in meaningful ways.

PX approach:

Gainsight PX offers native survey capabilities with out-of-the-box templates for each survey type to capture user sentiment and feedback. This enables you to quickly and confidently build and launch the right survey for the right situation.

Multi-Channel Product Engagement

As powerful as in-app engagement is, sometimes you need to reach users via email. It could be because they are new (and not actively in your product), because they are inactive and you need to reactivate them, or simply to be extra sure they receive a message about a critical change.

Native Triggering of Emails Based Off Usage

One of the most powerful use cases of a product analytics / email combination is the ability to target emails to users that meet certain criteria. For example, you may want to send an email to users who haven’t logged in in a certain number of days. From there, those who opened or clicked the email can receive a tailored in-app message reinforcing the email upon logging into your application. You are then able to track feature usage impact based on this coordinated, cross-channel messaging strategy.

Alternative solution gap:

Alternative solutions require an Email Service Provider (ESP) integration in order to enable this use case. In addition, not having this capability natively within the app translates to messy reporting and lack of coordination with other in-app engagements.

PX approach:

Gainsight PX enables you to trigger, design and launch emails based on application usage (or lack thereof)—completely natively within the application. You can also coordinate these emails with in-app messages as part of a holistic engagement strategy.

Seamless Cross-Channel Engagement Enabled By Customer Cloud (Product & Success Alignment)

In order to drive a truly best-in-class customer experience, in-app engagement and emails must be designed and triggered logically and seamlessly so a user’s experience with your company doesn’t feel disjointed. In addition, there are times you may want to reach out in-person to an individual (like an Exec) at a customer who is not in your product day-to-day, but is a key decision maker. How and when you engage with all of the personas at a customer should be carefully mapped out and orchestrated.

Alternative solution gap:

Because alternative solutions do not integrate seamlessly with other customer journey or customer success platforms, it is much more difficult to ‘orchestrate’ this kind of customer journey. You cannot visualize what the multi-channel outreach strategy will look like, nor segment it by persona type.

PX approach:

Because Gainsight PX sits within the Gainsight Customer Cloud, you can leverage the Journey Orchestrator capability within the Gainsight CS product. This capability allows you can map out in one visual pane exactly when, how, and to whom you want to engage at a customer. Based on how the target responded to the previous step, you can adjust what type of engagement he or she sees next. In this way, you can keep all of your touchpoints organized in one place as well as drive a seamless experience that cuts across all levels of a customer organization–from user to Executive.

Better Application Performance

You shouldn’t haven’t to compromise on your application speed as you introduce more in-app engagements to guide users. In addition, as a product leader, you want to be able to conduct deep analytics on large datasets—which means your queries need be able to crunch quickly.

In-App Guides That Don’t Slow Down Performance

Alternative solutions gap:

Alternative solutions make a lot of network calls as the browser is loading the application. This can cause up to a 2-3 second slowdown in load times for pages, which severely impacts your end-user experience.

PX approach:

Gainsight PX is 100% server-side and, unlike alternative solutions, was built specifically for SaaS applications (versus websites). This means you can run as many engagements as you want to different, targeted audiences without slowing your application down.

Security Built for Enterprises

Enterprises have strong security requirements for the way data is is stored and accessed. We understand that, which is why Gainsight PX offers the access management capabilities, integration options, and security measures organizations need for effective cross-functional team collaboration. Gainsight also provides API support, support tracking for multiple products, key native integrations, HMAC Identity Verification, SOC 2 Type II compliance, ISO 27001, FISMA, is PCI compliant, along with GDPR compliance and EU Privacy Shield. Additionally, all data collected by Gainsight PX is transmitted over SSL, and is encrypted at rest to keep data private and secure.

Flexible Role-Based Access Management

Organizations often have needs around role-based access management; that is, restricting functionality and access of the product based on a certain user profile.

Alternative solution gap:

Alternative solutions may provide differentiated access management, but in predefined user groups (i.e., 5 groups with predefined access settings set by the tool) versus ones you can set up on your own. You would have to allocate each of your users into one of these groups, and can’t easily change what permissions are ‘turned on’ for each group.

PX approach:

Gainsight PX enables you create your own groups and customize your own permission settings for each group. This gives you the highest level of flexibility to define the user groups and associated permissions that make the most sense for your organization.

User Preference Settings

In today’s’ world where GDPR and user privacy is more important than ever, it is critical to give your end-users the option to not be tracked / to not have their usage data collected or even to not receive engagements.

Alternative solution gap:

Alternative solutions don’t provide an out-of-the-box way to set flags on end-users who do not wish to be tracked or who do not want their usage data collected.

PX approach:

Gainsight PX gives you the power to comply with end-users’ requests around tracking and collection of data. This capability is available out-of-the box.

Ready to try Gainsight PX?

Sign up for a free trial of PX today and test out these capabilities and more for yourself.