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

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.

Hello All,

Thanks @link_black  for this impressive community post.

Here is a short video on implementing the above 

Code:

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

https://www.loom.com/share/036972a9894f4ae591da69a38db86024

Click here to access the video

Thanks

Dileep Nalla

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>
        <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">
                <br>
            </p>
            <p>Check this box for Testattribute2</p>
            <input type="checkbox" id="myInput" oninput="aptrinsic('set','user',{'attributeTest2':'JPsAttribute2'});" value="x">
            <p id="demo">
                <br>
            </p>
</div>

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!!!!! :)

@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.

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

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. 

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

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.

Thanks

Dileep Nalla

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

I tried this - 

aptrinsic('set','account',{'payrollvendor':'TestValue'});

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

aptrinsic('set','user',{'role':'Director'});

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

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

https://support.gainsight.com/PX/Release_Notes/Current_Release_Notes_-_2023/PX_Release_Notes_February_2023_Interim_Release_Version_3.13.0#New_Action_Type_in_Custom_Buttons