Liz Feller
コメント
-
Update your Feature Element Matching to use the Custom CSS option and update it to read:[href*="/Accounting/Index"] For feature tagging, the wildcard * needs to go before the = and the attribute yo...
-
Similar to what was posted in Slack, guide preview only works for the single guide you are editing. But segmenting the guides to yourself and/or putting them in Staged helps you test the entire wor...
-
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,...
-
Are you hoping to tag these as features for analytics or to do something else?
-
This can happen if your product's style sheet is somehow influencing all radio buttons regardless of if they're in the product or in Pendo. We fix this with a custom code block to specify the Pendo...
-
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 should be able to manually type in a font if it's not included in the list. I hope that fixes it across the different text types for you!
-
I'd recommend using the Pendo Tagging Aid Chrome extension to find out if it's possible. You may have to adjust your Pendo tagging settings for your subscription to use extra things like name, labe...
-
I think you can since title and subtitle and paragraphs each can have their font set within the theme, plus you can also get into the global CSS to make double sure!
-
I believe it'd be a separate guide, but you could basically style it as an alert badge and have it dismiss on clicking the RC to open it up or something, not sure! I'd be curious what you end up tr...