Skip to main content
New Idea

Gainsight PX Attributes Blocking

Related products:PX Admin & Security
Yoeri
Kenneth R
Joris
dilekgencer
Kseniya
+5
  • Yoeri
    Yoeri
  • Kenneth R
    Kenneth R
  • Joris
    Joris
  • dilekgencer
    dilekgencer
  • Kseniya
    Kseniya
  • rashmin
    rashmin
  • HaikoK
    HaikoK
  • Jeremie
    Jeremie
  • L.L
    L.L
  • Ryadom
    Ryadom

Ashton
  • Contributor ⭐️⭐️⭐️⭐️
  • 30 replies

If a product has implemented an attribute in their Identify call, then it is later deemed to be a data point that the company no longer wishes to have user send. The Attribute Management page toggle should be able to stop all instances of the Gainsight Identify call from sending this attribute. 

 

The underlying reason that this would be needed is in the event the specific piece of data is now listed as PII and the company does not wish to collect this data. As Security and Data Privacy laws change we need to respond quickly. Having to go back and remove attributes from the Identify Call code (from every product) is extra overhead that can be eliminated by Gainsight PX configuration. It would tell the browser side java script to omit any field that is deactivated via the Attribute Management page. (Similar to the URL Mask tool)

 

This can also be used in reverse. An attribute can be coded in advance for the future eventuality that we wish to enable the value and begin gathering the data. 

0 replies

Be the first to reply!

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings