Pendo

What Is Pendo?

Pendo is a product-analytics and in-app guidance platform that helps software teams understand how people use their applications and then act on that understanding directly inside the product. It combines two capabilities that are usually sold separately: analytics that capture how users move through an application, which features they touch, and where they get stuck, and an in-app layer that delivers guides, tooltips, walkthroughs, surveys, and announcements to users without requiring engineering to ship new code for each message. The result is a closed loop, measure behavior, then guide behavior, aimed at improving adoption and retention.

The core idea is that product teams should not have to choose between knowing what users do and being able to influence it. Pendo's analytics show, for example, that a valuable feature is rarely discovered, and its guidance tools let the team launch a tooltip or walkthrough pointing users to that feature, all from Pendo's dashboard rather than a code release. Because both halves run on the same data about who the user is and what they have done, guidance can be precisely targeted to the right segment at the right moment.

Pendo is a hosted SaaS platform, not a browser extension and not self-hosted software. Teams install a small JavaScript snippet (or a mobile SDK) in their application, and the data flows to Pendo's servers where it powers analytics and drives the in-app layer. Because that snippet runs in the user's browser and renders guides on the page, Pendo's presence is detectable from the outside, which is why a site or web app using Pendo often reveals it through its agent script and data-collection requests.

It helps to place Pendo in context. Pendo is aimed primarily at product, customer-success, and product-marketing teams working on software applications, especially SaaS products, rather than at marketers measuring a brochure website's traffic. Its emphasis on feature usage, adoption, and in-app messaging reflects that audience: the questions it answers are about how users engage with an application's functionality and how to nudge them toward value.

How Pendo Works

Pendo works by installing an agent in your application that both captures usage and renders in-app experiences. On the web, you add a JavaScript snippet that loads the Pendo agent; on mobile, you integrate an SDK. Once installed, the agent observes how users interact with the application, which pages and views they visit, which elements they click, and how they progress through flows, and sends this data to Pendo's servers.

A distinctive aspect of Pendo's analytics is its tagging model. Rather than requiring engineers to instrument every event in code up front, Pendo captures interaction data broadly and lets product teams define "features" and "pages" retroactively through a visual tagging interface. A product manager can point at a button or a screen and tag it as a feature, and Pendo will report on it, often including historical data, because the underlying interactions were already being collected. This codeless tagging is a major reason non-engineers can drive analytics in Pendo.

To make analysis meaningful, Pendo associates activity with identified users and accounts through a step called identification, in which the application passes Pendo a visitor identifier and an account identifier along with relevant metadata such as role, plan, or company size. This lets teams segment behavior by user attributes and, crucially, roll usage up to the account level, an essential capability for B2B SaaS where decisions are made about customer accounts rather than individual logins.

The in-app guidance layer uses the same data. From Pendo's dashboard, a team designs guides, tooltips, banners, walkthroughs, onboarding flows, and surveys, and targets them to segments defined by behavior or attributes. When a matching user loads the application, the agent renders the guide in context. Because no code release is required, product-marketing and customer-success teams can launch and iterate on in-app messaging independently. Pendo also includes survey tools, including the ability to gather product feedback and sentiment directly in the app.

A useful way to picture the workflow is to follow a single initiative. A product team notices, through Pendo analytics, that a powerful reporting feature has low adoption. They confirm with a funnel that users abandon before reaching it. Without shipping any code, they build a short in-app walkthrough that highlights the feature and target it to users on the relevant plan who have not used it. They launch an in-app survey asking non-adopters what would make the feature useful. Over the following weeks they watch adoption climb in their Pendo dashboard and iterate on the guide. This measure, guide, and re-measure loop, run largely by non-engineers, is the essence of how teams use Pendo.

Because the agent collects broadly and renders experiences in context, Pendo provides controls around what is captured and how guides are targeted, and responsible implementations configure these with privacy and consent in mind, particularly when passing user metadata for segmentation.

How to Tell if a Website Uses Pendo

Pendo leaves recognizable fingerprints in the browser. Because StackOptic analyzes a URL from the server side, it inspects the same kinds of signals you can verify manually with browser tools, View Source, or a detection extension. Where a signal is not guaranteed, treat it as suggestive and corroborate with others.

The Pendo agent script and its domains. The strongest signal is the Pendo agent loaded from Pendo's content-delivery domains, conventionally hosts under pendo.io (for example agent and data hosts such as cdn.pendo.io for the script and a data-collection subdomain for beacons). A request to a pendo.io host in the Network tab is a clear indicator.

The global pendo object. Pendo conventionally exposes a global JavaScript object named pendo on the page (used to initialize the agent and call pendo.initialize(...)). Finding pendo defined in the source or evaluating it in the DevTools console is a recognizable tell.

Network beacons to Pendo. As the agent captures usage, it sends data to Pendo's ingestion endpoints. Watching the Network tab while interacting with the application can reveal these outbound requests.

Guide and agent assets. When in-app guides are active, the agent loads guide content and associated assets from Pendo's domains, and injected guide markup may appear in the DOM, another sign of Pendo at work.

Here is how to check each signal yourself:

Method	What to do	What Pendo reveals
View Source	Open the page, right-click, "View Page Source"	Inline snippet referencing pendo and a script from a pendo.io host
Browser DevTools (Console)	Type pendo and press enter	A defined object confirms the agent loaded
Browser DevTools (Network)	Filter requests while interacting	Agent script and beacons to pendo.io hosts
Browser DevTools (Elements)	Inspect the DOM when a guide shows	Injected Pendo guide markup and containers
Wappalyzer	Run the extension on the live page	Flags "Pendo" when its signals are detected
BuiltWith	Look up the domain	Current and historical Pendo detection

A quick console check is to evaluate typeof pendo. If it returns "object" rather than "undefined", the page is running the Pendo agent. For a broader walkthrough of identifying measurement and product tools, see our guide on how to find out what analytics a website uses, and for the general methodology, how to find out what technology a website uses.

It is worth noting how these signals behave in practice. Pendo is most often deployed inside authenticated SaaS applications rather than on public marketing pages, so the agent may only load after a user logs in, which means a quick look at a homepage might not reveal it even when the product behind the login is heavily instrumented. Many teams also load Pendo through a tag manager, so the script reference can appear indirectly. Some implementations proxy collection requests through their own domain, which can mask the pendo.io hostname while leaving the global pendo object intact. Because no single tell is guaranteed, the reliable approach is to combine signals: a pendo global, a request to a Pendo domain, and injected guide markup together make for a confident verdict. Server-side analysis helps by fetching the raw HTML and spotting the inline snippet directly, though for login-gated apps the strongest evidence appears once authenticated. If you want to compare Pendo against another product-analytics tool, contrast its fingerprints with those of Mixpanel.

Key Features

• Product analytics. Capture how users move through an application, which features they use, and where they drop off, with funnels, paths, and retention views.
• Codeless tagging. Define features and pages retroactively through a visual interface, often with historical data, without instrumenting events in code up front.
• Account-level rollups. Identify users and accounts so behavior can be segmented and aggregated by company, plan, or role, essential for B2B SaaS.
• In-app guides. Build and target tooltips, walkthroughs, banners, and onboarding flows from a dashboard without shipping code.
• Surveys and feedback (NPS). Collect in-app sentiment and product feedback tied to user behavior.
• Segmentation. Target both analysis and guidance to precise segments defined by behavior or attributes.
• Web and mobile. Instrument and guide users across web applications and native mobile apps.

Pros and Cons

Pros

• Unifies analytics and in-app guidance so teams can measure behavior and act on it without separate tools.
• Codeless tagging lets product managers and non-engineers drive analysis and messaging.
• Account-level reporting fits B2B SaaS, where customers are accounts rather than individuals.
• Reduces reliance on engineering for onboarding flows and in-app communication.

Cons

• Oriented toward in-application product teams rather than website traffic measurement.
• Broad data capture and user identification require careful privacy and consent handling.
• Can be a significant investment relative to lightweight or free analytics tools.
• Most value appears inside authenticated apps, so it is less relevant for simple public sites.

Pendo vs Alternatives

Pendo competes with product-analytics tools and with digital-adoption platforms. The table clarifies its niche.

Tool	Core focus	Guidance layer	Best for
Pendo	Product analytics + in-app guidance	Built in	Product and CS teams driving adoption
Amplitude	Product analytics	Limited (analytics-led)	Deep behavioral analysis and experimentation
Mixpanel	Product analytics	Limited	Event-based funnels and engagement
Walkme	Digital adoption platform	Strong	Enterprise guidance across many apps
Heap	Autocapture product analytics	Limited	Codeless event capture and analysis

If a site is not using Pendo, the same family of signals points to the real tool; compare it with Mixpanel or a behavioral platform like Amplitude to see which globals and endpoints appear. Some organizations run a dedicated analytics tool alongside a separate guidance platform, so detecting Pendo does not always rule out a second product in the stack.

Use Cases

Pendo is most at home with SaaS product, customer-success, and product-marketing teams that need both to understand in-product behavior and to act on it. Product teams use its analytics to see which features drive value and which are ignored, then use in-app guides to improve discovery and onboarding without waiting on an engineering release. Customer-success teams use account-level reporting to spot accounts whose usage is slipping, an early warning for churn, and deploy targeted guidance or outreach.

It also serves product-marketing teams announcing new features in-app, onboarding teams building first-run experiences that shorten time to value, and research-minded teams gathering in-app feedback and sentiment to prioritize the roadmap. For competitive and market research, detecting Pendo on a web application signals a mature, product-led organization that invests in adoption and user experience, typically a B2B SaaS company rather than a content site.

Consider a few concrete scenarios. A B2B SaaS company might use Pendo to find that a key integration feature is adopted by only a fraction of accounts, then launch a targeted walkthrough to the rest and watch adoption rise. A customer-success team might build a dashboard of accounts whose weekly active usage has dropped and trigger an in-app message plus a human check-in before renewal risk grows. A product-marketing team might roll out an in-app announcement for a new capability and measure, in the same tool, how many users engaged with it. In each case Pendo links insight to action inside the product.

From a sales-intelligence perspective, knowing that a prospect runs Pendo tells you they are a product-led, adoption-focused software organization, which is valuable context for vendors selling product, analytics, customer-success, or developer tools. Because Pendo often loads only behind a login, detecting it can require analyzing the authenticated application, but when its signals are present they are a strong qualifier. Surfacing that signal across many domains automatically, rather than inspecting each app by hand, is exactly what technology detection is built to do, and it ties directly into using tech-stack data to qualify leads.

Frequently Asked Questions

What is Pendo used for?

Pendo is used by software teams to understand and improve how people use their applications. Its analytics reveal which features users adopt, how they navigate, and where they get stuck, while its in-app guidance layer delivers tooltips, walkthroughs, onboarding flows, and surveys to nudge users toward value, without an engineering release for each message. It is especially popular with B2B SaaS product, customer-success, and product-marketing teams because it can roll usage up to the account level and target guidance precisely.

How can I tell if a web app uses Pendo?

Open DevTools and check whether pendo is defined in the console, view the page source for an inline Pendo snippet, and watch the Network tab for the agent script and beacons to pendo.io hosts. When a guide is active, you may see injected Pendo markup in the DOM. Note that Pendo often loads only after login, so a public homepage may not reveal it. Tools like Wappalyzer and BuiltWith will flag Pendo when its signals are present.

What is the difference between Pendo and a tool like Mixpanel or Amplitude?

All three are product-analytics tools, but Pendo's distinguishing feature is its built-in in-app guidance layer: it can both measure behavior and deliver tooltips, walkthroughs, and surveys to influence it, largely without code. Mixpanel and Amplitude focus more purely on deep behavioral analysis, funnels, retention, and experimentation, and rely on other tools for in-app messaging. Pendo's codeless tagging and account-level rollups also make it especially approachable for non-engineers on B2B SaaS teams.

Does Pendo require engineering to set up?

Initial installation requires adding the Pendo snippet or SDK and passing user and account identifiers, which is an engineering task, but a one-time one. After that, much of the day-to-day work, tagging features and pages, building funnels, and creating and targeting in-app guides, is done by product, marketing, and success teams through Pendo's visual interface without further code releases. This separation of a small technical setup from extensive no-code operation is central to Pendo's appeal.

Is Pendo only for product teams, or can it track a marketing website?

Pendo is built for in-application product experiences rather than marketing-website traffic measurement, and it shines inside authenticated SaaS apps where it can tie behavior to accounts and deliver in-app guidance. While it can technically run on public pages, most teams use a general web analytics tool for their marketing site and reserve Pendo for the product itself. That focus is why detecting Pendo usually points to a software application and a product-led organization rather than a brochure site.

Want to detect Pendo and the rest of a site's technology stack instantly? Run any URL through StackOptic at https://stackoptic.com.