Skip to main content

Our organization has many products (20) and our Accounts can have multiple products. The problem is that Account Custom Attributes are global and if each of our products sends a value (Version 10.8, or 11.2) then all of our products are competing for the one default attribute of “Product Version”. 

We are going to have to setup 20 custom account attributes just to track version numbers for each account on our products. I wish there was a better way of having custom attributes per product rather than having to have what will end up needing 100s of custom attributes simply because we have so many products. This management of custom attributes is a mess with the number of development teams we have touching the Gainsight PX portal. 

Great suggestion @Ashton!  

 

In cases like this, we recommend using either (1) a pipe-delimited list of values in single PX User/Account custom attribute field, which supports up to 2,000 characters, or (2) having the tracked application pass those user sessions specific values as Global Context properties to be stored with all the usage events.

 

 

Terms & ConditionsCookie settingsAccessibility statement