Product Experience (PX)

I had a customer that wanted to embed their onboarding videos from Google Drive into an In-App Engagement. Here are the steps I provided them: Prerequisites   The file can be any video type but must be under 10MB You need to set your Google Drive share permissions for the file so that your users will be able to see the video. Steps:   Open the video from GDrive (which will by default provide a Preview of the video). From the top right corner menu select Open in new window. Once opened in the new window select the menu again from the top right corner and choose Embed item... Copy the Embedded Item Code into your clipboard Click on the Code View icon from the engagement editor pane, and paste the code into the location where you want the video. In the example below, the video will be at the top of the dialog window. (optional) adjust the width and height in the inserted code. Unselect the Code View icon to see the results:

I am trying to leverage gainsight PX API so that I can POST information about how long a certain process takes (from the backend). So basically, I will have a call in Java that determines the time from method 1 until the app gets to method 2, then save that time somehow to Gainsight (along with other information like which process this was and possibly user information). Is this possible? And how do I achieve this?

Hello Folks! I'm attempting to build out a guide engagement in PX, and I have 1 dialog and a few tooltips beyond it. On each tooltip, I'd like to add the option to exit the tour, or say 'got it' or whatever button text, but the option to select Exit Button is greyed out until the last step in the guide. Is there a means to include an exit on each step?

The docs needs to be updated to let the customers know that "When they query the audience using the query builder, they need to select the Continent under the Inferred location section and not the continent under the "Location and Account Location". If they apply the remaning sections, the customer will not view any user records. thanks, Avinash.

What does "Other" indicate in the Product Analyzer flow? Are they unmapped features? If they are, how can I map them out so my path is clear?

Hey everybody, This question came up while a customer was testing a new feature. While trying to verigy it was working correctly they were not seeing this feature in the analytics. This is because with the filter "Last 7 days", today is not included. If you add a custom filter to include todays date you will now see data. Hope this helps. PX Support

Currently while we integrate SFDC with the PX, we have only the 4 types supporting (String/integer/ boolean/ number). While we search for the fields in the SFDC to map, the lookup fields doesn't show up. We should enable the "lookup" fields also to show up for mapping. Can we add the Lookup(alphanumeric ID) also to be mapped with the string type in the integrations.

Hi folks, One of our growth initiatives is to have numerous out of product nurture campaigns. We have open and click rates from our email providers, but want to track and launch an engagement once logged in within GPX. We've tried utm referrals with emails sent from Hubspot and Sparkpost. We've experimented in the following ways, but still haven't had any luck: Shortening the UTM Placing the full and shortedn UTM link with attributes as the "URL" and the "Referral" Removing the UTM all together Has anyone else experienced the UTM breaking or not being respected when triggering an engagement?

I recently worked with a PX customer that needed an automated way to enable Engagements within their Production environment. Their high-level, immutable requirement was as follows: When a fully tested and approved PX Engagement is ready to be enabled within the Production environment, no additional manual editing of the PX Engagement is permitted as part of our fully automated (scripted) Production deployment/update release process. If you do not already know, there is not currently an Engagement API available to can be used to modify/update and existing Engagement. When this Engagement API is available in the future, other options will be possible. However, working with the current PX version, here is what I was able to suggest... --------------------------------------------------------------------------------------- Assumptions The customer's Staging environment’s Product used to fully test, validate, and approve the PX Engagement for release is identical to the custo

For the given scenario, we were able to suggest creating a feature on a Submit button, then use that feature in the Audience Condition along with URL. This allowed the user to follow the specific steps and only see the engagement once complete.

Is there a means to integrate video hosting sites, like Vidyard? The use case I have is we have videos/webinars that we'd like to include into the Knowledge center bot, under it's own category. I could add them all manually, but that's kind of a pain, and a gap wherein any updates/removals to the existing content on vidyard might break things unless I manually go in and change it myself.

Gainsight's Enablement Engine allows Gainsight CS users to launch In-App enagements into Gainsight CS for purposes such as onboarding or communicating important Customer Success initiatives. One common request we see is the need to launch an engagement on only specific Dashboards from Gainsight Home. Here's how you can set it up: Step 1: In Gainsight Home, go to the first Dashboard to capture the URL. It is recommended you verify the URL by looking in the Audience Exploer as noted below. In Audience Explorer, search for your logged in email and select Full Profile. Under Recent Activity you will see the last page viewed. Right mouse click and select Copy Link Address. Depending if you are using Lightning or Classic your URLs will be different. My example will be with Lightning (because it can be more challenging). Step 2: Once you have the URLs, you wil need to grab the first part of the URL up to HomePage and then the 18 character id at the end of the UR

The other day I was having trouble with a Guide engagement launching. It was launching in the same window but for some reason when I launching in a new window it was not triggering. Found out (by going through advanced troubleshooting below) that the URL in the new window had a double slash which was causing the problem. Once I corrected the audience URL rule, it launched. Here are some of my troubleshooting tips I take when determining why my engagement will not launch. Troubleshooting Checklist Ensure you using the right product - if you have multiple products you want to make sure you have the right one selected Check the Schedule From date and Time Zone to ensure they are correct [img]https://uploads-us-west-2.insided.com/gainsight-us/attachment/Scheduler-70bc69d6-41d6-4ffb-9f6c-8f6341b4e15e-1802717610.png[/img] Ensure the URL you are using matches the URL that the Audience explorer is recognizing - Go to Audience Explorer & search on your

Hello PX Community! We're pleased to announce the launch of PX end user video training on Gainsight University! The first video training is now live called Overview and Anatomy of PX Engagements. In this course, you'll learn: What are Engagements? Types of Engagements and Use Cases The 5 Steps of an Engagement Walk through setting up in-product Engagement example FEEDBACK WELCOMED: If you have other topics that you'd like us to cover in video format, please let us know by commenting on this post! Thank you, everyone!

The September PX release is live in your orgs!    Highlights from this release include: Map your product within minutes with Instant Mapper Enable SAML for your Demo org Deeper UI Elements Tracking You can read all about the latest enhancements in the release notes.   Please note, we're in the process of transferring the PX documentation to support.gainsight.com. In about a week, we'll have all of the PX docs available there, and the old site and pages will redirect to the above url. Thanks for your patience during this transition!

As a Gainsight PX and Gainsight CS customer, you can push surveys to customers in two different ways: either through engagements within your product or by email using Journey Orchestrator. I believe that you should use both methods to collect real time feedback from your users and contacts. However, I do believe that each method has a better audience and feedback focus. For Gainsight CS using emails, you are asking someone to take a moment from their day and click into an unknown dedication of time. This will lead to more thoughtful responses. I also think you will get better feedback by asking questions around ROI and company product adoption. To me, the target audience should be your champions and sponsors, the ones that ultimately make the decision come renewal time. For Gainsight PX using in-app engagements, you are presenting a user in the middle of their workflow to give feedback about their experience. I believe you will get more reactive feedback this way, but will help you u

You likely have hundreds or thousands of users to keep track of. How will you know whether someone has a negative sentiment on a given day? How will you stay updated if someone gives you a high rating? How do you take real-time action on at-risk users? Assuming you have NPS survey engagement(s) active in Gainsight PX, you can enable the Slack integration in Settings > Integrations and allow survey responses to surface up in a designated Slack channel for PX. Your Customer Success teams can then take proactive action and reach out to Detractors and manage the risk. They can also reach out to Promoters and ask for a positive review on public review sites, like G2Crowd. Additionally, you'll also be able to track user sign-ups, email engagement activity, user feedback, and engagement management activity (ex. Engagement paused, launched). Click here for more details on enabling the Slack integration: https://docs-px.gainsight.com/integrations/gainsight-px-slack-integration

Hey Guys, This use case came up the other day and has me stuck. Has anyone else seen this issue and come up with a workaround?.... Any input would be much appreciated. Use case: I have a URL https://abc.com/xyz3/manage/alerts/edit/1234(dynamic number) https://abc.com/xyz3/manage/alerts/edit/new I have an Edit Button on both the pages, with same ID(same selector) Can I track Edit button on https://abc.com/xyz3/manage/alerts/edit/1234 separately from the edit button on https://abc.com/xyz3/manage/alerts/edit/new Query: Since I will use scope as https://abc.com/xyz3/manage/alerts/edit/* And selector as same ID, will both the features be called when I use any one?

Can the product mapper do what tooltip/hotspot engagements can do--target a part of the product by looking at the text inside an element? I have a bunch of generic buttons and am wondering if there is an alternative to asking dev for some ID tags on them. (Ultimately, I want clicking the Save button to trigger an engagement.) Thanks, community!

A question came up this week when seeing this error in the Knowledge Bot. In this scenario it was an easy fix and should be the first place you check to avoid any headaches. When creating the Sub-domain you do not need to include the .zendesk. After making this change all worked as expected. So remember to check here first to save you some time in the long run!! Thanks, PX Support

It would be awesome if the tool could "pop up" with suggestions when someone is completing a task (specifically during first couple of week? that they become an administrator). For example, if someone is completing Task A, the associated workflow would pop up "I see you are creating Task A, would you like step by step instructions". The user could then choose to snooze or disable to pop ups.

Today, we launched the PX Knowledge Center bot in your PX instances. From the KC bot, you can view getting started materials, including engagements, links to articles and release notes, and more! On the Knowledge Base tab, you can search for any topic and preview our product documentation. PX can integrate with some of the largest documentation vendor apps in the market, such as Salesforce, Zendesk, Mindtouch, and helpdocs.io.To learn more about configuring the Knowledge Center bot in your own web app, check out this article.   Click "read more" in the article preview to open the article in a new window.And on the Onboarding tab, you'll find links to getting started docs and guides.   Try out the new Knowledge Center bot, and let us know what you think!

Gainsight's Customer Success Operations Manager, @kendra_mcclanahan, shares two uses cases developed to drive customer value and strengthen customer relationships. Learn more in this blog post here.

I'm having a usability issue that's making it very hard to use PX for guiding a user through a very basic tour. Here is a video overview to explain: Basically I'd like to setup a 2 step guide here: Step 1: Dialogue [list] Next Button [list] Navigation: Opens my drop-down menu from the top-navigation [/list] Step 2: Tool-Tip Points at the second item in the drop-down [/list]However, it doesn't seem like I can force a drop-down menu item to open from within PX. Instead I'm having to do the following: Step 1: Dialogue [list] Next Button [list] Navigation: Look for next element [/list] Step 2: Hotspot Overlaid on top-navigation button [list] If user clicks on hotspot: [list] Hotspot disappears Sub-menu does not open [list] The user now must click on the sub-menu in order to see the tooltip (Step 3) [list] This is a bad user experience. The user has to click twice in the top-menu. [/list][/list] If use

Whenever thinking of an Engagement, start with (you could even create a calendar, see pic below): Objective/ Problem Statement (Why) Metrics Improved (Why) Storyboard/ Engagement Type (What) Audience (Who) Duration (When) Using this Framework has the following benefits: Objectivises the need of an Engagement hence eliminating the ones not really needed Quanitfies the desired impact of an engagement Simplifies defining the audience criteria and rules Provides visibility to multiple teams into the planned engagements Enables various teams plan engagements in a way to avoid duplication/ overwhleming users with too many engagements