Thanks for posting to PX Community @DannyPancratz.
I would recommend a PX Webhook first, then using the PX REST API second. Both of these require a technical person and/or developer to help with the actual PX User update using the PX REST API for that as well.
Another way, that requires an application developer too, would be to call the PX Identify javascript inside your application when the “Feature” is tracked with the IdentifyId and the current datetime value as a PX User attribute mapping. Your application developer would need to know when the “Feature” is being used, which is probably easier to do when the Feature is based on a URL match, but would become more difficult when the Feature is based on a click event and CSS selector.
Can you explain the use case? Since this data is available in PX Analytics I am trying to understand why you would want it on the PX User level as an attribute value.
Thanks, @link_black. Here’s the use case: User Attribute for Last Save to be used in both PX reporting and other reporting (via push to Salesforce Contacts).
- We have a Save action mapped as a feature.
- We differentiate Active Users (those who login) vs Active Creators (those who save) on our development platform
- We’d like to use Last Save for segmentation and analytics
As I type this, I realize I can probably do the PX version via Query Builder, identifying the audience as Users with that Feature Match event.
But for my use case to push the Last Save date to Salesforce, Tableau, and other systems… It seems like I’d need to do a bunch of API calls to (and consume a lot of my Zapier tasks) to apply this for every save or check every active user within a day.
Based on your response, I’m thinking there might be a way via Zapier to subscribe to the webhook and then hold the actions in a queue that somehow only runs the API updates once per user per day. If there’s an option I’m looking for, it’s probably that.