Capture backend requests
Is there any way to use Pendo to capture the backend requests performed by an action on the page? Up to some point this might be covered by event properties (e.g.: retrieving the contents of a form) but on the page I am working on there are several different buttons with the same css identifiers, which makes it impossible to identify each one of them without any doubt. Is there any way that I can use Pendo to track which kind of request was made? This would be only a temporary solution, as our goal is to add the identifiers to each button. However, that will take a long time until the start of the implementation and therefore we need a quicker solution.
0
Comments
Event properties yes but also the Pendo tagging aid can help uncover other bits that may be helpful for tagging. For example, I'd bet most buttons have name, value, or other attributes found in [ ]. You can also tag with :contains rules, such as button:contains("Your Button Text"), they're just case-sensitive and then if your button's text changes, you have to re-tag.
Liz Feller sometimes that does not happen and there are multiple buttons with the same text (in different areas) that we need to differentiate (e.g..: there are multiple "Submit" buttons, despite having the same CSS and different functionalities. We thought about capturing the backend requests, but is that even possible?
Are you hoping to tag these as features for analytics or to do something else?
Liz Feller analytics. We are hoping to see how people navigate the website and what is the journey of our users
gotcha! In that case, have you tried tagging each button/feature specific to the page they are on? That is how we differentiate a Save button in a gradebook vs on an attendance screen, for example, even if everything else about them is the same. Tagging them as features gets you the analytics to view user paths, observe their completion of funnels, journeys, and also helps you understand overall feature usage throughout your product, too.
Liz Feller we have explored that possibility as well, but the problem is that most of them appear on pop-ups, so technically, they are all on the same page, which invalidates this. Basically, there are a couple of actions that a user can take on a page and each one of them triggers a pop-up on that page, with the buttons that are equally coded on every pop-up
Isn't that fun :D my only trick I have left is to use the Pendo Tagging Aid to combine CSS selectors to make them modal-specific. We have done that before and it's worked well. It's a free Chrome extension!
Yeah, we are trying to have those buttons reworked, but it will take some time. I haven't explored Pendo Tagging Aid as much as I wanted to, so maybe Î will find something there then!
Please sign in to leave a comment.