Adobe Campaign Standard Developer Expert flashcards
Adobe Campaign Standard Developer Expert · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Profile resource extension table
- Adding fields to the Profile resource in Adobe Campaign Standard creates a separate extension table joined one-to-one to the profile table, so each read of those fields costs an extra join.
- Custom resource namespace prefix
- Custom resources and their fields use the cus namespace; the internal name must be unique, free of spaces and special characters, and the data model must be published before use.
- Enumeration field type
- An enumeration is a shared list of labeled values referenced by many fields; the internal value name is what gets stored, so renaming it later can orphan existing data.
- Collection link cardinality
- A collection defines a one-to-many link from a parent resource to child records; modeling many-to-many requires an intermediate resource holding a link to each side.
- Target mapping
- Target mapping binds a delivery or workflow to a target dimension schema such as Profile, and that schema determines which fields personalization and typology rules can reference.
- Incremental query activity
- Incremental query targets only records created or modified since the previous execution, using a date or identifier field, so recurring workflows avoid rescanning the whole table.
- AND-join activity
- AND-join merges two workflow branches and releases a single outbound transition only after both inbound transitions are activated, reconciling them on a shared key.
- Deduplication activity
- Removes duplicate records on a chosen unique key, keeps the first record according to a sort order by default, and can send duplicates to a separate complement transition.
- Wait activity
- Pauses a workflow branch for a fixed duration or until a specific date, enabling time-based follow-ups and delayed sends inside a single workflow definition.
- Keep interim populations
- A workflow option that preserves each activity's temporary work table between executions; useful for debugging, but it increases database volume and should be off in production.
- Pressure typology rule
- Limits how many deliveries one recipient may receive within a defined period and can spread remaining messages over later days instead of excluding them.
- Fatigue typology rule
- Caps the number of messages sent to a single recipient per period on a channel; messages above the cap are excluded rather than deferred to later days.
- Delivery analysis stage
- The targeting phase where the audience is built and typology rules, quarantines, and duplicates are applied, with exclusions reported in the delivery audit before sending.
- Personalization block
- A reusable snippet of content or script stored centrally and inserted with a personalization tag, so one edit updates every place that references it.
- Test profiles
- Profiles flagged for testing that receive proofs and can be added to a delivery target to preview personalization and rendering before the production send.
- xtk.session.Write
- JavaScript API call usable in a workflow code activity that creates or updates records from an XML document, for example inserting a profile or writing a log record.
- Transactional Messaging API
- REST endpoint that sends an event-triggered message to a single recipient using a declared event and message template, returning an identifier for tracing the request.
- Workflow trigger API
- REST call that activates a workflow whose first activity is an external signal, passing a JSON payload that downstream activities can read during execution.
- Custom resource API
- REST access to a custom resource that has the API option enabled in its definition and whose data model is published, supporting filtered reads and record updates.
- logInfo function
- Logging function in the JavaScript code activity that writes a diagnostic message to the workflow execution log, used alongside logWarning when debugging scripted steps.
- Load file activity
- Imports a delimited or fixed-width file from an external account, requiring format, encoding, column mapping, a deduplication key, and a defined update mode.
- Extract file activity
- Builds an output file from a workflow transition by selecting columns and applying sorting and formatting, before optional compression and transfer to a remote server.
- Transfer file activity
- Moves files between the Adobe Campaign server and an external account such as SFTP or S3, uploading or downloading around import and export steps.
- Reject file output
- Lines that fail import validation or deduplication are written to a separate reject file for review, while accepted lines continue through the normal workflow path.
- Organizational unit
- An entity that scopes users, folders, and deliveries to part of the organization, so operators only see and act on objects belonging to their unit.
- Security group permissions
- Groups grant rights on resources and folders, such as read, write, or sending deliveries; users accumulate all rights from every group they belong to.
- Control Panel IP allowlist
- A hosted console setting listing the addresses permitted to reach the campaign instance and its SFTP server; connections from unlisted addresses are rejected.
- Audit trail
- A chronological record of administrative and user actions such as logins, exports, and configuration changes, used for compliance investigations and periodic access reviews.
- Workflow work tables
- Each activity stores its outbound population in a temporary table prefixed wkf; the cleanup technical workflow purges them, and orphaned tables bloat the database.
- Delivery exclusion causes
- Reasons recorded per address when targeting removes a profile, such as quarantine, denylist, duplicate, typology rule, or already targeted, visible in the delivery audit.
- Alert activity
- A workflow activity that sends a notification email when a defined error condition occurs, giving early warning that a recurring workflow execution has failed.
- Segmentation activity
- Splits an incoming population into several subsets in one pass using successive filters, replacing multiple separate query activities and lowering overall workflow cost.