Query - Pendo Auto launch based on multiple visitor metadata for the same page
Hi Team,
We are building a use case where we are aiming to launch Pendo guide automatically for specific visitors, in our product ‘iluminr’ when visiting a certain page which has unique ID.
I understand there is a concept of permalink which we are looking into, but this specific use case goes beyond permalink as it is visitor specific and the metadata the visitor has in Pendo.
Use case is,
We have 2 roles in our platform, one is Facilitator, and another is Participant role. We want to auto-launch Pendo guides for Facilitators but not for Participants, when they visit an event-page (iluminr terminology) which has unique database eventide in the URL.
And we are currently validating this case by pushing these roles to visitor metadata.
Challenge and the question here is, same Facilitator can be a Participant in another event and Pendo guide is to be auto launched or not, is decided based on this role.
I am looking into Pendo Agent functions https://agent.pendo.io/public/Guides to see if we can achieve the above leveraging this, but not able to come to a solution from this.
Appreciate if you could offer your expertise/inputs to unblock us on this and let us know how we can achieve the above use case.
Thanks.
Comments
Hello Praneeth Gedela,
I've encountered a similar setup in our applications portfolio, where a user can hold different roles across various applications. For instance, an individual may serve as an admin in one application and a regular user in another.
We maintain all roles associated with users across different applications. To address your specific requirement of displaying a guide exclusively for Facilitators, you can implement a solution by adding a common role meta across your app. This meta will dynamically update based on the role a user logs in with, effectively resolving the issue.
On our end, we have implemented a similar approach where guides are shown only to users who are admins in one app but sales users in another. Users can seamlessly switch between apps without the need to log out. To dynamically control guide behavior, we use an additional dummy role identifier meta, labeled as 'current_role,' on top of the regular 'app_x_role_id' meta per app. This 'current_role' is utilized in the guide segment to control the launch.
While permalinks can offer a temporary solution, adding a dummy role identifier proves to be a more robust and long-term fix for various situations.
Feel free to connect on LinkedIn if you need any further assistance.
Cheers, Rohit Pandey
Hey Rohit Pandey
Thats a clever approach and sounds like a potential solution.
One follow up question to this approach,
We have only 1 app in Pendo, and what I mentioned as Facilitator/Participant roles, they are not really a role on app-level, but lets consider this as 'event-persona'.
And when a user logins and goes into our event listing page, it will have multiple events, and thats where this 'event-persona' applies i.e. for some event it could be Facilitator and others it could be Participant.
With your apporach, does it mean that on loading of each event-page, iluminr sets this custom-metadata-role, and based on it, relevant guide is launched ?
If so, will there be any latency in loading the guides, as we are litertally setting custom-metadata on page load, for guide to be launched at the same time ?
Thanks for your prompt response.
Cheers,
Praneeth G.
Praneeth Gedela latency should not be a big issue, it would be under 1 2 seconds even if the we are setting the custom metadata on page load.
Noted Rohit Pandey
will give it a try and validate it
Thanks much for your guidance & inputs, much appreicated
will keep posted here of the updates
Please sign in to leave a comment.