Tagging best practices

Last updated:

This article reviews our recommended best practices for Page and Feature tagging.

Use Product Area colors to organize

Product Areas allow you to label and group similar areas of your product for filtering and color-coding in data visualizations throughout Pendo. This helps you quickly look at behavior analytics and guidance for the parts of the product you're responsible for.

Think about your product and how it's organized. Create Product Areas corresponding to the identified sections within your app and assign designated colors for improved visualizations and quick navigation within Pendo.

ProductAreaExample.png

Use consistent formatting for event names

A shared naming convention promotes consistency, clarity, and efficient collaboration within the Pendo platform. Administrators play a pivotal role in establishing a naming convention for Pages and Features, ensuring its strict adherence by anyone with tagging permissions.

For the naming convention to be useful, it must not only be adopted by other Pendo users in your company creating tags but also adhere to a level of descriptiveness so that someone who didn’t tag the Page or Feature would know what it refers to.

When naming Pages, provide a clear indication of their location within the application. Here are some naming convention examples for Pages based on the Pendo app:

[Module] | [Page Name]
Behavior | New funnel

Guides | Ordering

Replay | Replay Player

Discover | Validate Ideas

For Features, ensure other Pendo users understand their location and function without needing to review the selection rules. Here are some naming convention examples for Features based on the Pendo app:

[Page] | [Action]
Funnels list | Create funnel

Guides Ordering | Guide Throttling

Replay Player | Playback speed

Validate | Create idea

No matter what naming convention you choose, be concise, prioritize descriptiveness, and consider employing abbreviations for efficiency.

Additional tips

  • Start small, such as 20 to 30 Pages and 5 to 10 key Features.
  • Consider clearly differentiating exploratory tagging from key value drivers.
  • For Feature tagging, start with key value drivers related to team goals.
  • Perform exploratory tagging on an ad-hoc basis.
  • Clean up unused Pages and Features every few months.
Was this article helpful?
6 out of 9 found this helpful