Rolling out Pendo across a large organization is rarely straightforward. The platform is flexible, which is part of its appeal, but that flexibility comes with important decisions about architecture, governance, and identity. Without a clear plan, you end up with a fragmented implementation that is hard to manage and harder to extract value from.
We recently supported a multi-billion dollar enterprise with this challenge. As a Pendo customer with dozens of digital applications, they were managing tools for both external customers and internal field teams. Their goal was to unify these experiences without creating operational chaos or breaking the analytics foundation. Here is what it took to get that right.
Subscriptions should follow the journey
In Pendo, a subscription is the highest-level container. Applications live inside that subscription and represent distinct products or experiences.
The key decision is whether multiple applications should share a subscription or be separated. In this case, customer-facing apps and field tools needed to live together. These users frequently move between apps, and the business wanted to understand their full journey. A single subscription made clean tracking and unified messaging possible.
Internal systems with no connection to customer workflows were a different story. They had different goals, different users, and different owners. Separating them reduced noise, simplified admin tasks, and gave each team cleaner governance over their own data.
Applications are about scope, not just domains
A common misstep in Pendo implementations is defining applications by domain or subdomain. Applications should be defined by their function and by how the business wants to manage them.
This enterprise ran a large platform with many internal tools. Several of these tools shared a domain but served different purposes, supported different user journeys, and were owned by different teams. Defining each as its own application made it easier to track usage, assign ownership, and manage instrumentation in a focused way.
Think of an application in Pendo as a unit of analysis and engagement. If it serves a different audience or supports a different set of actions, it probably deserves its own app key.
User identity is not optional
When users move across apps, consistent identification is critical. Without it, cross-app analytics and behavioral targeting fall apart.
In this case, some applications used Salesforce IDs, others created local hashed identifiers, and still others pulled from different sources entirely. The fix was a policy requiring all apps to use one of two standard identity systems, one for internal users and one for customers and federated employees.
This change allowed the team to join data across subscriptions, send unified communications, and align Pendo data with broader business metrics. It also meant that data flowing into their warehouse could be trusted and mapped without complex transformations.
Governance matters more than you think
Even with the right architecture, things get messy without a plan for operational management. Large-scale Pendo deployments require clear roles, consistent naming conventions, and visibility across the stack.
For this client, centralized admin access and thoughtful subscription boundaries gave them the control they needed to grow without confusion. It also made it easier to move apps between environments during early-stage pilots, without losing data or creating reporting gaps.
Clean structure supports clean execution. It also saves teams from spending time untangling mistakes six months down the road.
Know the limits, especially on mobile
One challenge that surfaced in this work was the limitation of instrumenting certain mobile applications. Many enterprise mobile tools, particularly those built on closed or proprietary platforms, are difficult to work with. Some frameworks do not allow direct access to the code, which limits what can be tracked or enhanced with in-app messaging.
When this happens, raise the issue early. Pendo continues to expand support for modern mobile frameworks, and their product team actively incorporates feedback from enterprise customers. Surfacing these blockers early creates a better chance of finding a solution, whether through roadmap alignment or creative workarounds.
The most successful Pendo deployments are the ones where architecture follows the customer journey, applications are defined by purpose, identity is standardized, and operations are built for scale. Make the hard decisions early. Your future team will thank you.
If you need help sorting it out, we are here.