Skip to main content

Did you know that you can add dynamic URLs/Button links to your PX Engagements? 

 

Just like how you can use tokens to include PX User/Account attribute values to personalize your in-app messaging (e.g. “Hi Link from Pittsburgh, please take my important survey!”), you can also use those PX User/Account attribute values to craft a personalized URL or Button link for the user to visit.

 

There are many use cases for this, but in this simple example I will pass the PX User’s email address at the end of a hard-coded hyperlink as shown below…

 

And, here is how it looks for a user in-app…

 

And clicking the Button leads the user to this page…

 

Imagine if you will that URL leading the user to a custom dashboard you built just for them, or some custom application that auto-logins as them, or some marketing site where you not only want to have personalized content, but also track which users visited, etc. etc. etc.. 

The possibilities for using this technique in your PX Engagements may not be infinite, but are surely many.

 

Happy PX-ing!!!!

 

 

@link_black , I kind of see where you are going with this, but I feel like the use case doesn’t make a whole lot of sense to me. Could you share an example wehre the use case is more realistic. I am not sure why http://www.test.com/somename@email.com would be useful. 

 

Would it be possible to share an example where a user can be pushed to a unique dashboard? May a PX dashboard with data about their own account?

 

 

Thanks for reading and commenting on my tip @JPKelliher. 

 

I did include a few potential use cases to think about above and I am not sure pushing your web application users to a PX custom dashboard you created for them is a normal use case. ;)

However, if that was the goal then one could store the PX custom dashboard ID (“50494603-940e-4ebe-9aa6-df5963dc20c2”) as a user/account String attribute and then dynamically create a link such as the following to display within an Engagement

https://app.aptrinsic.com/dashboard/50494603-940e-4ebe-9aa6-df5963dc20c2

 

I hope this helps!

 

 

 

  

Reply


Terms & ConditionsCookie settings