Pendo in Development and Testing

Last Updated:


We encourage including the Pendo agent in all instances of your web application except environments used for automated testing. Including Pendo ensures developers and manual testers are working in an environment as close to production as possible.

Automated Testing

The Pendo agent will function properly in automated testing, but doesn't provide any value. Including the Pendo agent in pages loaded during automated tests may slow down completion time in addition to generating a large quantity of usage data not associated with actual users. We encourage including the Pendo agent only for deliberate automated testing of Pendo guides or for performance profiling.

Single API Key

Each API key (or "subscription") uses separate data stores. There are no mechanisms to automatically move data or settings between subscriptions. Pendo provides draft, staging, and public workflow concepts for in-app messaging components to meet testing and development needs. Pages and Features allow multiple rules which can support upcoming changes to the web application.

Always Use Unique Visitor and Account IDs

Visitor and Account IDs must be unique per API key due to the way Pendo processes metadata values at this time. Excluding is insufficient to address ID collisions.

If there are ID collisions between testing and production environments, consider adding a prefix or suffix to indicate each non-production environment.

Pendo tracks guide interaction behavior at the visitor ID level. Non-production environments should also contain unique IDs to ensure visitors receive a consistent Guide experience.

Pages and Features

Including the Pendo agent in pre-production code lets you ensure new or updated pages and features can be tagged successfully before pushing your code to production.