Digital adoption glossary

Plain-English definitions of the digital adoption, user onboarding, and product engagement terms that matter — from activation checklists to time-to-value.

Glossary terms

Digital adoption: Digital adoption is the process by which users move from awareness of a software product to fluent, productive use of it. It applies to both external customers learning a SaaS product and internal employees adopting enterprise tools like Salesforce, Workday, or ServiceNow. Adoption is measured not by signups or installs, but by whether users actually accomplish the work the software was bought to enable. The term is broader than 'onboarding,' which usually refers to the new-user phase. Digital adoption covers the entire lifecycle: onboarding, ongoing engagement, feature adoption, and continuous training as the software changes.
User onboarding: User onboarding is the process by which new users move from sign-up to productive use of a product. In SaaS, onboarding usually covers the first hours to the first few weeks of a user's relationship with the product. Effective onboarding gets users to a defined moment of value quickly enough that they decide to stay and, eventually, pay. Onboarding is distinct from ongoing customer education. Once a user has reached the aha moment and integrated the product into their workflow, the focus shifts to feature adoption and engagement — both related but distinct disciplines.
Product-led growth (PLG): Product-led growth (PLG) is a go-to-market strategy in which the product itself is the primary vehicle for acquiring, activating, and expanding customers. Users sign up directly, experience value through the product, and convert to paid plans without a traditional sales process. Free tiers, free trials, and freemium models are typical PLG mechanics. PLG sits in contrast to sales-led growth (where a buyer evaluates and signs a contract before any user touches the product) and marketing-led growth (where demand-gen drives MQLs into a sales funnel). Modern B2B SaaS often blends approaches, but the PLG label specifically describes companies where the product, not the salesperson, is the primary conversion engine.
Product-led onboarding: Product-led onboarding is the practice of getting new users from sign-up to first value through the product itself, with no human in the loop. The product surfaces guided guides, tooltips, checklists, and in-app help so users can self-serve their way to productive use. There's no kickoff call, no CS-led implementation, no scheduled training. Product-led onboarding is the onboarding practice of product-led growth (PLG) companies. It's distinct from concierge or CS-led onboarding, which can deliver excellent first experiences but doesn't scale to thousands of self-serve users.
Feature adoption: Feature adoption is the process of getting existing users to discover and use specific features within a product. Unlike onboarding, which focuses on first-time users, feature adoption deals with ongoing customers who haven't yet engaged with a particular capability — often a newly shipped one. Feature adoption is measured per-feature, typically as the percentage of eligible users who have used that feature within a given window. A feature with low adoption isn't necessarily a bad feature; it might be undiscovered, misunderstood, or surfaced to the wrong segment. The feature-adoption discipline is the practice of figuring out which is which and intervening accordingly.
In-app messaging: In-app messaging is the practice of communicating with users inside a product, rather than via email, push notification, or external channels. Common formats include banners (persistent at the top or bottom of a screen), modals (full-attention pop-ups), slideouts (less intrusive corner messages), and full-screen takeovers for high-impact announcements. In-app messaging is one-way: the product team publishes; users see (or dismiss) the message. It's distinct from in-app chat or messenger widgets, which are conversational. Both can coexist in the same product — they solve different problems.
In-app guidance: In-app guidance is the broad category of in-product help and education systems that support users as they learn and adopt a product. It encompasses guided guides, contextual tooltips, beacons (highlights drawing attention to UI elements), in-app announcements, checklists, and self-serve help centers. The unifying principle: help shows up inside the product, at the moment of need, rather than requiring users to leave and find it elsewhere. In-app guidance is a superset that includes user onboarding, feature adoption, and self-serve support. A digital adoption platform (DAP) is software that combines all the in-app guidance primitives in one tool.
Net Promoter Score (NPS): Net Promoter Score (NPS) is a customer loyalty metric introduced by Fred Reichheld in 2003. It's calculated from responses to a single question: 'How likely are you to recommend this product/service to a friend or colleague?' on a 0–10 scale. Responses are bucketed: 9–10 are Promoters, 7–8 are Passives, 0–6 are Detractors. NPS is the percentage of Promoters minus the percentage of Detractors, expressed as a number from -100 to +100. The calculation ignores Passives entirely.
Customer Satisfaction Score (CSAT): Customer Satisfaction Score (CSAT) measures how satisfied a customer was with a specific interaction or experience. The standard question is 'How satisfied were you with [interaction]?' on a 1–5 or 1–7 scale. The score is typically calculated as the percentage of respondents who gave a positive answer (4 or 5 on a 1–5 scale). CSAT is most often used at the transaction level — measuring satisfaction with a single support conversation, a specific feature usage, or a specific event in the customer lifecycle. It complements but doesn't replace NPS, which measures longer-term loyalty.
Product tour: A product tour is a guided sequence of in-app steps that walk a user through a feature, workflow, or area of a product. Tours are typically multi-step (3–7 steps is common) and combine narrative explanations with visual highlights of UI elements. They're most often used for new-user onboarding but also appear in feature adoption campaigns and in-product training. Tours can be triggered automatically (on first login, after a feature ships) or manually (a user clicks 'show me how this works'). Modern tours support audience targeting, completion analytics, and skip-and-resume behavior.
Activation checklist: An activation checklist is a list of the high-leverage first actions a user should complete to reach the aha moment in a product. Unlike a one-time tour, an activation checklist persists across sessions — it stays visible in the product (often as a sidebar widget or floating launcher) until the user finishes or dismisses it. Activation checklists are particularly powerful because they map activation to a small, measurable set of actions. The user can see what's left to complete; the product team can see which segments finish and which drop off where.
Aha moment: The aha moment is the moment at which a new user first experiences the core value of a product — the 'oh, I get it now' point that maps to long-term retention. For some products, the aha moment is a single concrete action (sending the first message in Slack, creating the first dashboard in Notion); for others, it's a combination of actions over a session or two. Identifying the aha moment is one of the foundational exercises in PLG product strategy. Once identified, it becomes the activation event the entire onboarding system is designed to drive users toward.
Time to value (TTV): Time to value (TTV) is the duration between when a new user signs up for (or begins using) a product and when they first experience meaningful value. For self-serve B2B SaaS, TTV is typically measured in minutes for simple products and days for more complex ones. For enterprise software, TTV can extend over weeks or months as implementation completes. TTV is closely related to but distinct from time to first action. TTV emphasizes value (the user got something useful out of the product); time to first action emphasizes activity. A user can take an action without experiencing value, and the system that confuses the two ends up gaming activity metrics rather than driving real activation.
Tooltip: A tooltip is a small piece of contextual information that appears when a user hovers, clicks, or otherwise interacts with a UI element. Tooltips are used to explain icons, define terms, label buttons, or surface keyboard shortcuts. Modern product platforms also use tooltips for onboarding hints, feature explanations, and just-in-time help. Tooltips are typically authored without code through a visual editor — the product manager picks an element, writes the tooltip text, and publishes. Modern platforms support audience targeting (different tooltips for different segments), engagement analytics, and self-healing detection when the underlying UI changes.
Contextual help: Contextual help is the practice of surfacing help content where and when it's needed, rather than requiring users to find help elsewhere. It encompasses tooltips, beacons, inline FAQs, in-product search, and an AI agent — anything that resolves a user's confusion without asking them to leave the product. Contextual help is a superset of in-app guidance that emphasizes resolution at the point of need. While in-app guidance can include proactive education (announcements, onboarding guides), contextual help is reactive — it surfaces when the user is signaling confusion or actively looking for an answer.
User experience (UX): User experience (UX) is the sum of every interaction a person has with a product — from the first marketing impression to long-term, deeply integrated use. It covers usability (can a user accomplish their task?), usefulness (does the product solve a real problem?), accessibility (can everyone use it?), and the emotional response the product produces. UX is broader than visual design or interface polish; a beautiful product that's hard to use has bad UX. In SaaS, UX is increasingly measured at every touchpoint: signup, first session, activation, ongoing engagement, support interactions. Modern UX work blends design, research, analytics, and in-product guidance — because shipping a great experience requires more than a polished interface.
User journey: A user journey is the full sequence of steps, actions, and touchpoints a user goes through when interacting with a product to accomplish a goal. In SaaS, a typical journey includes pre-product touchpoints (marketing, signup), the activation arc (first session, aha moment, completed onboarding), ongoing usage (regular workflows, feature adoption), and key lifecycle events (renewal, expansion, support). User journeys can be short (a single task) or long (a multi-month adoption arc). User journey mapping is the practice of visualizing the journey explicitly — listing each step, the user's intent, the emotional state, the touchpoint, and the moments where the experience breaks. It's a research and design tool used to align product, design, marketing, and CS teams around the same picture of how users actually move through the product.
UX design: UX design is the practice of intentionally designing how a product is used: which actions are possible, how they're surfaced, how the system responds, and how users learn what to do next. It overlaps with — but isn't reducible to — UI design. UI design covers the visual surface; UX design covers behavior, structure, guide, and the experience the surface produces. In SaaS, UX design typically combines information architecture (how content and capability are organized), interaction design (how individual UI elements behave), workflow design (how multi-step tasks are sequenced), and feedback design (how the system communicates what's happening). A good UX designer ships things that feel obvious — which is harder than it sounds, because it requires removing all the cleverness that didn't help users.
Digital experience (DX): Digital experience (DX) is the sum of every interaction a user has with a brand through digital channels: marketing site, web app, mobile app, email, push notifications, in-product messaging, and self-serve help. Where user experience (UX) typically focuses on a single product, digital experience considers the entire constellation of digital touchpoints as one experience the user moves through. The distinction matters most for organizations where the user crosses channels frequently — sign up on the marketing site, onboard in the web app, get help via email, and re-engage via push. A good digital experience makes those transitions invisible; a fragmented one makes them friction.
Customer onboarding: Customer onboarding is the process by which a new customer organization moves from purchase to productive use of a product. In B2B SaaS, customer onboarding usually covers more than the user-onboarding experience: it can include procurement, contract setup, technical integration, data migration, training of multiple users, and CS-led implementation milestones. The goal is the customer organization successfully adopting the product, not just any individual user reaching first value. User onboarding (the in-product experience for a new user) is one component of customer onboarding. Strong customer onboarding combines a great in-product user experience with the organization-level work — kickoff, training, integration support — that turns the purchase into actual usage at scale.
Guidance share link: A guidance share link (sometimes called a permalink, guide link, or share URL) is a tokenized URL that, when opened in the product's real domain by an end user, triggers a specific piece of in-app guidance to render immediately. The link bypasses the usual audience-targeting and frequency rules that would normally govern when content appears, because the recipient has been intentionally directed to it. The primitive originated in digital adoption platforms as a way for product teams to test guides — most major DAPs (Pendo, Userpilot, Whatfix, Appcues, Chameleon, WalkMe, Intercom, UserGuiding) ship some version. Modern usage extends well beyond testing: support agents send share links inside helpdesk replies, customer success managers attach them to QBR follow-ups, and lifecycle marketers deep-link emails into specific walkthroughs.