| Term | Abbreviation | Description |
|---|---|---|
| Account | – | A Pendo-specific hierarchy of data collected from the organization (customer) that uses Pendo. An account represents a group of Visitors. |
| 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. |
| Adopt | – | A product line designed to drive digital adoption in internal teams and to understand how employees are using company tools. |
| Adopt Studio | – | The name of the guide designer in Pendo Adopt. For more information and instructions for using Adopt Studio, see the Guide Designer: Adopt Studio article. |
| 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 installing Pendo. |
| 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. |
| 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. |
| 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 the Content Security Policy (CSP) article. |
| 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. See the list of supported selectors in What selectors are supported for CSS feature tagging article. |
| 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 are 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. |
| 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 Mappings and Data Types in Pendo and Visitor and Account Metadata. |
| Daily Active Users | DAU |
The number of unique, active visitors in a day. See also WAU and MAU. |
| Designer | – |
An unofficial term used to describe the Visual Design Studio in Engage and Adopt Studio in Adopt. Both are in-app designers that allow you to create and edit guides within your application. The Visual Design Studio additionally allows you to tag Features and Pages in both Engage and Adopt. |
| 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. |
| Engage | – | A product line designed to help you understand and improve how your end-users interact with your applications with data analytics to track behavior and provide insights on which features are being used, and in-app messages to create and distribute announcements, guides, surveys, and so on. |
| 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, Track Events, Page View Events, or Guide Events. |
| 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 Listing. |
| Feature | – |
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 Tagging and viewing 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 Tagging and viewing Features. |
| Feedback | – |
Part of the Pendo suite of tools designed to centralize and prioritize user feedback. For more information, see Overview of Pendo Feedback. |
| 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 | – |
An analytics tool that allows you to measure how customers move through a defined series of steps in your application. Funnels can provide high-level clarity on where your customers “drop off” when following these steps. For more information, see our Funnels article. |
| 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. |
| 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 (multistep 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. |
| Include List | – |
A subscription-wide setting available to admins that only collects data from server domains and accounts that you specify. For more information, see Exclude and Include Lists. |
| 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. |
| Monthly Active Users | MAU | The number of unique, active visitors in a month. See also DAU and MAU. 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 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. |
| 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, page loads, and so on) coming into Pendo. Time on App serves as a better indication of activity. |
| Page | – | The URLs that you've tagged in Pendo to track page views. A Page in Pendo can capture multiple URLs. For more information, see Tagging and viewing 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 Tagging and viewing Pages. |
| Page View Event | – |
When a page loads or a URL changes. Page View Events are used to track visits to tagged Pages in your application. |
| Path | – |
A visual representation of the sequence of actions that visitors took before or after a target event with a tagged Feature. For more information, see Paths Overview. |
| 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 can be added 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). |
| 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. |
| Product Engagement Score | PES |
A Pendo-specific metric for understanding product health. It combines three metrics tied to user engagement: adoption, stickiness, and growth. |
| Resource Center | – |
A customizable menu that a user can open from a badge on the page. The Resource Center provides on-demand access to contextual help, such as published guides, support articles, and announcements. For more information, see Resource Center Overview. |
| Sample Group | – |
An integer value between 0 and 99 that's automatically assigned to each unique visitor at random. The field can be used to sample populations of your visitors from their first visit to your application. |
| Segment | – |
A group of accounts or visitors that is filtered based on product usage and metadata. Segments can also be used to target guides at specific populations of your users. |
| Snippet | – |
A programming term for a small region of reusable source code, machine code, or text. Pendo installation requires the insertion of a small Javascript snippet into a template that is present on every page of an application. This snippet securely and asynchronously loads a Javascript file, called the install script, from our CDN. For more information, see the Developer's guide to installing Pendo. |
| 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). |
| 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. |
| 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. |
| 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. |
| Visitor | – |
A unique end-user visiting your application. This visitor can belong to one or more accounts (see Account). |
| Visitor Report | – |
A type of report that provides insights into how visitors 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 that overlays the customer’s application for tagging Pages and Features in Engage and Adopt, and for positioning and styling guides in Engage. |
| Weekly Active Users | WAU | The number of unique, active visitors in a day. 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. |
Glossary
Last Updated: