Skip to content

Pendo

Pendo combines in-app guides with product analytics so you can decide where to offer help and see how people used it.

Visit Pendo

Who should see the first guide?

Choose one task and one audience, such as first-time people who have not saved a project. Pendo can use a segment, a group of visitors defined by conditions, to decide who sees the guide.

Your app identifies visitors and can supply metadata, such as an account role. Choose stable identifiers and only the fields the guide needs. Review analytics collection separately before putting it on a real app.

What does Pendo Free count, and what needs a keyboard test?

Pendo Free documents a 500 monthly active user limit. It counts unique Visitor IDs in a 30-day period, and requires a business email to register. Check how your plan counts anonymous or identified visitors.

For a multi-step web guide, configure accessibility settings for each step where needed. Test how someone reaches the guide, advances and closes it using a keyboard. Verify the exact guides and app states your visitors will see.

What can you take with you?

Pendo documents guide PDFs and translation content exports, plus separate methods for reporting and data export. Keep your original guide copy, audience rules and task definitions. Check what your plan and role can export.

A PDF records steps for reference. Plan separately to reproduce when the guide opens and how each step points into your app.

How can you check two visitors on paper?

Draw a fictional new visitor and a returning visitor who already saved a project. Use no Pendo account, analytics script, guide publish or real visitor data.

  1. Mark who sees the guide
    Offer the first visitor help. Keep the returning visitor on the normal path.
  2. Show how both can proceed
    Draw the guide close action and where focus should return.