Tip of the Week: Using a PX Dialog Engagement to collect additional information from your users to store on their PX User Profile

Userlevel 6
Badge +2

I had a great conversation with one of our PX customers last week about this use case.   


As a refresher, PX does not create PX Users and User attributes on its own.  PX relies on your user/account data to be passed through the PX Identify call code in your applications, developer inserts/updates using our PX REST API, imports/updates using our PX Data Loader, mapped fields synched with the CRM system using our Salesforce integration, and/or updates from the Customer Success platform using our new “Load to PX” CS Rule Action type.


All of the above are great options for creating rich PX User profiles with many attributes that can be leveraged for PX Analytics and PX Engagement targeting … plus many other use cases for sure.  


So, the specific use case that we discussed was… “In addition to application usage data, how can PX help us to collect additional user information that we do not already have available within our business systems, such as job role, job responsibility, interests, etc.?”  Well, PX has you covered here too!



Here is how it can be done…


Our PX Web SDK (JavaScript) API has a newer method available that can be used as a standalone JavaScript call within your application or even used on a Custom Button in a PX Dialog Engagement, which is the focus of this post.  This Javascript method looks like the following:


aptrinsic('set', 'user', {'[attribute_api_name]':’[attribute_value]’});"


[attribute_api_name] is the PX User Attribute API name from your Users Model in PX.

[attribute_value] is the PX User attribute value you want to record on the users profile in PX.


While you cannot add a bunch of JavaScript code to the source of a PX Engagement, you can make simple JavaScript calls when the user clicks a Custom Button using the “onclick” <a href> property.  You will need to edit the source code of your Engagement to do this, but it is not hard, and below is an example screenshot of how this can be implemented on a PX custom button:



And here is how the actual PX Dialog Engagement could look for your users:



As for Audience Logic, you will probably want to set this up to be triggered when the desired PX User Attribute field is empty such as the following:


And, for Qualification Scope you would probably want to give the user many chances to update their data with some time in between requests such as the following.




I hope this helps someone with similar use cases, but we would love to get your feedback and other interesting use cases that you come up with too.


Happy PX-ing!

11 replies

Badge +2

Thanks for sharing this idea in such details Link, this is very cool!

This very much tied with considering user context as we trigger in-app. The method you mentioned will help build/add attributes to the ICP (Ideal Customer Profile) which can be used to do very targetted user-segmented in-apps and analysis.

Userlevel 5
Badge +1

Hello All,

Thanks @link_black  for this impressive community post.

Here is a short video on implementing the above 


onclick="aptrinsic('set','user',{'role': 'Support Analyst' });"


Click here to access the video


Dileep Nalla



Userlevel 4

Thanks @link_black . If this can be sent using an “onclick” DOM event, could it in theory also be used in an “onchange” DOM element type of checkbox? This would allow a specific attribute to be sent to the user’s profile by checking off certain boxes in an on boarding questionaire.  Please see the example below. For some reason, this DOM event continues to get stripped from the HTML when I save the engagement.


        <div class="px-dialog-title">Please take a minute and let us know what you need to get done using this product.
<div class="px-dialog-content">
<p>Check this box for Testattribute</p>
<input type="checkbox" id="myInput" value="x" onchange="aptrinsic('set','user',{'attributeTest':'JPsAttribute'});">
<label> I need to learn how to add and manage users on my account.</label>
<p id="demo">
<p>Check this box for Testattribute2</p>
<input type="checkbox" id="myInput" oninput="aptrinsic('set','user',{'attributeTest2':'JPsAttribute2'});" value="x">
<p id="demo">


Userlevel 6
Badge +2

Hi @JPKelliher, thanks for replying.

PX does strip out unsupported/invalid HTML and JavaScript code automatically.  However, I was able to use your HTML above with the simple JavaScript code in a PX Engagement successfully.  See my results below:


In the case of using a form checkbox, the attribute is set with every select/deselect, so this may not be the best way to implement this use case.  Anyways, thanks for taking my tip to the next level!!!!! :)



Userlevel 4

@link_black  I am not sure if this is a bug or what, but Gainsight is stripping our the DOM event every time I try to save. I have tried this in several instances, along with several engagement types.


First it is there.

Code with simple java event


can see the checkbox with the WYSIWYG view


Then it is gone when I go back to the HTML view.

the DOM event has been stripped automatically

I have tried this in a Dialog engagement and a Tooltip engagement. Both with the same results. The strange thing is that this worked for us in test last week. :disappointed:

Userlevel 6
Badge +2

Please create a PX Support ticket for further review (pxsupport@gainsight.com).

Userlevel 5
Badge +1

Hi @JPKelliher,


Exposing scripting was determined to be XSS vulnerability on the templates, so considering this factor, those customers that were using it were added to an allowed list... but security blocked for others.



Dileep Nalla

Userlevel 1

Can you use this function for Custom Attributes at the Account level?


I tried this - 


but it did not seem to work, I can set user account values this way i.e.



Userlevel 6
Badge +2

@brian.atkins Nope.  But, check this post out to see how to do this with the Identify call. 


Userlevel 3

We have released a “No Code” solution to this on new Guide Editor. Please check the below release notes:





Userlevel 2

Edited to add: I got help from the amazing PX Support team and my issue is solved 😄


Hello everyone! We are trying to use this api call to update a user attribute. We are not using the no code solution because we are actually also utilizing a branching flow in this engagement to capture additional data points, but only showing the need to know steps to users. Unfortunately it does not seem to work as expected. The code in the new editor looks much different than the screenshots shared above, so I am hoping we set it up correctly, but any extra eyes on it to see what could be going on would be helpful. Thanks in advance!


<button data-gramm="false" data-lt-tmp-id="lt-461595" id="pxCustomButton-123e8338-34af-4838-84ef-937b8c515672" onclick="aptrinsic{'set','user',{'Job_Department':'IT/Technology'});" spellcheck="false" style="
padding-right: 16px;
padding-top: 16px;
padding-left: 16px;
padding-bottom: 16px;
border-radius: 16px;
background-color: rgba(4, 112, 247, 1);
color: #ffffff;
font-size: 14px;
font-family: Helvetica, Helvetica;
font-style: unset;
font-weight: unset;
text-decoration: none;
border-style: none;
border-width: 0px;
border-color: #0470F7;
cursor: pointer;
display: inline-block;">IT&nbsp;/&nbsp;Tech</button>