Adobe Target Business Practitioner Professional key terms

A configured test, personalization, or recommendation in Adobe Target that defines which content different visitors receive. It contains experiences, audiences, goals, and traffic settings, and must be activated before it can affect live traffic.

A specific content variation delivered to a visitor within an activity, such as a different hero image or offer. Each experience is mapped to one or more audiences and is compared against the others during reporting.

The baseline experience in a test that represents current or default content. Performance of other experiences is measured as a lift or loss relative to this baseline, making it the reference point for statistical comparison.

A named set of targeting rules that determines which visitors qualify for an activity or experience. Audiences can use built-in attributes like geography and device, or custom parameters and profile attributes passed into Target.

A single condition inside an audience definition, such as browser equals Chrome or custom parameter category equals shoes. Rules are combined with AND/OR logic and evaluated in real time when a visitor requests content.

A stored value about a visitor, such as loyalty tier or past purchase count, held in the Target visitor profile. It persists across sessions and can be used for targeting and for building audiences.

A key-value pair passed into Target on a page or API call (often called an mbox parameter) that describes the current context, such as page type or campaign source. It is available for targeting and reporting but is not stored long term.

The record Target maintains for an individual visitor, containing attributes, segments membership, and behavioral history. It enables consistent personalization across sessions and devices when identities are stitched together.

Server-side JavaScript that computes a derived visitor attribute, such as category affinity or a recency bucket, and writes it to the profile. The resulting value can then be used in audiences and offers.

The Target delivery point embedded in a page or app that requests and renders personalized content. Each mbox has a name and can carry parameters, and it is the unit that activity offers are assigned to.

The content Target delivers into an mbox, such as HTML, an image, JSON, or a redirect. Offers are stored in the offer library or defined inline and are selected by the activity logic for a given visitor.

A test that splits traffic randomly among two or more experiences and compares their performance on a chosen metric. It measures which variation wins and typically requires a control for comparison.

A test that evaluates multiple elements on a page simultaneously, each with multiple variations, to find the best combination. It also reports which individual elements contribute most to performance.

An activity setting that shifts traffic toward the better-performing experience as data accumulates, while still exploring alternatives. It aims to reduce the cost of a losing variation during the test.

A personalization capability that uses a machine-learning model to choose, per visitor, the experience most likely to drive the goal. It differs from Auto-Allocate by selecting content individually rather than shifting overall traffic.

The probability that an observed difference between experiences is not due to chance, usually expressed as a confidence level. Target reports it to help practitioners judge whether results are trustworthy before declaring a winner.

A range around an estimated metric, such as conversion rate, that likely contains the true value. Overlapping intervals between experiences suggest the difference may not be real.

The percentage improvement or decline of an experience relative to the control on the goal metric. Positive lift indicates the variation outperformed the baseline during the measurement period.

The number of visitors or conversions included in an analysis. Too small a sample produces unreliable conclusions, so practitioners estimate required size before launching a test.

The success measure defined for an activity, such as conversion rate, revenue per visitor, or a custom event. It determines what Target reports and how automated allocation decisions are made.

The full set of measures tracked for an activity, including the primary goal and additional metrics for context. They allow practitioners to check whether gains on one metric came at the expense of another.

The percentage of eligible visitors assigned to each experience, and the overall share of total traffic entering the activity. It controls exposure and how quickly enough data accumulates for analysis.

The analysis views in Target that show activity performance by experience, audience, and metric over time. Reports support comparison, segmentation, and export for deeper analysis.

Delivering content tailored to an individual or segment based on known attributes, behavior, or models, rather than showing everyone the same experience. It aims to improve relevance and business outcomes.

A Target capability that suggests products or content using algorithms such as recently viewed, frequently bought together, or people who viewed this also viewed. Criteria and design control what is shown and how.

An activity type that delivers different content to defined audiences without a statistical test. It is used to personalize by segment, such as showing region-specific messaging to each geography.

The connection that lets Target use AEP segments, attributes, and datasets for targeting and reporting. It enables real-time audience sharing and richer profile data beyond native Target attributes.

The Adobe Target JavaScript library that requests and renders personalized content on web pages. It replaces the legacy mbox.js and supports features such as single-page app support and on-device decisioning.

A Target capability that evaluates activities locally in the browser or app rather than calling Adobe servers. It reduces latency and improves resilience but requires the decision logic to be downloaded ahead of time.

The technical setup that connects a site or app to Target, including the library, mboxes or scopes, parameters, and identity handling. Correct implementation is a prerequisite for accurate targeting and reporting.

A configuration boundary in Target that groups activities, audiences, and offers for a specific site, brand, or app. Properties support permissioning and help separate workspaces in large organizations.

A logical container that organizes properties, activities, and user access for a team or brand. Workspaces let administrators partition the account and control who can view or edit each area.

The access-control model that assigns users to roles and scopes them to specific workspaces or properties. It governs who can create, approve, edit, or view activities and settings.

A predefined permission level such as Approver, Editor, or Observer that determines what actions a user can take in Target. Roles are combined with workspace scope to limit access appropriately.

A preview mode that lets practitioners view activities without affecting live traffic or reporting. It is used to validate content, targeting, and rendering before an activity is activated.

An activity type that requires a specific Target license, such as Recommendations, Auto-Target, or certain AI-driven features. Practitioners must confirm entitlements before planning these solutions.

The documented rationale for an optimization effort, covering the problem, hypothesis, expected impact, and resources required. It aligns stakeholders and justifies prioritization before activity design begins.

A testable statement predicting that a specific change will produce a measurable effect on a chosen metric. A clear hypothesis guides experience design and defines what a result will confirm or refute.

The planned length of an activity, chosen to cover full business cycles and reach adequate sample size. Ending too early risks false conclusions from incomplete or skewed data.