Liz Feller
コメント
-
I think all those fields are passing data strictly related to guide loads and views, not page data or element/feature data. the uiElement columns are probably referring to how the guide step is tar...
-
if you open the Chrome extension Pendo Tagging Aid it will give you the CSS or other selectors you need :) https://chromewebstore.google.com/detail/pendo-tagging-aid/jhbhgbhjadlmnigleahdiainjdhomdgn
-
You should be able to give them Guide Publisher access as a regular user, not an admin, per this article https://support.pendo.io/hc/en-us/articles/360058639932-Roles-and-permissions
-
It is possible using iframes in a custom code block on your guide step, but you have to make sure your product's Content Security Policy (CSP) allows iframes displaying other pages like that.
-
What an interesting idea, I like it! We do not have specific guidelines for circumstances, but we do communicate internally that guides should be used if existing product functionality won't solve ...
-
Try this in the Pendo github, it sounds like what you're after! https://github.com/pendo-io/snippets/tree/master/guides/advancingGuides/advanceGuideOnElementAppear
-
Did you try looking through the Engage API options here? https://engageapi.pendo.io/#dd943e68-5bff-4a1a-9891-b55638ae2c3d
-
There's actually a new button action coming out/out already called Automation that should help with this! If it's been released to GA, it's at the very bottom of the list of button actions available.
-
We've run into this as well and I believe decided to switch those badges to be clickable only, not display on hover, to increase their accessibility.
-
This would be setting up your RC to be target activated instead of badge activated, and then you proceed just like setting up a normal guide :) it will automatically open if you only have one modul...