Adobe Campaign Standard Developer Expert key terms

The database entity a workflow or delivery acts on, such as profiles (nms:recipient), subscriptions, or a custom resource. It determines which fields you can filter, select, and personalize with, and which table each activity queries.

The XML definition of a data entity in Adobe Campaign Standard: its fields, keys, indexes, links, and enumerations. Custom resources and extensions are deployed in a package and afterwards become usable in queries and personalization.

Adding fields, links, or indexes to an existing resource, for example extending profiles, without altering the out-of-the-box definition. Extensions are built in the custom resource editor and must pass diagnostics before publication.

A named relationship between two resources with a cardinality of 1-1, 1-N, or N-N. Links drive joins in queries and control how records are reached from a source targeting dimension.

A reusable list of allowed values for a field, stored centrally so that several resources can share the same options. Enumerations keep coded values consistent and behave like normal fields in filters and personalization.

The field that uniquely identifies each record of a resource. Keys determine deduplication behavior, reconciliation during imports, and how links between resources resolve related rows.

The folder tree that organizes resources and objects such as deliveries, templates, workflows, and landing pages, and that carries permissions. An object's placement controls who can see and edit it.

A workflow activity that selects records from the database using a targeting dimension, filters, and optional joins. It outputs a temporary audience that downstream activities can enrich, split, or deliver to.

A workflow activity that adds attributes to the incoming population, either from a linked resource through a join or from a constant or expression. It can also define additional links used later in the workflow.

A workflow activity that routes incoming records into two or more outbound transitions according to filters or a percentage, with an optional residual population. It is the usual tool for A/B splits and segment-based paths.

A workflow activity that removes duplicate records from a population, identified either by a key such as email or by a combination of fields. Duplicates can also be kept on a separate transition for analysis.

A workflow activity that starts the workflow on a defined recurrence, for example every day at a set hour. It can be combined with external signals to trigger executions on demand as well as on schedule.

A wait point in a workflow that resumes only when another workflow or an API call activates it. It allows chained, event-driven orchestration across workflows instead of simple scheduling.

Values declared on a workflow or on a single activity that persist only for the current execution. They carry data between activities, feed personalization, and can be read or written by JavaScript code.

A reusable delivery configuration holding properties, targeting, content, and typology rules. Creating deliveries from templates keeps branding, sender, and routing settings consistent across a program.

A named set of typology rules applied together during delivery analysis or sending to enforce business constraints, such as contact limits, address exclusions, or mandatory proof validation.

A single rule inside a typology. Pressure rules cap how many messages a profile receives in a rolling period, filtering rules remove addresses, and control rules check content or audience before sending.

An address added to a delivery's test list to receive a copy of the proof or the final message. Seeds verify rendering, tracking, and inbox placement without contacting real recipients.

A test send of a delivery to seed addresses or selected profiles, produced for content and personalization review. Analysis and proof sending happen separately from the final target.

Content blocks shown or hidden per recipient using conditions on profile or context data, letting one delivery present several variants without duplicating the whole message.

A saved, reusable fragment of HTML or text content that can be inserted into several deliveries and edited in one place, optionally with its own targeting and personalization fields.

A hosted web page used to collect data, manage subscriptions and unsubscriptions, or confirm an action. Its fields, database mapping, and storage settings are configured inside the platform.

A named topic that profiles can subscribe to or opt out of. Services drive newsletter targeting, connect to landing pages, and are checked before sending subscription-based communications.

The Adobe Campaign Standard capability that sends event-triggered, one-to-one transactional messages, such as order confirmations, through a REST call from an external system using dedicated message templates.

A random share of the target deliberately excluded from a delivery so its behavior can be compared with the contacted population, measuring the incremental impact of the campaign in reports.

The server-side JavaScript interface, built on libraries such as xtk and nms, used in script activities, landing pages, and JSSP to query the database, read variables, and call platform functions.

A JavaScript object describing a database query: schema, filters, ordering, and selected columns. Executing it returns a collection that code can iterate over, typically inside a JavaScript workflow activity.

The REST interface for reading and writing profiles, services, and subscriptions from external applications. Requests are authenticated per technical account and scoped to the tenant's instance.

The Adobe I/O credentials (client identifier, secret, and JWT or OAuth token) that authorize API calls. Each account carries product profiles that limit which endpoints and data it can reach.

A workflow activity that loads a file from a server or exports a population, mapping columns to resource fields and choosing reconciliation, update, and error handling options.

The field used to match inbound import rows to existing records, together with the mode (insert, update, or insert-or-update). It decides whether an import creates duplicates or enriches known profiles.

A saved connection to an outside system, such as an SFTP server, a routing service, or another marketing instance, holding the address and credentials that workflows and deliveries reuse.

Access control objects: operators are individual logins, and groups bundle operators and carry rights on folders and functions. Effective permissions combine group membership with folder-level settings.

The Adobe Admin Console construct that grants a user a set of Campaign Standard permissions, mapping an organizational role onto platform capabilities such as workflow execution or delivery management.

A record of changes and administrative actions captured by the platform, used to trace who modified an object, changed a setting, or altered access during an investigation.

Configurable rules that remove old delivery, tracking, and log data after a set period, keeping database size under control and supporting privacy and compliance obligations.

Per-activity execution history showing start time, duration, output counts, and errors. Restarting or resuming a paused workflow reprocesses only the branches still pending.

The number of messages per hour the platform sends for a delivery, shaped by IP affinity and instance capacity. Heavy volume on one affinity group can slow other campaigns that share those sending IPs.

A holding list for addresses and mobile numbers that hard-bounced or complained, automatically excluded from future sends until an administrator reviews and releases them.