Tagging is a central part of Pendo Adopt. You must tag Pages and Features to get analytics.
Pages and Features are tagged in the Analytics page of the UI, which you can access from the left-side navigation. For specific instructions on tagging Pages and Features, see Tagging and viewing Pages and Tagging and viewing Features, respectively.
What "tagging" means
"Tagging Pages" is shorthand for defining the URLs that Pendo identifies as Pages in its analytics. “Tagging Features” is shorthand for selecting the UI elements in your application that Pendo identifies as Features in its analytics.
Tags are created based on rules. Page rules match the structure and content of the Website URL you want to track as Pages in Pendo. Feature rules are derived from the HTML behind the UI elements in your application, such as buttons or text fields.
You can think of tags as queries or criteria for searching all events sent to Pendo and returning only the events that are relevant to your Pages and Features. An event is a user interaction with your internally built or SaaS application.
The data for your Page or Feature includes only the events that fit its tagging rules. When you segment or filter based on Pages and Features that you created in Pendo, you’re searching every unidentified user interaction (event), and pulling in the information that you’ve defined as useful, grouped into Pages and Features in Pendo.
The Visual Design Studio
The Visual Design Studio is the interface that loads over your application so that you can navigate to the relevant parts of your application for tagging Pages and Features.
While in the Visual Design Studio, you can switch between Page tagging and Feature tagging using the tabs at the top of the designer.
Since Pendo has retroactive analytics, it’s not necessary to tag every Page and Feature immediately.
Prioritize which Pages and Features to tag first based on your guide targeting and usage analytics goals so that you can get started as soon as possible. For more information, see Deciding what to tag in this article.
Before you start tagging, you should also create a Page and Feature naming convention, for example, App-Page-Location-Button. Use descriptive names that would allow someone who didn’t tag the Page or Feature to know what it is. For more information, see Naming Best Practices.
Finally, while not necessary, we recommend tagging Pages before tagging Features, especially if Features exist in particular Pages.
Deciding what to tag
Tag Pages and Features based on what you want to learn more about or include in in-app messaging. This helps to narrow down what needs to be tagged.
|Tag the Pages and Features that coincide with the business processes you want to look at.||If seeing the number of clicks for a button isn't useful, then you don't need to tag it.|
|Tag Pages and Features that you're interested in seeing the workflow of.||Tag the buttons that can show you how many people start ("Create X") versus complete ("Save X") an activity in your application.|
|Tag Pages and Features that help you answer specific questions.||"Is this process being followed as expected?"|
|Tag Pages and Features that are relevant to your stakeholder audience.||If you support Sales Development Representatives, which Pages and Features are they most likely to spend time using?|
Auditing Pages and Features
- Check your Page rules before your Feature rules, since Features can be Page-specific.
- Look for duplicates.
- Look for outliers. Sort your list by number of clicks or views and review items with very low or very high numbers.
- Focus on parts of your application that are most important or that have recently gone through development changes.
Frequently Asked Questions
Does it matter if a Page or Feature is tagged first?
If your Feature lives on a particular Page, you should tag the Page first. If you are tagging a Page, you also have the option to tag the Feature. You can switch between tagging either option in the Visual Design Studio.
Do I need to tag a Feature to use it with a guide?
No. When you build a guide, you can select the UI element that you want to anchor the guide to. This feels similar to the Feature tagging experience.