A-B
| Term | Abbreviation | Description |
|---|---|---|
| Account | – | A Pendo-specific hierarchy of data that represents a group of visitors. For more information, see Accounts. |
| Account report | – | A type of report that provides insights into how visitors from a specific account interact with your application. You can view the account information that's most important to you by customizing the time range, segments, and table data. You can also save your custom reports and export them to CSV. |
| Agent | – | The pendo.js file that provides event collection, in-app guidance, and a Feedback module, depending on your Pendo subscription. For more information on these components, see the Developer's guide to implementing Pendo using the install script. |
| Application | App | A distinct web or mobile application hosted on a single platform (for example, web, iOS, or Android). Applications can be grouped under a single subscription. For more information, see Multi-app subscriptions. |
| Badge | – | An icon that you place next to an element in your application during guide creation. Badges are primarily used for opening supplemental explanations for functionality that would otherwise clutter the UI if permanently displayed. For more information, see Guide activation options: Visual Design Studio. |
C-D
| Term | Abbreviation | Description |
|---|---|---|
| Click event | – | When a visitor clicks on an element in your application. Click events are used to track how visitors navigate through your application. |
| Canonical Name | CNAME | The domain name that maps your subdomain to a location. For more information, see CNAME for Pendo. |
| Content delivery network | CDN | A system of distributed servers (network) that reduces latency in the delivery of web content by reducing the physical distance between the server and the user. Cached versions of web content are stored in multiple geographical locations (points of presence, PoP), which deliver content to visitors based on proximity. |
| Content Security Policy | CSP | An added layer of security that helps to detect and mitigate certain types of attack, including Cross Site Scripting (XSS) and data injection attacks. For more information, see Content Security Policy (CSP). |
| Cascading Style Sheets | CSS | The markup language used to apply styling to HTML elements. CSS syntax is used for Feature tagging and guide positioning in Pendo. For a list of supported selectors, see Using CSS selectors in Feature tagging. |
| Core Event | – | A specific action taken in your application that you've defined as a key indicator of value. You can designate up to 10 tagged Features, Pages, and Track Events as Core Events for each app in your subscription. Core Events are used to track PES and listed separately from other events when building segments and reports. |
| CSS selector | – | The part of a CSS rule set that selects the content you want to style. Pendo makes use of CSS selectors for element matching. |
| Daily active users | DAU | The number of active, unique visitors in a day. See also WAU and MAU. |
| Data Explorer | – | A custom reporting tool that's used to gain deeper insights into visitor or account behavior by querying event, guide, or app data to visualize trends and comparisons. Break usage down by metadata, compare segments or date ranges, filter by event properties, or add formulas. For more information, see Data Explorer. |
| Data Mappings | – | A page in the Pendo UI where you can see the name and type of data that Pendo uses for analyses. For more information, see Data mapping and data types in Pendo and Configure visitor and account metadata. |
| Designer | – | An unofficial term used to describe the Visual Design Studio, which is the in-app designer that allows you to create and edit guides within your application and to tag Features and Pages. |
| Designer (classic) | – | The name of the classic in-app designer that has been replaced by the Visual Design Studio. |
| Document Object Model | DOM | A programming language for web documents (webpages) that allows programs to interact with the structure, style, and content of the webpage dynamically. Each object in the DOM corresponds to a part of the webpage, such as elements, attributes, and text. For more information, see Introduction to the DOM. |
| DOM tree | – | A hierarchical data representation of a webpage's structure, style, and content according to the DOM. The root of the DOM tree represents the webpage itself, and each node underneath it represented the structure of the webpage's elements. Each node in the DOM tree represents a part of the webpage, such as an element, attribute, or text object. |
E-F
| Term | Abbreviation | Description |
|---|---|---|
| Element matching | – | A method for allowing you to target elements in your application through CSS selectors so that you can tag Features, and choose locations for tooltip guides and badge locations. |
| Event | – | A specific action that a visitor takes in your application that Pendo can track and analyze. Pendo collects these actions as raw events to track visitor behavior within your application. Events can be: click events, focus events, load events, Track Events, or guide events. For more information, see Events overview. |
| Event properties | – | Details associated with an event. Event properties are used in reports and segments to target or analyze how your visitors are using your application over time. There are two types of event properties: global and custom. For more information, see Event properties. |
| Exclude List | – | A subscription-wide setting available to Admins that filters out events from the metrics and calculations for segments. For more information, see Exclude and Include Lists. |
| Extract, transform, and load | ETL | A standard data integration process that combines, cleans, and organizes data from multiple sources into a single, consistent data set for storage in a data lake, data warehouse, or other unified data repository. |
| Features | – | The tagged UI elements in your application, such as buttons and links, used throughout Pendo in segments, funnels, and so on. For more information, see View and manage tagged Features. |
| Feature tagging | – | The process of selecting the UI elements in your application that Pendo identifies as Features in its analytics. Feature tagging is retroactive, so you can tag relevant Features when you need them and still have all of the data. For more information, see Feature tagging. |
| Feedback (classic) | – | Part of the classic suite of Pendo tools designed to centralize and prioritize user feedback. For more information, see Overview of Pendo Feedback. This is different from the feedback collection tool in Listen. |
| Feedback (Listen) | – | A page in the Listen platform where you can manage customer feedback in saved table views. Each feedback view includes AI-powered insights and high-level trends. Though it has similar features, the Feedback page in Listen is different to the classic Pendo Feedback product. For more information, see Overview of Pendo Listen. |
| First visit | – | The date and time that Pendo first receives an event from an account or visitor. |
| Focus event | – | When a visitor interacts with an element without clicking on it, such as tabbing through elements in your application. Focus events are used to track how visitors engage with your application. Specifically, focus events are used to calculate time on app. |
| Funnel | – | A behavior report in Pendo that allows you to measure how visitors move through a defined series of steps in your application. Funnels can provide high-level clarity on where your visitors “drop off” when following these steps. For more information, see Funnels. |
G-H
| Term | Abbreviation | Description |
|---|---|---|
| General Data Protection Regulations | GDPR | A regulation that governs data protection and privacy rules in the EU and the European Economic Area as of May 25, 2018. |
| Goal | – |
Create and track an ongoing or time-bound usage goal for a specific Page, Feature, or Track Event. Define your goal based on the number of clicks or views, accounts, or visitors. For more information, see Event goals. See also Guide goal. |
| Guide | – | An in-app message, designed in Pendo, that can be used to alert users of new features, walk users through tasks, poll users, onboard users, and so on. We offer multiple types of guides, including tooltip, lightbox, banner, and walkthrough (multi-step guide). Guides can be tied to a Page or element inside of a Page, For more information, see Create a guide. |
| Guide event | – | A user interaction with a guide, such as a button click or form submission. Guide events capture specific guide-related behavior, which you configure in the guide step settings. |
| Guide goal | – |
Guide goals measure guide effectiveness by tracking adoption of a specific Feature, Page, or Track Event after viewing a specific guide. For more information, see Set guide goals. |
| Historical metadata | – | Historical metadata allows you to capture the past values of up to 25 metadata fields, instead of just the current value associated with a visitor or account. This feature gives you the ability to track changes in metadata values over time. For more information, see Historical metadata. |
I-J
| Term | Abbreviation | Description |
|---|---|---|
| Identity management | – | Identity management links the activities performed by a visitor before they signed in to your app with the activities they performed as an identified visitor. For more information, see Identity management. |
| Identity Provider | IdP |
A service that manages end-user accounts analogous to user directories such as LDAP and Active Directory, and can send SAML responses to service providers to authenticate end users. Examples: Google, Azure, Okta. |
| Include List | – | A subscription-wide setting available to Admins that only collects data from server domains that you specify. For more information, see Exclude and Include Lists. |
| Journey | – | Journeys focus exclusively on analyzing the sequential steps visitors take to complete a workflow. These journeys highlight common routes, completion times, and inefficiencies. For more information, see Workflow journeys. |
K-L
| Term | Abbreviation | Description |
|---|---|---|
| Key-value | – | A set of two linked data items, where the key is a unique identifier that points to the corresponding value. You can add custom key-values in the Pendo install script to pass additional metadata from your visitors and accounts. |
| Last visit | – | The most recent date and time that Pendo received an event from an account or visitor. |
| Layout | – | A format that can be applied to guides deployed in your application. Layouts hide the underlying HTML and CSS, allowing non-technical users to create and edit guides in a form-field interface. For more information, see Guide layouts. |
| Listen | – | Pendo's continuous discovery, validation, and planning platform consisting of the ability to collect feedback, create and validate ideas, and build roadmaps. For more information, see Overview of Pendo Listen. |
| Load event | – | When a visitor loads a URL in your application. Also referred to as Page view events, load events are used to track visits to tagged Pages in your application. |
M-O
| Term | Abbreviation | Description |
|---|---|---|
| Monthly active users | MAU | The number of unique, active visitors in a month. See also DAU and WAU. For more information, see Monthly active users (MAU). |
| Metadata | – | A set of data that describes and gives information about other data. Pendo stores metadata at the account and visitor levels. For more information, see Configure visitor and account metadata. |
| Most recent browser | – | Data that the user agent collects from the browser, which includes browser name, browser version, and operating system. |
| Most recent server | – | The server name parsed from the URL associated with the last event sent by a visitor. |
| Net Promoter Score | NPS | A common metric for customer loyalty and overall user satisfaction. NPS can be measured over time and used to compare products. For more information, see Understand NPS metrics. |
| Number of days active | – | The sum of every day within a date range that contains at least one event from a visitor or account. |
| Number of events | – | The sum of all events (clicks, loads, and so on) coming into Pendo. Time on app serves as a better indication of activity. |
| Organization | The configuration level above the subscription level, used to group Pendo subscriptions. Organization settings control shared functionality across subscriptions. For more information, see Organization settings overview. |
P-R
| Term | Abbreviation | Description |
|---|---|---|
| Page | – | The URLs that you've tagged in Pendo to track views. A Page in Pendo can capture multiple URLs. For more information, see View and manage tagged Pages. |
| Page tagging | – | The process of identifying URLs in your application that Pendo identifies as Pages in its analytics. Page tagging is retroactive, so you can tag relevant Pages when you need them and still have all the data. For more information, see Page tagging. |
| Path | – | A behavior report in Pendo that shows a visual representation of the sequence of actions that visitors took before or after interacting with a specific Page, Feature, or Track Event. Paths can help you understand how users naturally navigate your app. For more information, see Paths. |
| Pendo Academy | – | A website where Pendo customers can learn Pendo products and best practices for being product led. It offers on-demand courses, live classes, and certification opportunities. For more information, see academy.pendo.io. |
| Poll | – | A survey of visitor opinion that you can add to guides to gather feedback from your users. Available poll types include: Multiple Choice, Open Text Field, Yes/No, Number Scale, and NPS (Net Promoter Score). For more information, see Add guide content using building blocks. |
| Processing | – | A status given to a newly created or edited Feature or Page while Pendo retroactively finds and reclassifies historical events based on that Feature or Page. The amount of time a Feature or Page is in "Processing" depends on the amount of data you have in Pendo. |
| Product Areas | – | Specific, tangible locations that represent core areas of your application, used to filter your analytics and feedback by parts of your application. For more information, see Product Areas. |
| Product Engagement Score | PES | Pendo-specific metric for understanding product health. It combines three metrics tied to user engagement: adoption, stickiness, and growth. For more information, Product Engagement Score (PES). |
| Resource Center | – | A customizable menu that a user can open from a badge in your app. The Resource Center provides on-demand access to contextual help, such as published guides, support articles, and announcements. For more information, see Overview of the Resource Center. |
| Retention | – | Retention in Pendo refers to tracking user return rates over time. The retention report analyzes cohorts based on visitors' first interactions, while the Retention by First Use dashboard widget focuses on early event usage's impact on retention compared to average rates. For more information, see Retention and Retention by First Use widget. |
| Roadmap (classic Pendo Feedback) | – | A communication tool that helps you visualize and share your product vision with internal teams. This has been superseded by Roadmaps in Listen. |
| Roadmaps (Listen) | – | A page in the Listen platform where you can map features and initiatives to plan your product delivery and share with your colleagues. This is a more complete feature that builds on classic Feedback Roadmap but is specific to Listen. For more information, see Overview of Pendo Listen. |
S-T
| Term | Abbreviation | Description |
|---|---|---|
| Sample group | – | An integer value between 0 and 99 that's automatically assigned to each unique visitor at random. The field can be used in segments to sample populations of your visitors from their first visit to your application. |
| Security Assertion Markup Language | SAML | An XML-based standard for exchanging authentication and authorization data between an Identity Provider (IdP) and Service Provider (SP). The SAML standard addresses issues that are unique to the SSO solution. |
| Segment | – | A group of accounts or visitors that's filtered based on product usage and metadata. Segments can also be used to target guides at specific populations of your users. For more information, see Segments. |
| Service Provider | SP | Generally, a company, such as Pendo, providing organizations with communications, storage, processing, or other services. |
| Session Replay | – | Pendo's session replay product that allows you to watch playbacks of user interactions with your web apps, providing insights into user behavior through both a visual and data lens. For more information, see Session Replay overview. |
| Single Sign-On | SSO | A system in which the user signs in to the Identity Provider (IdP) once, and can then access multiple systems without being prompted to sign in for each one. Users can access all of their web applications, both behind the firewall and in the cloud, with a single sign in. This centralizes access control to the SAML admin. |
| Snippet | – | A programming term for a small region of reusable source code, machine code, or text. Pendo first-party installation requires the insertion of a short JavaScript snippet into a template that's present on every page in your application. This snippet securely and asynchronously loads a JavaScript file, called the install script, from our CDN. |
| Software development kit | SDK | The Pendo SDK for mobile applications provides developers with tools to instrument their apps and collect data on user interactions, feature usage, and other relevant metrics. This data can then be analyzed within the Pendo platform to gain insights into user behavior and make data-driven decisions to improve the mobile app's user experience. For more information, see Mobile SDK data collection. |
| Staging | – | A guide status before you publish it. Guides in staging display only on specific web application server hostnames or domains (for example, preview.example.com, *.qa.example.com, or demo.example.com). |
| Subscription | – | Your Pendo account with access to one or more applications under a single plan or agreement. Every subscription has a default web application. |
| System for Cross-Domain Identity Management | SCIM | An open standard for securely managing user identity information across multiple domains with application-level provisioning protocols. SCIM provides a defined schema for representing users and groups, and a way of running operations on those user and group resources. |
| Tagging | – | The process of defining the elements or URLs that you want Pendo to track for analytics. You "tag" Features and Pages with Pendo, and Pendo reports analytics based on those tags. For more information, see Tagging with the Visual Design Studio. |
| Theme | – | A group of similar NPS textual responses used to organize and analyze the responses to an NPS survey. Themes can be added manually or using machine learning models. For more information, see Manage NPS themes and insights. |
| Time on app | – | For visitor data, the time (in minutes) each visitor spent in your app. We add one minute to the counter for each minute of any activity (see Event), including page load, focus, clicks, and so on. If a user isn't interacting with the site, we don't count that time. The corresponding visitor time (in minutes) is added together for account data. For more information, see Time on page and app calculations. |
| Track Event | – | An event type that programmatically captures custom point-in-time events, such as errors or API calls. To learn more, see Track Events. |
U-Z
| Term | Abbreviation | Description |
|---|---|---|
| Validate | – | A page in the Listen platform where you can create ideas and then compare, test, and prioritize them. You can also link ideas to specific customer feedback, provide workarounds for ideas, create segments out of ideas, and promote ideas to items on your roadmaps. For more information, see Overview of Pendo Listen. |
| Visitor | – | A unique end user visiting your application. This visitor can belong to one or more accounts. For more information, see Visitors. |
| Visitor report | – | A type of report that provides insights into how your end users interact with your application. You can view the visitor information that's most important to you by customizing the time range, segments, and table data. You can also save your custom reports and export them to CSV. |
| Visual Design Studio | – | Pendo's interface for tagging Pages and Features and for positioning and styling guides. For more information, see Tagging with the Visual Design Studio and Get started with Visual Design Studio for Guides. |
| Weekly active users | WAU | The number of unique, active visitors in a week. See also DAU and MAU. |
| What you see is what you get | WYSIWYG | An editor system in which onscreen content (text and graphics) closely corresponds to its appearance when displayed as a finished product, which might be a printed document, web page, or slide presentation. |
| Workflow | – | A behavior report in Pendo that's used to track visitor progress through expected tasks in your apps. Workflows identify completion rates from start to finish, helping you monitor progress across different applications and analyze completion patterns for specific visitor segments. For more information, see Workflows. |