Adobe Campaign Classic Developer Expert key terms

An XML definition file that declares a table's fields, keys, indexes, links, and enumerations. Adobe Campaign generates the physical SQL table and input forms from it. Once deployed, a schema is modified only through an extension schema.

A schema whose namespace and name match an existing schema, letting you add fields, links, or indexes to a built-in table without editing the original definition. Extension content is merged at load time and survives product upgrades.

The attribute on a schema link stating how many records can relate on each side: 1-1, 1-N, N-1, or N-N. It determines whether Campaign stores a foreign key column or builds an intermediate join table.

A named list of allowed string values defined once in a schema and referenced by fields. It drives drop-down selections in the interface and keeps coded values consistent across tables, queries, and imports.

A schema field with no stored column; instead an expression, often SQL, is evaluated when the record is read. Useful for derived values such as concatenated names or aggregate counters maintained elsewhere.

The core schema holding profile data and serving as the default targeting dimension for direct marketing deliveries. Most customer schemas extend it or link to it through a foreign key on a shared identifier.

The schema a workflow or delivery operates on, specifying which table supplies the population. It determines the fields offered in activities and personalization, and the keys used to identify each record.

A workflow activity that selects and filters records from the database using a targeting dimension, filter conditions, and optional joins, then outputs the resulting population on its outbound transition.

The arrow connecting two workflow activities that carries a temporary result table and its schema. Activities can have several outbound transitions, and each transition can be enabled, disabled, or guarded by a condition.

A workflow step that removes duplicate rows from the incoming population by comparing one or more keys or expressions. It can keep the first record, the most recent, or a record chosen by a sort criterion.

A workflow activity that adds columns to the working table from another table or from a defined expression. The joined data becomes available downstream for personalization or for further filtering and splitting.

A workflow activity acting as a timed start point. It can run once at a fixed date or repeat on an interval, triggering the workflow independently of any inbound data or external event.

A workflow activity that waits for, or fires, a named signal. Another workflow or script activates it through the signaling API, letting separate processes synchronize without polling the database.

A named value stored on a workflow instance and readable by JavaScript and expressions inside activities. Variables can hold strings, numbers, dates, or lists, and persist for the lifetime of the instance.

The server-side JavaScript object used to build and execute database queries. It takes a schema name and condition, returns XML results, and can be called through SOAP or inside workflows and JSSPs.

Event handlers declared in a schema, such as load, save, or activate, that run on the Campaign server when a record is read or written. They enforce business rules beyond simple field validation.

Functions and attributes that embed raw SQL fragments in query conditions or computed fields when the standard operators are insufficient. They must be used carefully to avoid injection and portability problems.

The query structure inside a queryDef or workflow query that combines filters with operators such as AND, OR, equals, and isNull. Each condition names a field, an operation, and one or more values.

A reusable piece of content stored in the database and inserted into deliveries by name. Blocks can hold text, HTML, or an expression, and are shared across templates, messages, and web applications.

Markup that displays different content depending on a recipient's data, using if/else constructs or dynamic content variants. It lets one delivery carry several versions without creating separate deliveries.

The Adobe Campaign module that selects offers for a contact based on eligibility rules, weightings, and contexts, then tracks proposals and responses. It supplies personalized offers for deliveries and inbound interactions.

The dual editing modes in the delivery content editor: a visual view and an HTML source view. Developers use source view to add personalization syntax, tracking tags, and conditional markup with precision.

A reusable delivery definition holding content, targeting, typology, and routing settings. New deliveries created from a template inherit those properties, keeping campaigns consistent and reducing configuration effort.

A test recipient excluded from delivery statistics, used to check rendering and inbox placement. Seeds can be added to the target automatically and are often routed to specific domains or providers.

Adobe Campaign's transactional messaging module, which sends event-triggered messages such as order confirmations through templates and a REST or SOAP API, with real-time or batched execution modes.

The table recording every message Campaign attempts to send, with recipient, delivery, date, and status. It underpins reporting, quarantine logic, and troubleshooting of delivery failures.

A test render of a delivery sent to a small set of addresses before the real send. Proofs let you validate content, personalization, and links without contacting the full target population.

Files containing JavaScript executed by the Campaign web server to produce HTML or XML responses. They implement custom web applications, API endpoints, and dynamic pages served to visitors.

The classic Campaign interface exposing methods on schemas and sessions, such as xtk:session and xtk:queryDef, over HTTP. Clients authenticate, then read and write records using XML payloads.

The process that synchronizes data between a Campaign instance and its remote or mid-sourcing databases. Replication workflows and technical processes copy changed records so each node holds a consistent view.

A saved definition describing which file, schema, fields, and mapping an import or export uses. Templates run manually or from workflows and support delimited, fixed-width, and XML file formats.

A Campaign user account holding login credentials, group memberships, and rights. Operators are the unit of authentication and are audited when they change data, run workflows, or send deliveries.

Granular permissions assigned to operators or groups, such as the right to start workflows, manage deliveries, or export data. They complement folder-level access and are checked at each operation.

A setting restricting which IP addresses may connect to the console or web interface, and how. Operators assigned to a zone must connect from permitted addresses, optionally with VPN enforcement.

A container used to export schema definitions, forms, workflows, templates, and other configuration from one instance and import it into another. Packages are the standard vehicle for moving customizations between environments.

The log of administrative and data-changing actions in an instance, recording who did what and when. It is essential for troubleshooting, compliance reviews, and tracing unexpected modifications.

A Campaign object defining a set of pages, variables, and processing logic served to visitors. Web applications handle subscriptions, preference centers, and other forms and can read or write recipient data.

The mechanism by which a web application keeps values between page displays. Variables are declared in the page's storage schema and persisted either in the database or in the session.