Adobe Analytics Business Practitioner Professional key terms

A variable that stores a value and credits it to a visitor beyond the hit where it was set, according to a configured expiration and allocation model. Used to attribute success events to earlier marketing or content touches.

A variable that records a value only on the hit where it is sent and does not persist for later attribution. Often used for simple pathing, page-level detail, and list reporting.

A counter or numeric metric tied to an action you want to measure, such as a purchase, lead, or video start. Events can be standard or custom and can be serialized or counted once per visit.

The rules that decide how long a variable value persists (expiration) and which hits receive credit for it (allocation, such as most recent or linear). These settings determine how conversions are credited.

A setting that prevents an event from being counted more than once per visitor or per visit, such as counting a purchase only on the first occurrence. Used to avoid duplicate conversion counts.

A free-form key-value pair sent in the tracking request that has not yet been mapped to a report variable. Processing rules or tag manager rules typically map it into eVars, props, or events.

Server-side logic configured in the interface that copies, sets, or transforms values before data is stored, such as mapping context data into variables or appending text. They apply without redeploying site code.

A structured JavaScript object on the page that holds business data such as page name, product, or user status, decoupled from the tag manager. It gives tagging a stable, documented source of truth.

A tool that loads and manages analytics and marketing tags through configurable rules rather than hard-coded page scripts. It centralizes deployment, versioning, and vendor changes.

The JavaScript library loaded on a page or in an app that builds and sends image requests to the data collection servers. Its version and configuration affect which features and variables are available.

The single HTTP call sent to the collection server that carries all variables, events, and identifiers for one interaction. Each request is one hit and is the raw unit of collected data.

One row of data sent to the collection servers, representing a page view, link click, or other tracked action. Hits are the atomic records that reports aggregate into metrics.

The identifier used to stitch hits into a visitor's history, typically a first-party cookie value or an app-specific identifier. Its reliability directly affects unique visitor and attribution accuracy.

A group of hits from the same visitor with no gap longer than the configured inactivity timeout, typically 30 minutes. Visits reset on timeout or on a campaign-triggered new session.

A metric that credits a value or dimension once per visit rather than once per hit, so a page seen three times in one session counts once. Used to avoid inflating counts in visit-level reporting.

A reusable container-based filter of visitor, visit, or hit data that can be applied to reports and shared across users. Segments define who or what is included in an analysis.

The scope level of a segment: visitor, visit, or hit. The chosen container determines whether qualifying visitors bring all their data or only matching hits into the report.

A custom metric built from a formula combining existing metrics, such as revenue per visit or orders divided by sessions. It is defined once and reused consistently across reports.

A numeric measure of activity or outcome, such as page views, visits, or revenue, produced by aggregating hits. Metrics are the quantitative side of every report table.

A non-numeric breakdown or category used to group metrics, such as page name, campaign, or browser. Dimensions answer the question of which or what, while metrics answer how many.

The rule set that assigns credit for a conversion to one or more preceding touchpoints, such as last touch, first touch, or linear. It shapes which channels appear to drive results.

A classification of traffic source into a named group, such as paid search or natural social, based on processing rules. It standardizes source reporting across many referrers and campaigns.

A query-string parameter appended to inbound links that identifies the campaign source, medium, and name. It lets the platform attribute visits and conversions to specific marketing efforts.

The isolated data repository that receives hits and holds its own settings, variables, and reports. Choosing the right structure affects governance, data volume, and cross-site reporting.

A filtered view of one or more parent report suites that applies segments and settings without duplicating raw data. It lets different teams see tailored data from a shared collection source.

The document that defines every variable, event, and rule in a deployment, including names, purposes, and values. It is the contract between business requirements and technical implementation.

A written statement of the business goals, questions, stakeholders, and success measures a measurement program must serve. It anchors scope decisions and later validation of the solution.

A small set of measures tied directly to business objectives, such as conversion rate or revenue per visitor. KPIs focus dashboards and analysis on outcomes that matter to stakeholders.

Testable conditions that a tracking implementation must satisfy before sign-off, such as expected values in a debug tool. They convert requirements into verifiable checks.

The process of confirming that tags fire and variables carry correct values before and after release, using debug tools and report checks. It catches data errors before they pollute reports.

The degree to which collected data is complete, accurate, consistent, and timely enough for decisions. Common threats include duplicate hits, misconfigured variables, and missing consent.

Automated non-human requests that can inflate visits, page views, and conversions. Known bots are typically filtered, and settings can exclude suspected bots from reports.

The practice of preventing the same action from being counted more than once, through serialization, filters, or implementation checks. It protects conversion and revenue metrics from inflation.

The policies and roles that control who can define, change, access, and export data, including naming standards and approval workflows. It keeps variables consistent and protects sensitive information.

An agreed pattern for labeling variables, events, segments, and reports so their purpose is obvious and collisions are avoided. Consistent names reduce confusion and support self-service reporting.

The user permission required before identifiers or tracking scripts may be set, governed by privacy regulations and platform settings. Without it, tracking may be blocked, reducing data completeness.

The configured period for which collected hit data remains available for reporting and export. Retention choices balance analysis needs against privacy obligations and storage cost.

A visualization showing how many visitors proceed through a defined sequence of pages or events and where they drop off. It highlights friction points in a funnel.

An interactive view of the paths visitors take before and after a given page or event. It reveals common navigation patterns and unexpected exits.

A curated collection of reportlets and visualizations assembled for a specific audience and purpose. Good dashboards answer defined questions rather than display every available metric.

A concise, evidence-backed statement explaining what the data shows, why it matters, and what action is recommended. It converts report output into a decision-ready message for stakeholders.