An **Event-scoped Dimension** is a way to describe *what was true about a specific interaction at the moment it happened*. In **Conversion & Measurement**, that matters because most decisions—creative, targeting, UX, offer design, funnel fixes—depend on understanding *which* events occurred and *under what conditions*.

Event-based Analytics is a modern approach to understanding what people do across websites, apps, and digital products by recording meaningful actions (“events”) and analyzing how those actions lead to outcomes like sign-ups, purchases, upgrades, or retained users. In **Conversion & Measurement**, it’s one of the most practical ways to connect day-to-day user behavior to real business performance.

Event Taxonomy is the structured system you use to name, define, and organize user interactions (events) so they can be measured consistently across products, websites, apps, and campaigns. In **Conversion & Measurement**, it’s the difference between “we tracked something” and “we can trust our numbers.” In **Analytics**, it’s the foundation that makes dashboards interpretable, funnels comparable, and experiments credible.

Event Parameter Mapping is the discipline of translating the raw details that come with a user action (an “event”) into the standardized fields your measurement stack expects. In modern Conversion & Measurement, it’s how teams turn messy, inconsistent event payloads into trustworthy, comparable signals that power Analytics, reporting, experimentation, and optimization.

Event Parameter is the detail layer that turns “something happened” into “this specific thing happened, to this person, in this context.” In Conversion & Measurement, that context is often the difference between guessing and knowing why performance changed. In Analytics, Event Parameter values make events usable for segmentation, attribution, funnel analysis, and debugging tracking quality.

Event Count is one of the most fundamental concepts in Conversion & Measurement because it answers a deceptively simple question: **how many times did a specific user interaction occur?** In Analytics, those interactions can include anything from a button click to a video play, file download, form start, add-to-cart action, or purchase confirmation.

Engagement_time_msec is a measurement field that represents **how much time users actively engage** with your site or app, recorded in **milliseconds**. In modern **Conversion & Measurement**, it helps teams move beyond “pageviews and clicks” to understand whether visitors actually spent meaningful time with content, features, or flows. In **Analytics**, it’s a foundational ingredient for evaluating traffic quality, diagnosing UX friction, and building audiences that reflect real interest—not just accidental landings.

Engagement Time Per Session is a modern way to quantify how much “active attention” a user gives your website or app during a single visit. In **Conversion & Measurement**, it helps teams move beyond simple traffic counts and start evaluating whether users are actually consuming content, exploring products, and progressing toward outcomes that matter.

Engaged Sessions Per User is a behavioral quality metric that helps you understand whether people are having meaningful interactions with your website or app—not just “showing up.” In **Conversion & Measurement**, it acts as a bridge between traffic volume and business outcomes, revealing whether your acquisition and content strategies attract users who actually do something valuable.

Ecommerce Purchases are the recorded events that confirm a customer completed a transaction in an online store. In **Conversion & Measurement**, they represent the most important “bottom-of-funnel” outcome because they tie marketing activity to revenue. In **Analytics**, Ecommerce Purchases become the foundation for understanding what’s working: which channels drive sales, which campaigns create profitable customers, and which site experiences convert visitors into buyers.

Ecommerce Item Scope is the practice of measuring and analyzing performance at the individual product (item/SKU) level rather than only at higher levels like carts, orders, or sessions. In **Conversion & Measurement**, it answers questions such as: *Which products truly drive purchases? Which items are frequently viewed but rarely bought? Which SKUs are discounted heavily with little incremental revenue?* In **Analytics**, it ensures your reporting reflects what customers actually interact with—item by item—so teams can optimize merchandising, campaigns, and product strategy with precision.

Device-based Identity is the practice of recognizing and measuring interactions based on identifiers tied to a specific device (or browser/app instance) rather than a verified person. In **Conversion & Measurement**, it helps teams connect ad exposure, site/app behavior, and outcomes (like leads or purchases) to the device that generated them. In **Analytics**, it underpins reporting accuracy, attribution logic, audience building, and deduplication—especially when you can’t reliably join activity across devices.

Modern marketing creates a flood of visits, clicks, sessions, and events from search, social, email, ads, partners, and direct navigation. To make that activity understandable, **Analytics** tools organize incoming traffic into categories that humans can compare and budgets can be allocated against. One of the most important organizing concepts is the **Default Channel Group**.

Debug View is a diagnostic mode found in many measurement stacks that lets you watch tracking data flow through your instrumentation in near real time. In **Conversion & Measurement**, it acts like a live “inspection window” for events, parameters, user properties, and conversion signals before they become the numbers stakeholders rely on. Used well, **Debug View** prevents costly reporting mistakes and helps teams ship accurate **Analytics** implementations faster.

In **Conversion & Measurement**, small tracking mistakes create big business problems: undercounted leads, misattributed revenue, broken funnels, and decisions based on incomplete data. **Debug Mode** is the practical safety net that helps teams detect and fix those issues before they spread into reporting and optimization workflows.

In modern **Conversion & Measurement**, marketers face a recurring problem: not every user action is equally observable, attributable, or trustworthy. **Dau Mau Ratio** is a practical concept used to describe—and manage—that gap. In the context of **Analytics**, it represents a ratio that compares “clean, usable measurement signal” against “noisy, missing, or low-confidence signal” for a defined conversion outcome.

A **Data Warehouse** is one of the most practical investments a modern organization can make for **Conversion & Measurement**. When marketing and product teams rely on scattered dashboards, ad platform reports, and inconsistent tracking, decisions become reactive and hard to justify. A Data Warehouse brings key data together so performance can be measured consistently, explained clearly, and improved confidently.

Data Visualization is the practice of turning raw data into visual formats—charts, tables, maps, and dashboards—so people can understand performance quickly and make better decisions. In the context of Conversion & Measurement, it’s how teams see what’s working across channels, where users drop out of the funnel, and which changes actually improve results.

Data Thresholding is a technique used in Conversion & Measurement and Analytics to limit, suppress, or aggregate reporting when data volumes are too small to be reliable, safe, or privacy-compliant. Instead of showing granular results that could mislead decisions (or potentially expose individuals), systems apply a minimum “threshold” before displaying metrics, dimensions, or segment-level performance.

A **Data Stream** is the continuous flow of marketing, product, and customer signals—events, attributes, and outcomes—moving from where they happen (a website, app, POS system, call center, ad platform) into systems that turn them into insight and action. In **Conversion & Measurement**, a Data Stream is the backbone of trustworthy attribution, funnel analysis, experimentation, and optimization because it determines what you can measure, how fast you can respond, and how confident you are in results. In **Analytics**, it’s the raw material that powers dashboards, models, and decisions—so the quality of the stream often matters more than the sophistication of the reports.

Data Retention is the policy and practice of how long you keep data and in what level of detail—before deleting it, aggregating it, or anonymizing it. In the world of Conversion & Measurement, Data Retention is not a back-office technicality; it directly affects what you can analyze, how far back you can attribute performance, and whether trends you “see” in Analytics are real or simply artifacts of missing history.

Data Quality is the degree to which your marketing and business data is accurate, complete, consistent, timely, and usable for decision-making. In **Conversion & Measurement**, it’s the difference between confidently scaling what works and optimising based on noise. In **Analytics**, Data Quality determines whether reports reflect reality—or merely reflect how your tracking happens to be configured.

Modern marketing runs on evidence. Yet many teams still struggle to answer basic questions—Which channels drive qualified leads? Why did conversion rate drop last week? Which campaigns influence revenue? A **Data Mart** helps solve these problems by creating a purpose-built slice of data optimized for specific decisions, especially in **Conversion & Measurement** and day-to-day **Analytics**.

Data Governance is the practical discipline of making sure your marketing and business data is accurate, consistent, secure, and usable—so your Conversion & Measurement decisions are based on reality, not guesswork. In modern Analytics, the quality of your insights is limited by the quality of the data feeding dashboards, attribution models, experiments, and reporting.

A **Data Filter** is one of the most important (and most misunderstood) building blocks in **Conversion & Measurement**. In plain terms, it’s a rule or set of rules that narrows data down to what you actually need—so your **Analytics** reflects reality, not noise.

A **Data Dictionary** is the practical “source of truth” that explains what your data means, where it comes from, and how it should be used. In **Conversion & Measurement**, that clarity is not a nice-to-have—it’s what prevents teams from optimizing campaigns based on misunderstood metrics, inconsistent event names, or mismatched definitions of a “lead” or “conversion.”

A **Dashboard** is the practical bridge between raw data and everyday decision-making. In **Conversion & Measurement**, it brings key metrics—like leads, purchases, retention, and cost efficiency—into a single, readable view so teams can monitor performance and take action quickly. In **Analytics**, a Dashboard reduces the time spent hunting for insights across tools, reports, and spreadsheets by making the most important signals visible and comparable.

Modern marketing teams rarely win by tracking only “default” numbers. To understand what truly drives revenue, retention, and efficiency, you often need a **Custom Metric**—a measurement you define to reflect your unique business model, funnel, and customer behavior. In **Conversion & Measurement**, a Custom Metric turns scattered data points into decision-ready indicators that map directly to outcomes you care about.

A **Custom Dimension** is a way to attach business-specific context to your measurement data so your reports reflect how your company actually operates. In **Conversion & Measurement**, that context is often the difference between “we got conversions” and “we know which customers, content, experiences, and campaigns created valuable conversions.” In **Analytics**, a Custom Dimension lets you classify users, sessions, events, or items with attributes your default tracking doesn’t capture.

A **Custom Channel Group** is a way to classify incoming traffic and marketing touchpoints into business-friendly “buckets” (channels) that reflect how your organization actually markets—rather than relying on generic, one-size-fits-all defaults. In **Conversion & Measurement**, this matters because channel definitions directly influence how you interpret performance, allocate budget, and explain results to stakeholders.