Adobe Campaign Classic Business Practitioner Expert key terms

The hierarchical tree in the Adobe Campaign client console where folders hold schemas, campaigns, deliveries, workflows, and other objects. Access rights and folder permissions are managed at this tree level.

A user account in Adobe Campaign identified by a login and password. Operators are linked to security groups that determine which folders and actions they can access.

Granular permissions assigned to operators or groups that authorize specific actions, such as exporting data, starting workflows, or managing deliveries, independent of folder access.

A collection of operators that shares a common set of permissions and folder access rights. Assigning rights to groups rather than individuals simplifies administration.

A configuration that links a delivery channel to the schema used for its recipients. It defines which table supplies the target population and which fields feed personalization and address data.

The core data schema (nms:recipient by default) that stores profile records such as name, email, and address. It is the typical target of deliveries and the anchor for many extensions.

An addition of custom fields or new tables to an existing schema without altering the original definition. Extensions are declared in dedicated schemas and merged at load time.

An XML definition that describes a table, its fields, data types, keys, and links to other tables. Schemas drive the database structure and the forms shown in the console.

A schema element that connects two tables, such as a recipient to its subscriptions. Links define cardinality (1-1, 1-N, N-N) and determine how related data is queried and displayed.

A schema-defined list of allowed values for a field, such as a status or gender list. Enumerations standardize stored values and drive dropdowns in the interface.

A workflow activity that filters and extracts records from the database using a visual condition builder or SQL. Its output becomes the targeting dimension for downstream activities.

The table a workflow or delivery operates on, such as recipients or a custom table. It determines which fields are available for filtering and personalization.

A workflow activity that splits an incoming population into several subsets based on filters or percentages, each routed down a separate outbound transition.

A workflow node that divides a population across multiple branches according to defined conditions or random allocation percentages. Often used for A/B tests or holdout groups.

A subset of the target deliberately excluded from receiving a delivery so results can be compared against the contacted population. Used to measure incremental impact.

A visual sequence of activities that automates data processing, targeting, and delivery execution. Workflows run manually or on a scheduler and pass populations along transitions.

The connector between two workflow activities that carries the resulting population and temporary data forward. Conditions can be attached to control which records pass.

A workflow activity that triggers execution at defined times or intervals, enabling recurring campaigns. It can also wait until a set date before releasing the flow.

A reusable configuration that pre-populates a delivery's properties, content, targeting, and typology. Templates standardize branding and reduce repeated setup work.

A set of business rules applied to deliveries to enforce constraints such as exclusions, frequency caps, or proofing. Typologies help ensure message quality and compliance.

An individual constraint within a typology, such as blocking a send to quarantined addresses or capping messages per recipient per week. Rules can warn or block delivery.

A holding list of addresses that are excluded from deliveries, typically because of hard bounces or spam complaints. Addresses can be released manually after review.

Test recipient records used to check rendering and personalization without sending to real customers. Seeds are attached to deliveries and receive copies of the message.

A test send of a delivery to seed addresses or selected recipients to validate content, personalization, and rendering before the main dispatch.

A reusable snippet of content or logic stored for insertion into multiple deliveries. Blocks can contain static text, dynamic fields, or conditional expressions.

A placeholder in message content that is replaced at send time with data from the recipient record, such as a first name or city. Written using expression syntax.

Message sections that display or hide depending on recipient data or rules, allowing different text or offers for different segments within one delivery.

A record of each message sent, including status, timestamps, and recipient. Logs are the basis for tracking, reporting, and bounce analysis.

A record capturing recipient interactions such as opens and clicks, stored when tracking is enabled. These logs feed delivery and campaign analytics.

A message that could not be delivered to the recipient's server. Hard bounces typically quarantine the address, while soft bounces may be retried.

A configurable view of campaign or delivery data, such as delivery statistics or tracking indicators. Reports can be built with a report editor or queried from aggregated data.

A configured task that loads data into or extracts data from Campaign tables. Jobs define source files, mapping, and reconciliation keys, and can run manually or on schedule.

The field used to match imported records to existing ones, deciding whether a row updates an existing profile or creates a new one. Choosing it correctly prevents duplicates.

A workflow activity that reads a file and inserts or updates records in the database. It handles column mapping, deduplication, and rejection of invalid rows.

The programmatic interface Campaign exposes for external systems to create, read, or update objects such as recipients and deliveries. Access is controlled by session authentication and rights.

A tracked link that lets recipients opt out of future communications. It updates the recipient's consent status and is required for compliant marketing email.

The practice of limiting how long personal data is stored and purging records when no longer needed. Campaign supports retention rules and deletion workflows for compliance.