Adobe Analytics Developer Expert key terms

A document that maps every business requirement to the exact variables, events, and rules used to capture it, serving as the contract between stakeholders and implementers before any code is written.

A measurable business outcome, such as conversion rate or revenue per visitor, that drives which variables and events must be captured and reported on.

A written specification capturing tracking goals, stakeholder sign-off, variable naming conventions, and acceptance criteria used to plan and validate an analytics deployment.

The container that stores collected data and defines its settings, such as enabled variables, currency, time zone, and traffic limits, for a set of related digital properties.

A filtered view built on top of a base report suite that applies segment-like rules and separate settings without duplicating the underlying collected data.

A variable that retains a value beyond the hit on which it was set, based on a configured expiration and allocation model, and is used for attribution and segmentation analysis.

A variable typically used for page-level or pathing context that, by default, is limited to the hit on which it is set and does not persist across subsequent activity.

A counter or numeric metric configured in a report suite that records actions such as purchases or downloads, optionally with serialization and participation settings.

The rule determining which value of a conversion variable receives credit when a success event occurs, such as most recent or original value within the expiration window.

The setting that controls how long a conversion variable's value persists, for example until a visit ends, a purchase occurs, or a fixed number of days passes.

A free-form key-value pair sent with a tracking request that is not stored until mapped to a report variable through processing rules or a processing rule equivalent.

Server-side logic configured in the interface that copies, concatenates, or transforms values into report variables and can trigger or alter events after data is received.

A server-side customization, typically configured by Adobe, that applies conditional logic to incoming data for complex transformations not achievable with standard processing rules.

A structured JavaScript object on the page that holds business facts such as page name, product, and user status, decoupling tracking logic from page markup.

A platform that lets you deploy and govern analytics and marketing tags through configurable rules and extensions instead of hard-coding scripts in page templates.

A tag management construct that listens for a specified event or condition and then fires selected tags, optionally with data element values resolved at runtime.

A named reference in a tag management system that resolves a value from the data layer, cookie, or DOM so tags can consume it consistently.

A single client-side library that sends data to Adobe Experience Platform and Analytics through the Edge Network, replacing the older AppMeasurement and visitor ID libraries.

Adobe's data collection layer that receives SDK requests, enriches them with identity and consent context, and routes them to configured services such as Analytics.

An Edge Network configuration that specifies which Adobe services receive data from an SDK request and how that data is mapped or transformed along the way.

A standardized Experience Data Model structure describing the fields and types sent to the Edge Network, enabling consistent data use across Adobe applications.

Adobe's library for iOS and Android apps that collects lifecycle, action, and state data and transmits it to Analytics through the Edge Network.

Automatically captured mobile app measurements such as installs, launches, upgrades, and crashes that describe app usage without custom tracking code.

The identity system that assigns and persists a unique visitor identifier across Adobe solutions, supporting cross-device stitching when configured appropriately.

A structure in Web SDK and XDM payloads that carries multiple identifiers, such as CRM ID and ECID, so data can be tied to a known person.

A configured import channel that brings offline or external data, such as call center outcomes or CRM attributes, into a report suite for combined analysis.

A lookup table that attaches descriptive attributes, such as product category or campaign owner, to a collected variable value for reporting without changing the original data.

A scheduled export of raw hit-level data, delivered in a defined format, used for warehousing, custom attribution, or integration with external systems.

Programmatic access to Analytics data or configuration through Adobe APIs, enabling automated reporting, bulk configuration changes, and system-to-system data exchange.

A browser or app tool that inspects the exact tracking requests being sent, showing variables, events, and server responses so implementers can confirm what is transmitted.

The process of comparing expected variable and event values against what actually arrives in reporting, using debuggers, raw data, and test report suites.

A documented set of scenarios, expected values, and pass criteria used to verify an implementation before and after release into production.

The practice of capturing and honoring user permission choices so tracking requests are only sent or stored in ways consistent with applicable law and policy.

The policies and controls that define who may access data, how long it is retained, and which identifiers may be collected or shared across systems.

The configured period after which collected data is deleted or anonymized, affecting historical reporting depth and any downstream integrations that depend on it.

A report suite setting that excludes traffic from known spiders and robots so metrics reflect genuine human activity rather than automated requests.

The degree to which collected data is complete, consistent, and trustworthy, maintained through naming standards, validation, deduplication, and monitoring of anomalies.

A reusable definition that filters visitors, visits, or hits by rules on variables and events, used to isolate populations for analysis and comparison.