How to Tell If a Website Uses Pendo

Pendo is a leading platform that combines product analytics with in-app guidance — tooltips, walkthroughs, onboarding guides and surveys layered over a software product. Because it loads a distinctive agent and exposes a clear global, detecting it is straightforward: look for the cdn.pendo.io agent and type pendo into the console. This guide covers every reliable signal, the platform's dual role, the look-alikes to rule out, and what Pendo usage tells you about the company.

What is Pendo?

Pendo is a product-experience platform for software applications. It does two related jobs: product analytics (tracking feature usage, user paths, retention and adoption without manual event tagging, via its auto-capture agent) and in-app guidance (tooltips, walkthroughs, onboarding flows, announcements and in-app surveys like NPS). The combination lets product teams both measure how users behave and act on it by guiding users inside the app. Pendo is squarely aimed at SaaS and product-led companies, and because it operates inside the application, it is most often found behind a login rather than on a marketing site.

For detection, the key context is that Pendo signals a product-led, data-driven SaaS company that invests in understanding and guiding in-app behaviour — onboarding, feature adoption and retention. Finding it tells you the product team measures usage and runs in-app engagement programmes. Because Pendo loads its agent from cdn.pendo.io with an account API key and exposes a window.pendo object, it is easy to confirm — though you may need to be inside the app (logged in) to see it, since it lives in the product experience.

How Pendo loads and runs

A Pendo install loads its agent from cdn.pendo.io/agent/static/<api-key>/pendo.js, where the api-key identifies the Pendo subscription. The agent is initialised with pendo.initialize({ visitor: {...}, account: {...} }), passing visitor and account metadata for analytics and guide targeting. It exposes the global window.pendo object with methods including initialize, identify, track, and guide-related APIs. The agent auto-captures in-app interactions (clicks, page/feature views) and renders any active guides over the UI.

Captured data and guide configuration are exchanged with data.pendo.io (and the platform at app.pendo.io). So a Pendo-enabled app shows the cdn.pendo.io agent (with the API key), the window.pendo global, in-app guides/tooltips, and data.pendo.io traffic. Because Pendo targets the in-app experience, these signals are most visible once you are inside the product. Knowing them — the cdn.pendo.io agent, the pendo global, the pendo.initialize call, and data.pendo.io traffic — makes detection reliable.

How to tell if a website uses Pendo

Confirm at least one strong signal (the agent or global suffices).

1. Use the console. Type pendo and press Enter. A returned object with initialize/identify/track confirms Pendo.

2. Check the Network tab. Filter for pendo. The agent from cdn.pendo.io/agent/static/<api-key>/pendo.js and traffic to data.pendo.io confirm Pendo.

3. View the source. Search for pendo. The agent snippet and the pendo.initialize(...) call are usually visible.

4. Read the API key. The api-key in the cdn.pendo.io agent URL identifies the Pendo subscription.

5. Look for guides. In-app tooltips, walkthroughs, onboarding guides or NPS surveys rendered over the UI corroborate Pendo (you may need to be logged in).

What the Pendo signals look like

(function(apiKey){ … o.src='https://cdn.pendo.io/agent/static/'+apiKey+'/pendo.js'; … })('abcdef0123456789');
window.pendo.initialize({ visitor: { id: 'user-123' }, account: { id: 'acct-456' } });
window.pendo = { initialize: ƒ, identify: ƒ, track: ƒ, … }
POST https://data.pendo.io/data/...   (analytics + guide data)

The cdn.pendo.io agent, the window.pendo global, and data.pendo.io traffic are conclusive.

Pendo versus other tools — avoiding false positives

Match the host and global to keep product-experience tools distinct. Pendo uses cdn.pendo.io/data.pendo.io and the pendo global; Appcues (in-app onboarding) uses fast.appcues.com and an Appcues/AppcuesSettings global; WalkMe uses cdn.walkme.com; product-analytics tools like Amplitude, Mixpanel and Heap measure but do not provide in-app guides. Pendo's distinctive combination of analytics and guidance, plus the cdn.pendo.io host, identifies it. The main subtlety is that Pendo lives inside the app, so a marketing-site scan may not reveal it — check the logged-in product if you have access. Do not confuse Pendo's auto-capture analytics with a pure analytics tool; the in-app guides are the tell.

How reliable is each Pendo signal?

The cdn.pendo.io agent and the window.pendo global are definitive, and the API key identifies the account. Traffic to data.pendo.io corroborates. In-app guides confirm the guidance side. The weakest situation is that Pendo is often only present inside the authenticated app, so a public-page scan may miss it — log in to confirm. As a rule, the cdn.pendo.io agent or the pendo global settles it, and the API key identifies the subscription.

What Pendo usage reveals about a company

Finding Pendo signals a product-led, data-driven SaaS company that invests in both measuring and guiding in-app behaviour. Its dual analytics-and-guidance role tells you the product team runs onboarding, feature-adoption and retention programmes inside the app, not just passive measurement — a sign of product maturity. The presence of in-app guides and NPS surveys indicates active engagement and feedback efforts. If you sell product, data, customer-success or onboarding tooling, a Pendo customer is an ideal-fit, product-mature account with budget (Pendo is an enterprise-grade platform). The account metadata passed to pendo.initialize (visitor/account fields) even hints at how the company models its users and accounts. Because Pendo lives inside the product, finding it confirms you are looking at a genuine software application with a serious product function.

What finding Pendo means for sales, agencies and competitive research

For sales and prospecting, Pendo marks a product-led SaaS company with a mature product practice and budget — a fit for product, data, customer-success and onboarding tools. It signals a real application, not a marketing site.

For agencies and consultants, finding Pendo tells you the client invests in product analytics and in-app guidance, so engagements can focus on onboarding optimisation, adoption analysis, or guide strategy. It signals a sophisticated product team.

For competitive and market research, Pendo (versus pure analytics tools or no in-app guidance) reveals how seriously a competitor invests in product experience and onboarding, useful when benchmarking product-led maturity.

Pendo in the wider product stack

Pendo sits at the centre of a product-experience stack inside a SaaS app. It accompanies the app's framework, authentication, a CRM or customer-success platform (Pendo data often feeds CS tools), and sometimes a separate marketing-analytics setup on the public site. Because Pendo auto-captures, it may reduce the need for a separate product-analytics tool, though some companies run both. For an auditor, the valuable details are the API key, the visitor/account metadata model, whether in-app guides and surveys are active, and the surrounding product and customer-success stack; together these reveal a product-led company and the depth of its product-experience investment. One practical consequence is worth stressing: because Pendo lives behind the login, it is invisible to anyone profiling only the public marketing site, which means a great many Pendo-using companies are missed by superficial tech-stack scans. A real-browser audit that reaches the authenticated product experience — or that recognises the agent when it does load — captures a segment of serious, product-led SaaS companies that header-only or homepage-only tooling never sees. For anyone selling into product and customer-success teams, that hidden segment is precisely where the highest-value, best-qualified accounts tend to sit.

A quick Pendo confirmation walkthrough

Open the application (logging in if needed) with developer tools on the Console panel and type pendo — a returned object with initialize/track confirms it. Switch to the Network tab, filter for pendo, and confirm the agent from cdn.pendo.io/agent/static/<api-key>/pendo.js and traffic to data.pendo.io. View the source for the pendo.initialize(...) call and read the API key. Watch for in-app tooltips, walkthroughs or NPS surveys. The cdn.pendo.io agent or the pendo global confirms Pendo.

A quick Pendo detection checklist

• Type pendo in the console; a returned object is conclusive.
• Filter the Network tab for pendo; the cdn.pendo.io agent and data.pendo.io traffic confirm it.
• Read the API key from the cdn.pendo.io/agent/static/<api-key>/pendo.js URL.
• Look for in-app guides, tooltips and NPS surveys (the guidance side).
• Check the logged-in app, since Pendo lives inside the product.
• Distinguish Pendo (cdn.pendo.io, analytics + guides) from Appcues, WalkMe and pure analytics tools.

Detecting Pendo at scale

Checking one app is quick, but mapping product-experience-tool adoption across many SaaS domains — to find product-led companies — calls for automation. StackOptic detects Pendo and thousands of other technologies from a real browser, reading the agent, global and traffic. For related reading, see our guide to finding out what analytics a website uses and the full Pendo technology profile.