Glossary

An abandoned cart is an online shopping cart that contains one or more products but is left behind before the shopper completes the purchase. It is a common ecommerce signal that can point to friction, uncertainty, or a change in the shopper’s intent.

An abandoned journey is a digital journey that stops before the user reaches the intended outcome, such as completing a purchase, submitting a form, or finishing a reservation. It highlights where people leave, but not automatically why they leave.

Acquisition analysis is the process of examining where users come from and how different acquisition sources influence engagement and conversion. It helps teams compare channels, campaigns, landing pages, and audiences so they can invest in the sources that bring valuable customers—not just traffic.

Anonymization is the process of changing personal data so that a person can no longer be identified directly or indirectly. In digital experience work, it helps teams learn from behavior while reducing the amount of identifying information they collect, store, or share.

An app-to-web journey is the connected path a person takes when they start in a mobile app and continue on a website. It helps teams understand whether the handoff preserves the person’s intent, context, and progress instead of treating the app and website as separate experiences.

An authenticated user is a person whose identity a website or app has verified, usually through a sign-in step, before giving access to an account or protected experience. In digital experience work, that verified state can help teams connect behavior to a known account or user identifier—when the organization collects and uses that data appropriately.

Autocapture is a digital analytics method that automatically collects user interactions—such as clicks, taps, scrolls, form changes, and page views—without requiring each event to be defined in advance. It gives teams broad behavioral data they can explore and analyze retrospectively across websites and apps.

Average cart value is the average amount of revenue generated by each completed ecommerce transaction. It helps teams understand how much customers typically spend when they buy, not just how many customers convert.

Behavioral evidence is observable information about what people actually do when they interact with a website, app, or digital product. It can include actions such as clicks, scrolls, navigation paths, drop-offs, and repeated interactions, helping teams test assumptions against real behavior.

A behavioral segment is a group of users defined by the actions they take, such as viewing a product, abandoning a form, or returning to an app. Teams compare these groups to understand different experiences and decide what to improve.

A broken element is a user-interface component that does not work, appear, or respond as users expect. It can be a button, form field, menu item, link, filter, or other part of a website or app that blocks or disrupts a task.

Bug reproduction is the process of recreating the conditions and actions that cause a software problem so another person can observe and investigate it. It turns a vague report into a repeatable path for testing, diagnosis, and fixing.

Business impact analysis (BIA) is a structured process for identifying how a disruption could affect an organization’s critical activities, customers, finances, and operations. It helps teams decide what must be restored first, how quickly, and with which resources.

Chat analytics is the process of collecting and analyzing chat conversations to understand what customers need, how they feel, where they encounter friction, and how effectively the interaction resolves their issue. It turns chat messages and related service data into patterns that teams can use to improve support, products, self-service, and digital journeys.

Checkout abandonment happens when a shopper starts the checkout process but leaves before completing the purchase. It focuses on friction inside the purchase flow, rather than every shopper who leaves at an earlier cart or browsing stage.

A checkout funnel is the sequence of steps a shopper follows from entering checkout to completing an order. It helps teams see where people progress, hesitate, or leave before purchase.

A click map is a visual report of where people click on a webpage or tap on a mobile screen. It turns aggregated interaction data into an easy-to-scan picture of which page elements attract attention—and which are overlooked.

A cohort is a group of users or accounts that share a defining characteristic, behavior, or starting point within a specified period. In digital analytics, teams compare cohorts over time to understand how different groups adopt, engage with, convert, or remain active in a product or experience.

Cohort analysis is a way to compare groups of users who share a defining trait or a starting point, such as the month they signed up or the channel that acquired them. It helps teams see how behavior, conversion, engagement, and retention change across groups over time.

Cohort comparison is the practice of comparing defined groups of users to see how their behavior, outcomes, or experiences differ over the same period. It helps teams move beyond averages and identify which audiences are retaining, converting, or engaging more or less successfully.

A contact reason is a structured label that describes why a customer reaches out to a company. Grouping interactions by reason helps teams spot recurring needs, friction, and opportunities to improve the customer experience.

Conversation intelligence is the use of AI and language analysis to turn spoken and written customer interactions into structured insights. It helps teams understand what customers are saying, how they feel, what drives contact, and where the wider experience can improve.

A conversion blocker is anything that prevents or seriously disrupts a person from completing an important action, such as buying, signing up, submitting a form, or starting a trial. It can be a technical error, confusing design, missing information, or another experience problem that causes users to stop before they reach the goal.

A conversion funnel is a model of the steps people take from first interaction to a desired outcome, such as a purchase, signup, or subscription. It helps teams measure where users progress, pause, or leave so they can improve the experience and increase conversions.

A conversion path is the sequence of interactions a person takes before completing a desired action on a website or app, such as purchasing, signing up, or submitting a form. It helps teams understand not just whether users convert, but how they get there and where they may encounter friction.

A cross-channel journey is a customer’s path across two or more connected touchpoints, such as email, a website, a mobile app, a store, or customer support. It focuses on how one interaction influences the next, rather than treating each channel as a separate experience.

A cross-device journey is the sequence of interactions a person has with a brand across more than one device, such as researching on a phone and completing a purchase on a laptop. It connects those interactions to reveal the full experience instead of treating each visit as unrelated.

Cross-session analysis connects activity from multiple visits—often across devices or channels—to the same user or account, when identity signals allow it. It helps teams understand a customer journey beyond a single session.

A cross-session journey is the sequence of interactions a person has with a website or app over two or more visits, viewed as one connected experience. It helps teams understand what happened before, between, and after individual sessions—including when a user returns to continue research or complete a goal.

Customer journey analytics is the practice of collecting and analyzing how people move through interactions with a brand across digital touchpoints. It helps teams see the paths customers take, where they encounter friction, and which journeys lead to valuable outcomes.

Data accuracy is the degree to which collected data correctly reflects what happened in the real world. In digital experience work, accurate behavioral data helps teams trust the events, metrics, and patterns they use to improve websites, apps, and customer journeys.

Data completeness is the degree to which all required data is present and captured for a defined purpose. In digital analytics, it means the important user actions, attributes, and outcomes you expect to analyze are recorded without unexplained gaps.

A data controller is the person or organization that decides why personal data is processed and how that processing happens. In digital experience work, identifying the controller helps teams assign privacy responsibilities before they collect, analyze, or share visitor data.

Data governance is the system of policies, roles, standards, and controls that determines how an organization collects, manages, protects, and uses data. It helps teams treat data as a trusted asset throughout its lifecycle, from creation and capture through sharing, retention, and deletion.

Data masking is the practice of hiding, replacing, or transforming sensitive values so people and systems can use data without exposing the original information. It helps teams reduce privacy risk while keeping enough context for analysis, testing, or troubleshooting.

Data privacy is the responsible handling of information about people, from collection and use to storage, sharing, and deletion. It helps organizations use data for useful purposes while respecting people’s choices, rights, and expectations.

A data processor is a person or organization that processes personal data on behalf of a data controller. The processor follows the controller’s documented instructions and helps carry out the agreed data-handling work under a contract.

Data quality describes how well data reflects reality and meets the standards needed for a specific use. In digital experience work, it helps teams judge whether clicks, pageviews, events, errors, and other signals are trustworthy enough to guide decisions.

Data retention is the practice of deciding how long information should be kept, where it should be stored, and what should happen when it is no longer needed. It helps organizations balance useful history with privacy, security, legal, and operational responsibilities.

A data source is a system, application, file, device, or service where information originates or from which information is collected. In digital experience work, data sources provide the behavioral, business, and customer context teams use to understand what people do and decide what to improve.

A data subject request is a request from an individual to an organization about personal data relating to them. It can ask for access, correction, deletion, restriction, portability, or objection, depending on the applicable privacy law and circumstances.

Data validation is the process of checking whether data follows defined rules before it is stored, analyzed, or used. These checks can test formats, ranges, required fields, allowed values, relationships, and other conditions that determine whether data is fit for a particular purpose.

A dead click is a click or tap on a digital interface that produces no visible response. It often signals that an element looks interactive but is not working, is not actually interactive, or does not match what the user expected.

Drop-off is the point in a digital journey or conversion funnel where users stop progressing before completing the intended goal. It helps teams see where a process loses people so they can investigate the causes and improve the experience.

A dynamic variable is an extra piece of session context sent to Contentsquare as a key-and-value pair. Teams use it to describe what happened during a web or app session—such as an A/B test variation, feature state, rating, or error—so they can segment and understand experiences more precisely.

Entry-to-exit analysis is the study of how people move through a website or app from the page or screen where they arrive to the point where they leave. It helps teams see common paths, unexpected routes, drop-offs, and the experiences that lead to conversion or other goals.

Error count is the total number of recorded errors during a defined time period, journey, page, or audience segment. In digital experience work, it helps teams see how often technical or functional problems occur, then investigate which errors affect users and outcomes.

An error spike is a sudden, unusual increase in software or website errors over a defined period. It is an early warning that something may be disrupting user journeys, system performance, or a key business action.

An event stream is a chronological timeline of actions and page events connected to a user journey. In a Session Replay player, it helps teams move through a replay and jump directly to moments such as clicks, errors, form submissions, or other important interactions.

An exit point is the page, screen, or step where a visitor or user leaves a website, app, or digital journey. It shows where a session ended, but it does not by itself explain whether the exit was expected or caused by friction.

Fake door testing is a product validation method that presents a realistic but not-yet-built feature or product entry point—such as a button, menu item, or call to action—to measure whether people try to use it. Teams use the resulting behavior to estimate demand before committing to full development.

Feature engagement describes how deeply, frequently, and successfully users interact with a specific feature after they discover it. It looks beyond whether someone tried a feature once to examine whether the feature helps users make progress and becomes part of a useful behavior pattern.

A friction signal is a measurable sign that users are struggling, hesitating, repeating an action, or abandoning a digital task. It does not identify the cause by itself; it tells teams where to investigate the experience more closely.

Frustration score is a metric that estimates how much friction a user encounters on a page, across a group of pages, or during an entire session. It helps teams find difficult parts of a digital experience and decide which issues deserve attention first.

Full journey intelligence is an approach to understanding how people discover, use, and return to a digital experience—and how those behaviors affect business outcomes. It brings journey data together with experience context so teams can see not only what happened, but why and what to improve next.

A funnel step is one defined action, page, or milestone in a user’s path toward a goal, such as viewing a product, starting checkout, or submitting a form. Teams use funnel steps to see how many users move forward and where they stop.

The General Data Protection Regulation (GDPR) is a European Union law that sets rules for collecting, using, storing, and sharing personal data. It gives people stronger rights over their information and requires organizations to handle that information lawfully, transparently, and securely.

A geographic segment is a group of users or customers organized by where they are located, such as a country, region, state, or city. Teams use these groups to compare behavior and tailor digital experiences to the needs of different markets.

In digital analytics, a goal is a defined user action or milestone that an organization wants to measure, such as reaching a page, clicking a button, signing up, or completing a purchase. Tracking goals helps teams connect user behavior with outcomes that matter to the business.

Goal completion is the moment a user finishes a defined action that matters to a business, such as making a purchase, signing up, or submitting a form. Teams measure completed goals to understand whether digital experiences help people reach intended outcomes.

A heat map is a visual way to understand how people interact with a digital page. It uses color to show patterns such as where visitors click, tap, scroll, or move their mouse, helping teams see what attracts attention and where an experience may be difficult to use.

A heatmap summary is a concise interpretation of the behavior patterns shown in a heatmap or zoning analysis. It helps teams quickly see what users engage with, what they overlook, and which page changes may be worth investigating.

Hesitation time is a behavioral metric that measures the average time between a visitor’s last hover over a page element and their first click on it. It helps teams understand whether an element is quickly understood, carefully considered, or causing confusion.

Historical data is information collected about events, behaviors, or results that happened in the past. In digital experience work, teams use it to compare performance over time, understand changing user behavior, and make better decisions using evidence instead of memory or assumptions.

Hover is the interaction that happens when a pointer moves over a digital element without activating it. Websites and apps with pointer input often use hover states to reveal information, signal that something is interactive, or provide visual feedback before a click.

A hybrid app is a mobile application that combines web technologies with a native app shell, often through an embedded webview. It lets teams reuse much of their code across platforms while still distributing the app through app stores and connecting to device capabilities.

Impact prioritization is the practice of ranking ideas, problems, or improvements by the difference they are expected to make to a defined goal. In digital experience work, it helps teams focus limited time and resources on changes most likely to improve outcomes such as conversion, revenue, retention, or user satisfaction.

Impact quantification is the practice of measuring how a user behavior, experience, or issue connects to outcomes such as conversion, revenue, retention, or task completion. It helps teams compare opportunities and focus effort where an improvement could matter most.

In IT service management, an incident is an unplanned interruption to an IT service or a reduction in service quality. The goal of incident handling is to restore normal service as quickly as possible and limit impact, even when the underlying cause is not yet known.

An interaction is an action a person takes with a website, app, or digital interface—such as clicking, tapping, scrolling, typing, or swiping. In digital experience work, interactions are evidence of what users try to do and how the interface responds.

A JavaScript error is a problem that occurs when a browser or other JavaScript runtime cannot parse or execute code as expected. On a website, it can stop an interaction, prevent part of a page from working, or create a poor experience even when the problem is not immediately visible to the user.

A journey bottleneck is a step, page, interaction, or system condition where users repeatedly slow down, become confused, or stop while trying to reach a goal. In digital experience work, finding the bottleneck helps teams focus improvement efforts on the part of the journey that is creating the most friction or lost opportunity.

A journey loop is a pattern in a customer journey where someone revisits a previous page, step, or decision instead of moving straight toward an outcome. It can reflect normal research and comparison, but repeated looping can also signal confusion, friction, or unmet needs.

Journey visualization is a visual way to show the paths people take through a website or app. It turns many individual interactions into an at-a-glance view of common routes, detours, drop-offs, and outcomes.

A key event is a tracked user action that is especially important to a business, such as completing a purchase, submitting a lead form, or activating a product feature. Marking an action as a key event helps teams focus analysis and reporting on outcomes that matter most.

A landing page is a focused web page created for a specific audience, campaign, or conversion goal. Visitors may arrive after clicking an ad, email, search result, or other link, and the page is designed to guide them toward one main action.

Lifetime value (LTV) is an estimate of the total revenue or profit a business expects from a customer over the full relationship. It helps teams look beyond a first purchase or single session and make decisions that support repeat value.

LLM analytics is the measurement and analysis of digital journeys influenced by large language models (LLMs), including AI-referred traffic, prompts in AI assistants, and interactions driven by AI agents. It helps teams understand how these emerging sources affect discovery, engagement, and conversion.

Looping behavior is when a person repeatedly returns to the same page, screen, or step during a digital journey instead of progressing toward a goal. It can reveal confusion, missing information, comparison needs, or a broken part of the experience.

In Contentsquare, a mapping is a way to organize a website’s pages into page groups using conditions. It lets teams choose whether to analyze pages individually or view aggregated data for pages that share a template, such as product or category pages.

MCP integration connects an AI assistant to external tools and data through the Model Context Protocol. For Contentsquare, it gives teams a way to ask natural-language questions about digital experience data from compatible AI tools, without moving manually between reports and systems.

Mobile apps are software applications designed to run on mobile devices such as smartphones and tablets. They give people focused ways to complete tasks, consume content, communicate, shop, or use a service from a mobile device.

A mobile SDK is a packaged set of code, libraries, APIs, and documentation that developers add to a mobile app to use a capability without building every part from scratch. Depending on the SDK, it can support development, analytics, payments, messaging, identity, performance monitoring, or other app functions.

Monthly active users (MAU) is the number of unique users who meet a defined activity criterion at least once during a month. Teams use it to understand the reach and recurring engagement of a website, app, or digital product over time.

A native app is software built for a particular operating system, such as iOS or Android, using that platform’s own development tools and interfaces. Native apps are installed on a device and can use platform-specific features to deliver a responsive, integrated experience.

A natural language query lets a person ask a system for information using everyday language instead of a specialized query language. The system interprets the request, retrieves or analyzes relevant data, and returns an answer, visualization, or other useful result.

A navigation path is the sequence of pages, screens, or interactions a visitor follows through a website or app, from entry to exit or another goal. It shows the route people actually take, which may differ from the route a team expects.

Negative sentiment is an unfavorable thought, feeling, or opinion that a person expresses about a brand, product, service, or digital experience. Teams often identify it in survey responses, feedback, reviews, support conversations, or other qualitative data so they can understand what is going wrong and decide what to improve.

An omnichannel conversation is a continuous customer interaction that can move between channels—such as phone, chat, email, messaging, or an AI agent—without losing the customer’s context or conversation history. It connects what a customer says in one place with what happens in the rest of their journey.

On-page behavior describes how people interact with the content and elements on an individual webpage or app screen. It helps teams understand what users notice, use, ignore, or struggle with—not just whether they arrived or converted.

On-site search is a feature that lets visitors search within a website or app for products, services, information, or other content. It helps people who arrive with a specific need move from a search query to a useful result or next step.

Onboarding analysis is the structured study of how new users move through a product’s first-use experience, where they encounter friction or drop off, and which changes help them reach value and activation sooner.

A page group is a set of one or more web pages organized together by shared conditions, such as a URL pattern or page type, so teams can analyze them as a meaningful unit.

Pages per session is the average number of pageviews recorded during one website session. It is calculated by dividing total pageviews by total sessions, so it helps teams estimate how deeply visitors explore a site during each visit.

A pageview is one recorded view of a web page. It is a basic website analytics measure that helps teams understand how often pages are loaded or viewed, including repeat views by the same visitor.

In digital experience analytics, path analysis examines the routes users take through a website or app, from an entry page or event to an exit, conversion, or return visit. It helps teams see common, successful, unexpected, and incomplete journeys so they can improve the experience.

A path to purchase is the sequence of interactions and decisions a potential customer takes from recognizing a need to completing a purchase. It focuses on the buying process, which can move across channels, pages, sessions, and devices rather than following one straight line.

Personal data handling is the responsible management of information that identifies, relates to, or can reasonably be linked to a person. It covers the full data lifecycle, from collection and use to protection, sharing, retention, and deletion.

Personal data redaction is the process of concealing or replacing information that could identify a person while keeping the rest of a record usable. In digital experience analytics, it helps teams study behavior without exposing sensitive details such as email addresses, payment data, or long identifiers.

Personally identifiable information (PII) is information that can identify a person directly or indirectly. In digital experience work, recognizing PII helps teams learn from behavior while limiting unnecessary exposure of personal details.

Privacy-first analytics is an approach to measuring digital behavior that treats privacy, transparency, data minimization, and user choice as design requirements from the beginning. It aims to give teams useful insight without collecting or retaining more personal data than they need.

Product experimentation is a structured way to test changes to a digital product, feature, or experience with real users. Teams use evidence from these tests to learn what helps users and the business before making a change available to everyone.

Pseudonymization is a privacy technique that replaces direct identifiers with codes or other references, while keeping the information needed to reconnect those references to a person separately and securely. It helps organizations analyze useful patterns without exposing names, email addresses, or similar identifiers to everyone who handles the data.

Qualified traffic is website or app traffic from people who fit a business’s target audience and show signals of relevant intent, making them more likely to take a valuable action. The exact definition depends on the business model, audience, and conversion goal.

Qualitative feedback is descriptive input that explains what people think, feel, need, or experienced in their own words. It can come from open-ended survey answers, interviews, reviews, support conversations, feedback forms, and other research methods.

Quantitative data is information expressed in numbers that can be counted, measured, compared, or analyzed statistically. In digital experience work, it can show how many people visited a page, how often users clicked an element, or what percentage completed a purchase.

Quantitative-to-qualitative analysis is a workflow that starts with numerical evidence to locate a problem or opportunity, then uses qualitative evidence to understand the behavior, experience, or motivation behind it. In digital experience work, it helps teams move from “what is happening?” to “why is it happening?” before deciding what to change.

Rage click detection is the process of identifying a burst of repeated clicks or taps on the same element or area of a website or app. It helps teams spot moments where users may be frustrated, confused, or waiting for an interaction to respond.

A real-time alert is an automated notification sent when live or newly collected data shows a condition that needs attention quickly. In digital experience work, it helps teams spot errors, traffic changes, performance regressions, or conversion problems while they can still affect users and business results.

Retention analysis is the study of how many users or customers return, remain active, or complete a chosen action over time. By comparing groups that started at different times or took different actions, teams can see when engagement falls and which experiences are linked to lasting value.

A retention cohort is a group of users who share a starting point—such as signup, first purchase, or feature adoption—and whose return behavior is tracked over time. Comparing retention cohorts shows whether newer or different groups stay active longer, return more often, or churn sooner.

A retention curve is a chart that shows the share of a starting group of users who remain active over time. It helps teams see when people stop returning, compare cohorts, and identify the behaviors or experiences associated with longer-term engagement.

Retention rate is the percentage of customers or users who continue to use a product, service, or experience during a defined period. It helps teams understand whether people are finding enough ongoing value to return, renew, or make another purchase.

Retroactive analysis is the practice of examining historical data to answer new questions after the data was collected. In digital analytics, it lets teams explore past user behavior, redefine metrics or funnels, and investigate issues without waiting for a new tracking setup.

Revenue at risk is an estimate of sales or other commercial value that could be lost—or not captured—when a digital experience problem stops customers from completing a valuable action.

Searchandizing is the practice of applying merchandising rules to an ecommerce site’s internal search results. It helps businesses make products easier to find while balancing shopper intent with goals such as promotion, inventory, margin, or conversion.

In digital analytics, a segment is a defined group of users, sessions, or visits that share characteristics or behavior. Teams use segments to compare experiences and outcomes instead of treating all traffic as one audience.

Segment comparison is the practice of comparing the behavior, performance, or outcomes of two or more defined user groups. It helps teams see where experiences differ—for example, between new and returning users, mobile and desktop visitors, or users from different acquisition channels.

A segment condition is a rule that decides which users or sessions belong in an analytics segment. It lets teams focus on a specific audience, behavior, outcome, or context instead of analyzing all traffic together.

A segment filter is a rule that narrows digital experience data to a defined group of users or sessions. Teams use one or more filters to compare audiences, investigate behavior, and focus analysis on the experiences that matter most.

A session is a bounded period of activity by a user on a website or app. It groups related interactions—such as page views, clicks, and conversions—so teams can analyze a single visit without treating it as the same thing as a person.

Session capture is the collection of a user’s interactions during a visit to a website or app. It can include actions such as clicks, scrolls, taps, swipes, page changes, and events so teams can understand what happened during a digital experience.

A session replay event stream is a chronological list of actions, page events, and other signals shown alongside a session replay. It lets teams jump to the exact moments when users click, scroll, encounter errors, or show other meaningful behavior.

Session replay privacy masking is the practice of hiding sensitive information in recorded website or app sessions so teams can study user behavior without exposing personal data. It preserves useful context—such as clicks, scrolling, navigation, and errors—while masking content that should not be visible in a replay.

A session replay segment is a defined group of recorded user sessions selected because they share a behavior, characteristic, event, or other condition. It helps teams focus on the replays most relevant to a question instead of reviewing every available recording.

A session replay summary is a concise overview of one or more recorded user sessions. It helps teams find important behaviors, friction points, and moments worth investigating without watching every replay from start to finish.

Smart Capture is an automatic data-collection approach that records user interactions across a website or mobile app without requiring teams to define every event in advance. It gives teams a broad behavioral dataset to analyze immediately and revisit as questions change.

Synthetic monitoring uses automated tests to imitate selected user journeys through a website or app in a controlled environment. By checking availability, speed, and key workflows on a schedule, teams can find regressions and performance problems before they affect real customers.

Tagless analytics is an approach to collecting digital behavior data without manually adding a tracking tag for every event. It helps teams study interactions as they happen and revisit past behavior when new questions arise.

A touchpoint is any moment or interaction when a person comes into contact with a brand or digital experience, such as an ad, product page, checkout step, app screen, or support interaction. Looking across touchpoints helps teams understand the customer journey and remove friction before it affects conversion, satisfaction, or retention.

Tracking tag implementation is the process of adding, configuring, and checking a tracking tag so a website or app can collect behavioral data for analytics. It covers choosing where the tag runs, connecting it to a tag management system or site code, respecting privacy settings, and verifying that data is being collected as expected.

A traffic source is the origin that sends visitors to a website or app, such as a search engine, social network, email, advertisement, referral link, or direct visit. It helps teams understand where audiences come from before they analyze what those visitors do next.

A unified customer journey is a connected view of how a person interacts with a brand across touchpoints such as websites, mobile apps, stores, and support. It helps teams understand the experience as a whole instead of treating each channel as a separate path.

An upsell is a sales or merchandising approach that encourages someone to choose a higher-value version, tier, quantity, or upgrade of what they already intend to buy. In digital experiences, a good upsell makes the added value clear without interrupting or pressuring the customer.

A user is a person or other entity that interacts with a website, app, or digital service. In digital experience analytics, the term can describe both the people behind interactions and the measurement records used to understand their behavior.

User confusion is the uncertainty people feel when a digital experience does not make its meaning, next step, or expected action clear. It can appear as hesitation, repeated attempts, misdirected clicks, or abandonment—even when the product or page is technically working.

User friction is anything that makes it harder for someone to complete a goal on a website or app. It can slow users down, confuse them, or cause them to abandon a journey before taking the next step.

User hesitation is the pause between noticing an interface element and acting on it, such as waiting before clicking a call to action, submitting a form, or choosing a product option. It can signal careful consideration, uncertainty, or confusion, so it should be interpreted with surrounding behavior and outcomes.

User identity is the set of identifiers and attributes used to represent a person, account, device, or other user in a digital system. In digital analytics, it helps connect activity across sessions, devices, and touchpoints so teams can understand behavior as a more complete journey.

User identity resolution is the process of connecting activity that belongs to the same person or account across identifiers, sessions, devices, channels, or data systems. It helps teams move from fragmented records to a more complete view of a user’s digital journey.

A user segment is a defined group of people who share a characteristic, behavior, or experience. Digital teams use segments to compare how different groups navigate a site or app and decide where to improve.

A user struggle signal is a measurable clue that someone is having difficulty completing a task in a website, app, or other digital experience. It helps teams see where friction may be happening so they can investigate the cause and improve the journey.

Verbatim feedback is a customer’s or user’s exact written or spoken response, kept in their own words rather than rewritten as a summary. It preserves the language, emphasis, and context that can help teams understand what people experienced and why.

In digital analytics, a view usually means a page view: one occasion when a webpage is loaded or reloaded. It is a basic volume metric that helps teams understand which pages attract attention, but it needs context from sessions, behavior, and outcomes.

Visitor behavior is the pattern of actions people take while using a website or app, such as entering, navigating, clicking, scrolling, searching, converting, or leaving. Studying these patterns helps teams understand what visitors are trying to do and where the digital experience supports or frustrates them.

Voice of customer (VoC) is the structured practice of listening to what customers say, need, and experience, then using those insights to improve products, services, and digital experiences. It combines direct feedback with context such as customer journeys and behavior so teams can act on the reasons behind outcomes.

A web app, short for web application, is software that people use through a web browser to complete tasks, interact with data, or access services. Unlike a mainly informational website, a web app is designed for ongoing interaction, such as signing in, managing an account, buying a product, or submitting a form.

Web performance monitoring is the ongoing measurement of how quickly, reliably, and smoothly a website loads and responds for users. It combines performance data with context about devices, browsers, locations, and user behavior so teams can find issues, understand their impact, and improve the digital experience.

A web-to-app journey is a path that starts on a website and continues inside a mobile app. It connects the two experiences so people can move from web content, campaigns, or tasks into a relevant in-app destination with as little repeated effort as possible.

A zone is a defined area or page element that can be measured to understand how users interact with it. In digital experience analytics, zones make it possible to connect on-page behavior—such as clicks, exposure, scrolling, and conversions—to specific parts of a website or app screen.

Zone comparison is the practice of comparing how users interact with specific areas or elements of a digital page. It helps teams see whether a zone performs differently across audiences, time periods, devices, traffic sources, or page variants, rather than looking at one page view in isolation.

Zone hierarchy is the way nested page or app elements are organized into parent and child zones for digital experience analysis. It helps teams move from a broad component-level view to the individual elements inside it, while keeping the relationship between them clear.

A zone selector is an in-product control used to choose one or more page or screen elements for analysis. In Contentsquare, it lets teams create zones so they can measure and compare how people interact with specific content, components, or navigation areas.

Zoning analysis is a way to measure how visitors interact with defined areas of a digital page, such as banners, buttons, images, menus, and forms. It connects those page elements to behavioral metrics so teams can see what attracts attention, drives action, or creates friction.

A zoning summary is a concise, AI-generated explanation of the main patterns in heatmap and zoning data. It helps teams understand how page elements perform without having to interpret every metric manually.