PX Product Ideas
PX Product Ideas
- 18 Posts
- 1,409 Replies
Ability to view the data of more than 6 months in analyticsWorkaround Available
Use case : Currently in PX we are able to access analytics data only for 6 months, as the customers are growing it would be really great if they can access more than 6 months data, Customers are sometimes frustrated when they cannot view the complete data.
Account Level Filtering for PX dashboardsWorkaround Available
Hi, When we’re building dashboards in PX, we’re able to filter out on environment level (prod/qa/dev..) only. Currently, If I have to build a dashboard of metrics for multiple accounts, I’ll have to build N number of dashboards.Can we include account level filtering so that I can build a single dashboard and use filter to view the data for multiple accounts?
PX Engagement Design - Ability for engagements (KCB and otherwise) to honor thematic UI changesWorkaround Available
Our portfolio products all have a dark theme and a light theme, and we were hoping PX is working on a way to notice the theme the user has selected, and thus allows us to use audience rules on the KCB and/or engagements to display an appropriate experience. Is this on the roadmap or being discussed in any way?
Bulk Upload recipients for email engagementsWorkaround Available
Hi Everyone, We have some tools that we have integrated with Gainsight PX and we wanted to look at possibly sending an ‘end of contract’ email to them alerting them of their account closure/access removal.We aren’t currently able to differentiate users from an active/inactive status within Gainsight (say for example a user has left the company and does not need access - Gainsight has no way for us to opt them out).If we could upload a userlist of active users from our tool to Gainsight PX, it could help us target the right people and avoid confusion of people getting irrelevant emails (or spam). I understand we can copy and paste individual names into the audience tab when using the Email Address option, but this is an individual email address - and given we have some clients with 500 users it would be very time consuming to manually add everyone.If we could upload the list to a segment (e.g. CLIENT A - ACTIVE USERS FEBRUARY 2021) and then have that segment as the selected audience - t
Browser language as standard user attributeWorkaround Available
For our scalability initiatives, it would be tremendously valuable to have browser language as a standard user attribute in Gainsight PX (and exportable to S3 and Gansight CS). We are creating Gainsight CS contacts based on user data from Gainsight PX, which we leverage in the Journey Orchestrator. However, as browser language is not available in the export (although used in Localization), we are not able to address our users in their own language (which is very important for our German customers, for example).
Default new Dashboards to PrivateWorkaround Available
Posting on Behalf of a customer here. Currently whenever someone in the company creates a test dashboard it's instantly being showed publicly to all users and it leads to confusion and a clutter of dashboards for everyone in the company. Also when companies are sensitive to who sees what dashboards, it is easy to be unaware of what material is showing in dashboards upon creation. Suggestion would be to have dashboards private by default and then made public or shared with team members. -Mike
split step is missing when creating a guideWorkaround Available
When we create a guide that starts from a certain feature and there are two ways the user would like to proceed with the guide, we don’t have the option to present it to the user unless we lead the user to a separate engagement. here is an example: Is you content promotional or operational? promotional → new content/ previous content…. operational→
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
Ability to add multiple values at once in PX filtersWorkaround Available
Post on behalf of a couple of customers: Currently when trying to add values in the filters in PX we can add only one value at once and there is no option to either upload a file containing values to be added.It would be very useful and makes life easy if we have an option to upload/add multiple values in filters in one go instead of adding manually each value.Use case: If I have to add hundreds of account/user id in the account/user filter, currently I have to type all those hundreds of id’s, it would be great to have option to make it simpler.
Robot Font is not getting reflected in the End ApplicationWorkaround Available
Hi All,Roboto font is used by the PX application and that it is available in the Editor. However, Roboto is not a web safe font, and it is unavailable/not getting applied for the customer application. if the customer wants this font to be available he needs to add it by himself to his application.To get rid of this, it will be helpful that specific fonts should be loaded by the PX-SDK only.Regards,R Satheesh
Export previously uploaded XLIFF file in PX engagementsWorkaround Available
Currently, when you export the XLIFF file for an engagement, it exports just a blank file based off the base English engagement, rather than the existing XLIFF file. I believe the intended use case for re-exporting an XLIFF file is when the base engagement changes and thus the <source> tags (at least in XLIFF 2.0) change as well.However, our PMs are finding they frequently want to:Make small translation changes that aren’t based off changes in the base engagement. Make small changes to the base engagement that don’t require a full re-translation, just a few modifications to the XLIFF.This means that in order to avoid fully re-translating when we have a small translation or engagement edit, we have to maintain our own repository of our previously uploaded XLIFFs.We would like the option to re-export the currently populated XLIFF file instead of the blank one, as PX is clearly already storing them.
Text box in Multi Question Survey TemplateWorkaround Available
In Multi Question Survey of PX, We have two templates one includes the Question and One includes the additional text. But Can we have a option to have a extra text box in Question template itself? USE CASE: Once we ask a question, we will give users to select one option. If the options we have provided doesn’t work for users, We will provide an option called “OTHER”. So In most cases, we would like to know what customer is referring as OTHER, So If we can provide a text box in the Question template itself, It would be helpful for us to know what user is mentioning. More Clearly with an example: “I am asking my users what CRM they use and the options to select are Salesforce, Hubspot, etc. and I'd like to add an "Other" option where the user can type their own answer.”
Allow Metropolis or Helvetica Font in PXWorkaround Available
posting on behalf of customer, In PX, We knew there are different font families and styles we can use in customisation. Can we add Metropolis or Helvetica as an additional fonts in PX. These will be helpful for customer to customise their Engagements more effectively. Thanks, Shireesha
User Roles for API AccessWorkaround Available
Problem: The only way to grant PX API access to an engineer is to give them 100% Admin control over everything in the platform. I love engineers (used to be one) but come on...I don’t trust them that much. Solution: Add role-based controls for API access. Please make sure read-only is an option vs. read-write.
Manually Edit User or Account Attribute VALUES in Gainsight PXWorkaround Available
USE CASE:I have a custom account field for companies who’ve elected to NOT receive engagements. So I want to edit the attribute value for the specific accounts based on customer feedback whether they should receive the Engagements or not, and this can be used as a rule in audience criteria in the Engagements (Display the engagement If the custom attribute value is true only). I’d like to be able to manually change it within PX without an unnecessarily heavy API process. Other Solutions We have:If we have the integration with SFDC, we can create a field in SFDC(Account/Contact) and Create a custom attribute on Account/User in PX and sync the value We can update the field using the API’sHowever, there is no way to edit or update the field value manually. Video Recording of the Use case:https://www.loom.com/share/710003bb467549089de8cb6d7cc7090e ThanksShireesha
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.