Adobe Journey Optimizer Developer Expert key terms

A configurable, multi-step orchestration canvas that moves a profile through events, conditions, and actions over time. It defines entry sources, branching logic, timing waits, and the messages or updates delivered at each node.

The trigger that admits profiles into a journey, such as a segment qualification, a business event, or an audience read. Each journey has one entry configuration, and profiles re-enter only if the profile allows re-entrance.

A branching activity that evaluates profile attributes or expression results to route a profile down one path or another. It can compare values, test segment membership, or evaluate contextual data captured at the entry event.

A timed delay in a journey that holds a profile for a fixed duration or until a specified date and time before continuing. It shapes pacing and can be combined with conditions to model time-sensitive outreach.

A non-profile-triggered event, often sent from an external system via API, that starts or advances journeys. It carries a payload of contextual fields that journey conditions and messages can reference.

The journey setting that determines whether a profile that already completed or exited a journey can enter it again. Options control whether re-entry is allowed, blocked, or limited by a time window.

The point at which a profile leaves a journey, either by completing the final activity, meeting an exit condition, or being removed. Exit behavior affects downstream reporting and message eligibility.

An alternate branch taken when a wait or action does not complete within a defined duration. It lets journeys handle unresponsive profiles or delayed external events without stalling the main path.

A testing capability that runs a journey in a sandbox-like mode using sample or test profiles so developers can validate logic and message rendering before publishing to live audiences.

A formal data model that defines the structure, fields, and relationships of profile and event data. Schemas determine which attributes are available for segmentation, personalization, and journey conditions.

The shared data standard that organizes customer data into classes, field groups, and schemas. It provides a common language so ingested data can be unified into a real-time customer profile.

A reusable collection of schema fields that can be attached to multiple schemas, often aligned to a common data concept. Field groups promote consistency without duplicating field definitions.

A container for ingested records that conforms to a schema and feeds the profile or event stores. Datasets track batch and streaming loads and are the unit used for data ingestion and governance controls.

The unified, near-real-time view of each customer assembled from identity-linked records across datasets. It merges attributes and events so journeys and personalization can use a single profile per person.

The linked set of identifiers, such as email, loyalty ID, and device ID, that resolves records to the same person. It underpins profile unification and segment evaluation across sources.

A named symbol that labels a type of identifier, such as email or CRM ID, so the platform knows how to match records. Namespaces determine which identifiers can link into the identity graph.

Rules that decide how conflicting profile attribute values from different datasets are combined into one profile. Policies set precedence and can prefer the most recent or a specific source.

A set of profiles defined by criteria such as attributes, events, or audience membership. Segments are evaluated by the platform and can trigger journeys or target messages and offers.

The process that determines which profiles currently satisfy a segment definition. It can run on a schedule for batch segments or continuously for streaming segments, with results feeding journeys and targeting.

The state of a profile belonging to a segment at a given time. Membership changes can act as journey entry triggers or as conditions that gate message delivery and offer eligibility.

Continuous segment evaluation that reacts to incoming events and profile updates as they arrive. It enables near-real-time audience qualification for time-sensitive journeys and personalization.

The setup that connects a delivery channel, such as email, push, or SMS, to the platform, including credentials, sender identities, and routing. Correct configuration is required before messages can be sent.

A reusable configuration that stores channel-specific delivery settings, such as sender address, tracking preferences, and execution parameters. Presets let authors apply consistent settings across messages without re-entering them.

The content and delivery definition sent to a profile, including channel, template, and personalization. Messages are attached to journey actions or campaigns and are rendered at send time.

The act of transmitting a rendered message to a recipient through a configured channel. Delivery outcomes, including successes and failures, are tracked and reported for troubleshooting and optimization.

A message that could not be sent or accepted by the downstream channel, often due to invalid address, suppression, or configuration error. Failures are surfaced in reporting and logs for diagnosis.

A set of addresses or identifiers that must not receive messages, such as unsubscribes, complaints, or regulatory exclusions. Suppression is applied at send time to protect deliverability and compliance.

The recorded permission from a profile that governs whether and how they may be contacted on a channel. Consent policies are evaluated before delivery to enforce preferences and legal requirements.

The capability that selects the best offer for a profile from eligible candidates based on rules, eligibility constraints, and ranking. Decisions can be embedded in messages and web experiences.

A configuration that combines eligibility rules, a ranking strategy, and fallback behavior to choose an offer. It defines how candidates are filtered and ordered for a given decision request.

A constraint that filters which offers can be considered for a profile, based on attributes, context, or placement. Rules narrow the candidate set before ranking so only appropriate offers compete.

The method used to order eligible offers, such as by priority, formula, or profile-based score. The top-ranked offer is typically selected, with fallback options used if no candidate qualifies.

The use of profile, contextual, or offer data to tailor message and experience content to an individual. It relies on expressions and helper functions evaluated at render time.

A tool for writing and validating the expressions that insert dynamic values into content, conditions, and decisions. It supports profile attributes, functions, and operators with syntax checking.

An isolated environment that separates data, configurations, and users from other environments. Sandboxes support development, testing, and staged promotion of journeys, schemas, and settings.

The assignment of roles and permissions that determine what users can view, create, or change. It limits administrative scope and protects sensitive data and production configurations.

Rules that restrict how data can be used, such as labeling sensitive fields and limiting downstream use. Policies enforce privacy and contractual constraints across segmentation, personalization, and delivery.

A chronological record of administrative and configuration changes made in the environment. It supports accountability, troubleshooting, and investigation of unexpected behavior.

A sample profile used to preview and validate message rendering, personalization, and journey logic before launch. It helps catch missing attributes and expression errors without contacting real customers.