PX Product Ideas
PX Product Ideas
- 663 Posts
- 1,452 Replies
Submitting on behalf of our customer… Since the Gainsight aggregated default reports contains daily data, how to get data for the days when the integration was down/broken? How do we get historical data? Our S3 integration was in Down for 3 days due to AWS keys issue and the only way I was able to find out that by manually checking files on S3 and/or Gainsight Admin console. It would be great if PX provided the ability to execute missed/historic runs with PX Amazon S3 Integration. Also, if PX knows that the integration was down/broken then it would be great if it would automatically process and export the missing days once.
Submitting on behalf of our customer… The only way to know if the PX Amazon S3 Integration export jobs were successful is to review the status of the AWS_S3_PUSH job in the PX Admin Console. It would be much preferred if we could get notified in case of failure in exporting Gainsight reports to the S3 via email/MS Teams and/or hook it up with PagerDuty.
I didn’t see anything in the PX forums for this, but when I create an email and sent a test, there is an automated footer with an Unsubscribe link and a View in Browser link. These are nowhere to be found when I am editing the email, and I have been unable to locate it anywhere. Our marketing team doesn’t like the phrasing, plus we don’t know where the unsubscribe link is directing users.I did find an idea on the CS Product forum: Custom Headers/Footers for Email Templates | Gainsight Community and posted this comment: “This would be a request for Gainsight PX as well. I am starting to explore emails from PX, and there is an automated footer with an unsubscribe link and a “view in browser” link. I don’t know where the unsubscribe URL goes. It is not something I can see to edit or delete. It is not a part of the template I can edit. We don’t have CS now, so I don’t know how the experience differs.”
We want to present two KC Bots with different content: 1) Audience is the admin role for initial onboarding and 2) Audience is all roles.After the admin completes all initial onboarding tasks, they qualify for the content in bot 2.
Would like to simply track the Category and the number of selected labels as a way to measure feedback. Make Subject and Description optional selections.Alternatively, provide an option for like / dislike with a few options for recording why it was liked or disliked.
Have option for "Completed" Engagement StatusAcknowledged
I recently had a scheduled engagement so users could register for a live webinar. I only wanted the engagement to appear for a couple weeks, then stop. I’ve noticed with other scheduled engagements the Status will change to “Completed” after the date range used. With this recent engagement, I also had it displayed in the bot, so users could find it there as well. The scheduled was set to expire at 9:00am today, then I removed it from the bot. The Status is still showing as “Active.” My suggestion is that we have an option to change an engagement status to Completed. That would make it easier for filtering and reporting. I know that I can change the status to “Paused” but that is not an accurate designation. Plus, then in the “Paused” category when filtering, some of them are paused (for editing, etc.) and some of them are Completed.
Hi,Please add ‘Last active’ column in the User Management section of the tool. This would help us to get an idea of how often our employees are logging in to G.PX and when was the last time they had any interaction.This would help us to evaluate how much effort has somebody invested in learning the ropes of the tool before they come to us with the questions or complaints that the tool is easy or difficult to use. We could use this info to better structure our internal PX education for our employees.Generally more data about the PX usage of our employees would be really great to have. Number of created reports, time spent in the tool in the past 7 or 30 days, last active date, number of logins in the past 7 or 30 days, number of created dashboards/widgets, etc.
Add Date to BackfillNo Status
I’m using backfill typically after a release happened and I am getting the new feature and use into product mapper. I know the date that the feature went live, so it would be very easy to just use that date to search the relevant events. Any searching before that is pointless and is a waste of resources and time.
Bulk upload engagement recipientsNo Status
Hi everyone! Whenever someone in my organization comes to me for an engagement, they always send me emails for the users we want to share the engagement with. It would be super convenient to be able to upload the emails into a segment without having to use the data loader. For example: adding a comma after each email so when we copy and paste it into the segment, Gainsight PX will recognize that and upload the emails individually. This is just one idea for uploading the information, but the main point is being able to add the user information into a segment without having to use the data loader.
Hi everyone, When checking the performance of guide engagements, we feel that it would be more useful to be able to observe the data as a funnel (on user level). In the current setup, we are able to see the total number of times each step was viewed and the “completion rate” is then calculated based on those numbers. In example:let’s imagine that 10 users started the guide and only 1 of them completed it (saw the last step of the guide) and let’s imagine that the mentioned user completed the guide 10 times (while the other 9 users started the guide only once and never completed it)With the current setup, the “completion rate” of this guide would be calculated as:(10 times completed)/(19 times started)=52,63%And the question is - when estimating the performance, usefulness or design of a guide, are we more interested in this information or in the information about the share of users who started and managed to complete the guide (1/10=10% in the above example).
Hi everyone,It would be great if you would prolong the time horizon for daily retention stats at least to “Day 30 Retention” which is a standard in retention analysis. In the current setup, when selecting “Date Range = 30 days”, we’ll get the data for 30 daily cohorts, but only up to Day 12 Retention.If I’d need to choose between the two, I’d even say that it would be far more useful to have it the other way around when choosing to check daily cohorts - to get retention stats for 12 cohorts, but up to Day 30 Retention.
Add simple search within user management of PXAcknowledged
Currently in PX, within User Management, there is no search bar that allows me to easily find a user who has access. If I need to update just one individual user’s permissions, I must scroll through pages of users to find their account. Please add a simple search by name or email that allows me to easily locate one of my users.
Hello to PX Product team, I would love more user management for PX end-user. Better analytics around access and control over access for users. As well as ability to inactive rather than delete. Additional profile fields to help us understand our stakeholders and responsibility. An open text field would be great for notes on our end-user. For security reason we need to be able to manage our end users. who has access to what pieces of PX. We have close to 86 users and there is no auditing trail for changes. So you can see the need here. Best Regards, Darshana Shah
Tree Edit AttributionNo Status
I love that I can see when a feature or module was created or modified, but I often wish I could see WHO created or modified them. BONUS POINTS if I could access an edit history for each module and feature!This is important because we have several people empowered to add new features and modules to the Product Tree — as long as they’ve completed some specific training from Gainsight University. 😉Sometimes things change and it’s not always clear why. So if I’m trying to maintain a high-quality Product Tree while also empowering our product team, I often need to hunt down who last edited a branch. Sometimes nobody knows who did it so it seems like the change was done by mistake.
Community Votes requested for Exporting of Contextual Localization xliffs - units in sequential fashion needed urgentlyNo Status
Currently the content in the xliff is not reported in a sequential fashion as the content of the engagement in every line will be segregated into units randomly and therefore the same is exported in the XLIFF file.This random html unit content is extremely difficult to follow and makes translation very hard to do in a quality and efficient manner. The translator must find the random units in order to review several sentences in the context and order that is required. Community- please vote for this request. Your vote matters. I appreciate you and will pay it forward!Please provide a solution - Gainsight team! Thanks and many blessings!Janine
We would like to use the Feedback feature in the KC unified tab layout. It would be great if the user could click “Feedback” and the Feedback form shows as a second page like the image belowPlease let me know if this will be possible. We would like to collect feedback after implementation, which is happening soon.
We are using Crowdin as a translation platform and they have built a really great connector for Gainsight PX. We have asked them to add some automation to the connector to sync files based on the engagement translation state. However, I have searched and searched the PX API, and I cannot seem to find this exposed anywhere so the connector could use this. Use Case: New content is created or edited in PX. The designer changes the Translation state to “Ready for translation”. Crowdin connector automatically syncs only files that are in “Ready for translation” state. If the translation state was exposed in the localization export API, it could update the state to “Translation in progress”. When the translation is completed in Crowdin, the connector can then automatically sync the translated file back to Gainsight PX using the localization import API. And if the translation state was exposed in the API, it could also update the state to “Translation complete”.
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.
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.