PX Product Ideas
PX Product Ideas
- 642 Posts
- 1,408 Replies
Currently, after you upload XLIFF files to an engagement to provide translations, you are not allowed to modify the engagement. This means that to modify an engagement after a translation has been put in it, you have to take the following steps:Store the original XLIFF file Remove the translations from the engagement Update the engagement with the changes Re-export a blank XLIFF file Add the translations back into that blank, new XLIFF (likely using a 3rd-party diffing tool like Winmerge or Kdiff3 to facilitate) Re-import the translations.This is a pretty painful process, and means that we can only really upload translations and validate the engagement in other languages once the engagement is really, really done.It would be nice if Gainsight would:Allow editing the engagement after translations have been uploaded. Highlight engagements on the Engagements page that have been updated after they have translations, but that haven’t yet had their XLIFFs updated in one or more languages. Th
Hello Community users, Use case: I want to convert the feedback from KC Bot as cases into Salesforce. Is that possible?Yes, it is possible. How?Need to enable email forwarding on PX subscription and Email to Case on your salesforce Subscription Any Prerequisites?Enable Email to Case on SFDC Enable KC Bot Feedback option in PX Enable Email Forwarding in PX with Email Services Address Configure the Email Forwarding on your mail settings (IT team can help) I prefer to check the email domain settings and forwarding settings with your IT team before doing it. Any Live Walkthrough Session?Ofcourse, yes, watch this video recording: Click Here to Access the VideoThis video explains the basic overview/outline on creating the email to case. ThanksDileep Nalla
I’m running some data through Path Analyzer and the information is interesting. However what I really would like to see are the quantitative number behind each path. Is there a way to export this data to CSV for further analysis in a spreadsheet?
In the Product Mapping process we often have existing rules or features we want to duplicate but with just a couple of tweaks. For example, here is a feature that captures pageviews across various, similar pages: I’d love to create a feature similar to this, but with a UI element tagged on it. To accomplish this right now I have to open two browser windows and copy paste all the URLs into the new feature. Can we get a “duplicate” button for a feature or rule that will simply let us duplicate it and, ideally, update the type, i.e. from URL rule, to “Tag UI element”?
Knowledge Bot LocalizationImplemented
Posting on behalf of Trimble MEP (PX customer): Product Request: Language localization for Knowledge Center Bot Business Case: As a global company, it’s crucial to target customers with their respective language in order to properly onboard and train them. If the language is not localized: Some users may get confused and not know how to submit feedback. It looks like we were ignoring the language of our customers, when in fact there's nothing we can do about it. There's some sensitivity with customers around the world about the dominance of English. cc @angelo @mickey
Please add "Last Browser" and "Last Browser Version" to the available filters in PX AnalyticsNo Status
Posting on behalf of a customer…. Please add "Last Browser" and "Last Browser Version" to the available filters for Audience Explorer, Dashboards, Adoption Explorer, etc. within PX Analytics. We need to be able to easily report on these users in PX and the “Browser usage” Dashboard widget does not allow us to see the underlying user/account records. Gainsight PX add-on comments…You cannot currently filter users/accounts by these “Last Browser” fields. PX records the "last browser" and "last browser version" for each user, so it can change often for some users. The best way to see this and get a full filtered list of users/accounts would be to export your full Users to a CSV from Audience Explorer and then filter it in your spreadsheet program (e.g. MS Excel).
Hello team and @harshibanka , It would be better to track the stats of the articles that which are being viewed. It would be nice if we can also track which article is being opened quite often and maximum times and which article is being opened minimum. Presently we only track the stats of the engagements in the KC bot but not the articles in the KC bot. thanks, Avinash.
We have use cases where we would like to tag a “New” labelnext to some UI elements to raise attention to new features being introduced. This label will be persist until the guide is removed. However we can’t achieve this behavior as Navigation Bar section requires it does something (navigate to the next step or redirect). Please consider to add an option to do nothing in the dialog below
Product Feature Tree - select many to rearrangeUnder Consideration
Hi, we have a lot of features landing into Product Feature Tree. It would be very helpful if I could select more than 1 to move over to differend modules etc. Doing it one by one on every release we have it's a lot of manual work. [url=https://community.gainsight.com/users/link_black]@link_black[/url]
Currently in Analytics (Engagement performances), "Add filters" options is limited to only "Survey performance". Can we make this feature(add filters) available for "In-App performance" also. If we want to apply features, we can add widget in dashboard of particular engagement,but the downside is It will display only one graph. Having a filter at the In-App performance would be helpful to take out the non-applicable users in the numbers of who viewed the individual slides in the slider.
Number of Users as filtering optionAcknowledged
USE CASE: With the current PX design, we don’t have the ability to use the “Number of users and Number of visits” attributes as the filtering fields(In account filters). Even though they are standard/default attributes, we cannot use them in filters. So it would be difficult if we have to filter out some customers/accounts who have more than certain number (x number) of users. For e.g: I want to filter out accounts who have more than 100 users. This can be achieved only if we can filter out by using the “Number of users” attribute as a field in Account filters. Here is the sample image,
integration with LogRocketAcknowledged
My organization is using LogRocket for session replay, and is very heavily used by our PMs, UXers, Devs, QA, and Support. Apart from session replay, provides a lot of log information and captures detailed session history information from several modern tech stacks. In particular, its capture of action logs from Angular + NGRX has been useful. We would love to be able to have LogRocket integrated with Gainsight in order to tie user sessions with events tracked in Gainsight, and to be able to further use Gainsight as our primary customer success hub.
Right now, In the Email Engagement Audience criteria we can use Survey/Email engagements as trigger options but not the In-App engagements.Here we need to improve the consistency, because we can use In-App engagements as Audience in All engagements except Email.
Currently, when we integrate the slack with the Gainsight PX, We are providing only one channel where we can receive the notifications. Can we make it possible to add the multiple slack channels while integrating, so that we can configure like “within each channel establish unique channel specific alerts”. For Example, USE CASE: I’ll create the multiple slack channels called Engagements channel, Account channel, Audience channel etc. Then While integrating,I want to map “Engagement related notifications to #Engagement_channel.” “Accounts related notifications to #Account_channel.” “Audience related notifications to #Audience_channel.” “Leads created -> #BDR_Leads.” “Feedback received -> #ProductManagement or #FeatureRequest.” **With the current design, we can set up only one channel for all the notifications.
It would be nice to be able to calculate and trend custom adoption metrics in PX (both global, per account and even per user), for example The percentage of users using a group of selected features (to see what percentage of users uses basic, advanced or expert functionality). The ratio of advanced feature events vs. other selected or all events Being able to calculate this per account and, for example, plot advanced feature usage vs. usage frequency would provide an interesting overview of the accounts for segmenting (e.g., accounts with high usage frequency and high adoption of advanced features vs. low usage frequency but high advanced feature adoption) A similar representation on the user level would allow selecting power users or targeting selected users by campaigns to either increase usage frequency or advanced feature adoption.
PX Product Environments should maintain entirely separate User/Account records and should not share dataWorkaround Available
Submitting this on behalf of a customer… Background:Having different sets of account/users within each PX Product Environment is normal and supported by PX. However, PX adheres to Unique ID principles and there can be one and only one User/Account per unique identifier across all PX Products and PX Product Environments. Challenge:If Users/Accounts share the same unique identifiers in different PX Product Environments and are passing different User/Account attributes (e.g. names, email addresses, custom attributes, etc.) then any changes are updated across all Users/Accounts within that PX Product in every PX Product Environment. Additionally, any tracked usage in ALL Environments is also visible on the User Profile → Recent Activity section and is not correct. Request:Allow PX to support this model so we do not need to worry about matches to unique identifiers in other PX Environments altering data in a different PX Environment. Most companies I’ve worked for have completely unique s
Conditional survey stepsPlanned
Background: We’d like to track additional data for negative user sentiment. In this case, my goal is to make PX show users a step with a free textbox only if their NPS rating was 1-4. If the user clicks 5 or above, they'd like to show a step that says 'Thank you for your feedback!'. Target flow: Step 1: Rating survey; user clicks rating Step 2: If user chose 1-4, show a textbox asking for feedback on negative experience. If user chose 5-10, skip this step Step 3: Thank user for feedback Problem: We believe that if the rating selection and feedback box (steps 1 and 2) are combined into the same step, users will change their answers when they see the label above the feedback box ask them why they gave a negative response. Because of this, PX’s dynamic label offering does not solve the problem. Request: Create multi-step surveys that show users different steps based on their ratings.
If I have a lot of engagements but my company changes its branding, or creates new templates to standardize its style, I would like to have a smooth process to update my old engagements to new templates where I can update the engagement to a new template with preserving content. Many larger organizations will have hundreds of engagements across multiple types, and updating them all to match branding or style changes could be prohibitive. My organization is currently facing this with 75-100 active engagements and it’s giving us pause.Understanding that the content is not necessarily tagged in such a way that makes it easy by default, I imagine this having something like the following workflow:Go to the Templates tab Choose a new template Confirm whether to overwrite existing content or to migrate content (rather than current “this will overwrite existing content” message) Have side-by-side view of the old engagement and the new template, and allow for drag and drop of new content into d
Hi team, We’d like to have the ability to designate a preferred slack channel per engagement, so that eg all of our NPS surveys can be sent to an nps channel, all of our CES surveys can be sent to a ces channel, and so on.Currently the PX Slack integration is all or nothing - so with the integration on for survey responses/feedback, all responses to any survey/feedback engagement are dumped into a single slack channel. This becomes very messy to manage when you want to have different survey engagements running at any given time, and where surveys differ in relevancy across the staff who would be monitoring them in Slack. Cheers, A
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.