Adobe Journey Optimizer Developer Expert flashcards
Adobe Journey Optimizer 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.
- Journey re-entrance window
- The configured period after a profile exits a journey during which it cannot re-enter. Re-entrance is disabled entirely when the journey starts from a Read Audience activity.
- Journey states
- Draft, Published, Stopped, and Closed. Only Published accepts new profiles; Closed is terminal and cannot be republished, so a new journey must be created.
- Custom action timeout
- The maximum time a journey waits for an external custom action to respond. Exceeding it produces an activity error and the profile is dropped or errored.
- Jump activity
- A journey node that moves a profile to another point within the same journey. It cannot jump to a different journey or to a start node.
- Journey versioning
- Editing a published journey creates a new version. Profiles already in flight continue on the version they entered; new entries use the new version.
- Profile-enabled dataset
- A dataset whose schema is enabled for the unified profile. Only profile-enabled datasets contribute attributes usable in segmentation and personalization.
- Merge policy
- A rule set that resolves conflicting profile attribute values when multiple datasets contribute. The default policy uses timestamp-based precedence to pick the winning value.
- Identity graph
- The service that stitches identities across namespaces (ECID, CRM ID, email) using each record's identity map, producing a unified profile view.
- Streaming versus batch segments
- Streaming and edge segments evaluate as events arrive and can trigger journeys in near real time; batch segments evaluate on a schedule and update membership periodically.
- Segment-of-segments
- A segment defined by referencing another segment as a condition. It inherits the evaluation method of the referenced segment rather than choosing its own.
- Channel surface
- The configuration binding a channel to its subdomain, IP pool, sender identity, and credentials. A message cannot be published without an associated surface.
- Email authentication records
- SPF, DKIM, and DMARC DNS records that authenticate the sending subdomain. Missing or mismatched records reduce deliverability and can block or throttle sends.
- Push credentials
- APNs certificates or keys for iOS and FCM server keys for Android, bound to the channel surface. Expired credentials cause push send failures.
- Suppression list
- A list of addresses or identities (bounce, complaint, opt-out) checked at send time. Suppressed recipients are skipped and the skip is logged.
- Sent versus delivered
- Sent counts messages handed to the provider; delivered counts messages accepted by the recipient system. A large gap signals deliverability or provider problems.
- Decisioning evaluation order
- Eligibility first (decision rules), then ranking (static or AI), then capping. Only offers passing all three stages are returned for the placement.
- Decision policy
- The component supplying the ranking formula and frequency capping rules for a decision. It is combined with a placement and an offer collection.
- Fallback offer
- An offer returned by a placement when no eligible offer passes ranking and capping. Fallbacks are not ranked and can be empty if none is configured.
- Decision events
- Impression and click events sent to the decisioning API. They train AI ranking models and are the basis for enforcing frequency capping.
- Offer representation
- The channel-specific content (image, text, link) attached to an offer. The placement determines which representation is rendered in the message.
- Sandbox isolation
- A separation boundary for schemas, datasets, journeys, and configurations. Objects and API credentials in one sandbox cannot be used in another.
- Product profile
- A bundle of permissions assigned to users within a sandbox. A user needs the appropriate profile to publish journeys or configure channels.
- Audit log scope
- Records create, update, and delete configuration events with actor, timestamp, and object. Read operations are not captured in the audit log.
- Data usage labels
- Labels attached to schema fields (for example C1, C2, I1) that data usage policies evaluate. A policy violation blocks the requested action such as segmentation.
- Failed-records dataset
- A dataset that captures records failing schema validation or data prep mapping. Inspecting it reveals the payload and the reason for ingestion failure.
- Journey error metric
- The count of activity-level failures in a journey report. It maps to error codes identifying configuration problems such as a missing surface or identity.
- Read Audience start node
- A journey start that batch-loads profiles from an audience. It disables event-based re-entrance and runs on the audience's evaluation schedule.
- Union schema
- The merged view of all profile-enabled schemas. Segment conditions reference union schema fields, so a field must be profile-enabled to appear.
- Data prep mapping
- The transformation that maps source data into the XDM schema. Mapping errors route the record to the failed-records dataset for inspection and replay.
- Frequency capping
- A limit on how many times a profile receives a message or offer over a window. Journey-level caps apply across the journey; decisioning caps apply per offer.
- AI ranking learning phase
- The initial period of a dynamic ranking model before it has enough decision events. Rankings during this phase are less reliable and improve with event volume.
- API rate limit errors
- HTTP 429 responses returned when a sandbox exceeds its API quota. They surface as journey activity errors or ingestion failures and require throttling or retry.