Adobe Campaign Classic Architect Master key terms

The configuration that links a delivery template to a targeting dimension and defines which recipient records a delivery selects, including filtering and deduplication options applied at send time.

A schema declared as a selectable population for campaigns and deliveries, such as recipients or a custom schema, that determines which fields and filters are available when building a target.

An additive modification to an existing schema that adds fields, links, or indexes without altering the original definition, allowing customization that survives package upgrades.

A short identifier prefixing a schema name that groups custom tables and prevents collisions between customer-defined and Adobe-defined objects during installation and upgrades.

Predefined value lists stored as schema-linked objects that constrain a field to a fixed set of options and can be extended or replaced through customization.

A granular permission flag, such as the ability to start workflows or export data, that is granted to operators or groups and checked by the application before an action is allowed.

An individual account in Adobe Campaign with credentials, group memberships, and assigned rights that determine what the user can view, edit, execute, or administer.

A rule mapping connection contexts, such as IP ranges or reverse-proxy settings, to allowed operator access and security policies like password restrictions or session limits.

A single configurable step in a workflow, such as query, split, union, delivery, or JavaScript code, that receives data, performs an operation, and passes results to downstream steps.

The connection between two workflow activities that carries a named temporary table of records, enabling downstream steps to consume the output of the preceding step.

The main population a workflow operates on, defined by a targeting dimension and a filter, which supplies the initial dataset for activities unless overridden.

A reusable workflow skeleton stored with predefined activities and settings that can be instantiated for recurring operational patterns, reducing rebuild effort and enforcing standards.

A system-level workflow, often running on a schedule, that performs background maintenance such as tracking consolidation, campaign cleanup, or database housekeeping.

A workflow step that waits for an external trigger or a scheduled event before allowing execution to continue, used to coordinate dependent workflows or external processes.

An API or script call that activates a waiting signal activity in a running workflow, allowing external systems to release a paused branch.

The legacy web service interface exposing Adobe Campaign objects and operations through WSDL-described methods, commonly used for integration with external applications and middleware.

JavaScript Server Pages, a server-side scripting mechanism that renders dynamic content and can expose custom HTTP endpoints within the Adobe Campaign web application.

A workflow step that executes server-side JavaScript with access to the workflow's temporary tables and the campaign object model, enabling custom logic inside automation.

A reusable configuration holding content, targeting, typology, and routing defaults for a class of deliveries, from which concrete deliveries are created and personalized.

A control applied during delivery analysis that validates or restricts a message, for example enforcing pressure rules, exclusions, or maximum message volume per recipient.

The pre-send validation phase that resolves the target, applies typology rules, computes exclusions, and produces the final recipient list before the message is rendered or sent.

The table recording each message delivery attempt per recipient, including status, date, and delivery reference, used for reporting and for exclusion and pressure rules.

Records capturing recipient interactions such as opens and clicks, populated from tracking servers and used for engagement reporting, scoring, and reactivation logic.

A deployment architecture where message execution is delegated to a separate hosted instance that receives deliveries from the marketing instance, improving throughput and isolating sending load.

The execution module handling transactional and trigger-based messages, often deployed separately to guarantee low-latency, high-volume delivery independent of batch marketing campaigns.

The arrangement of Adobe Campaign instances and their roles, such as marketing, execution, mid-sourcing, and tracking servers, and how they connect and replicate data.

A portable archive of schema definitions, workflows, templates, and configuration objects used to export customization from one environment and import it into another.

The process that propagates shared data and configuration between instances in a multi-server topology so that execution and marketing environments stay consistent.

A database structure on one or more schema fields that speeds up filtering, joins, and sorting, and whose design directly affects query cost and overall instance performance.

A workflow step that builds a filtered population or extracts data using the query editor, generating SQL whose efficiency depends on indexes and filter selectivity.

A storage area in the underlying database where tables and indexes are placed, affecting disk layout, growth planning, and maintenance operations.

The process of estimating database volume, growth, throughput, and server resources needed to support expected recipient counts, delivery volumes, and workflow concurrency.

A chronological record of administrative and user actions, such as logins, configuration changes, and data exports, supporting investigation and compliance requirements.

A scheduled cleanup that removes old delivery, tracking, and workflow logs according to retention settings, controlling database growth and maintaining performance.

The process of moving an environment to a newer Adobe Campaign build, including compatibility checks, schema and package migration, and regression testing before production rollout.

A non-production instance that mirrors production configuration for testing workflows, integrations, and upgrades before changes are promoted to live systems.

A governance mechanism requiring designated reviewers to validate campaign content or targeting before sending, enforcing separation of duties and regulatory review.