Skip to content

Pendo Integration Guidelines

Our design system components are not only the building blocks of our product’s UI, but also the foundation of our analytics. Pendo.io is the primary platform we use to capture user interaction data, helping us measure adoption, validate design decisions, and identify opportunities for improvement.

By embedding Pendo tracking at the component level, we ensure every product experience generates consistent, high-quality metrics without requiring ad hoc instrumentation. This allows us to make data-informed decisions that directly support product growth and user satisfaction.

Important

If a user action is important enough to design and build, it’s important enough to measure. Building Pendo-ready components into our design system ensures every feature contributes to actionable insights.

H2 Consistent Naming Conventions

Use clear, human-readable event and element names. Format: ComponentName-ActionContext

  • Do

    Do: Button-SubmitCheckout

  • Don't

    Don’t: Btn1

Tagging at the Component Level

  • Instrument reusable components in the design system so tracking is inherited automatically.
  • Avoid tagging the same action multiple times in different contexts unless intentional.

Tagging with the Visual Design Studio

https://support.pendo.io/hc/en-us/articles/360032293971-Tagging-with-the-Visual-Design-Studio

Tagging best practices

https://support.pendo.io/hc/en-us/articles/360031863592-Tagging-best-practices