In questa pagina: Cerca i termini e i concetti essenziali di Adobe Journey Optimizer in modo da poter navigare nella piattaforma con sicurezza e collaborare in modo efficace con il tuo team.
Questa guida di riferimento definisce i termini essenziali che si incontrano quando si utilizza Adobe Journey Optimizer. Comprendere questi concetti consente di navigare nella piattaforma in tutta sicurezza e di collaborare in modo efficace con il team.
Nuovo utente di Journey Optimizer? Inizia con cinque concetti di base.
Per coppie di termini simili che vengono spesso confusi, ad esempio Decisioning vs Decision Management o Schede di contenuto vs Messaggi in-app, vedere Quando i termini sono simili nella parte inferiore della pagina.
Termini di percorso e campagna journey-campaign-terms
Termini cliente e pubblico customer-audience-terms
Contenuto e termini di personalizzazione content-terms
Decisione e condizioni dell’offerta decision-terms
Dati e termini di configurazione data-config-terms
Termini di conflitto e definizione delle priorità conflict-terms
Quando i termini sono simili: guida alla disambiguazione disambiguation
Adobe Journey Optimizer è cresciuto nel corso degli anni, il che significa che alcune aree funzionali condividono nomi simili. Utilizza le tabelle seguenti per identificare rapidamente quale funzionalità soddisfa le tue esigenze.
Decisioning e gestione delle decisioni decisioning-vs-dm
Entrambe le funzionalità selezionano e forniscono le offerte, ma servono diverse fasi del ciclo di vita del prodotto.
Se stai utilizzando la funzione di gestione delle decisioni e desideri effettuare il passaggio, consulta la guida alla migrazione.
Tipi di campagna campaign-types-disambiguation
Journey Optimizer offre tre tipi di campagne attivate in modo diverso e distribuite per casi d’uso distinti.
Per una panoramica completa di tutti i tipi di campagna e di quando utilizzarli, consulta Introduzione alle campagne.
Limitazione di frequenza e arbitrato di percorso capping-vs-arbitration
Entrambi sono meccanismi di set di regole nel set di strumenti per conflitti e definizione delle priorità, ma affrontano problemi diversi.
Schede di contenuto e messaggi in-app content-cards-vs-in-app
Entrambi i canali distribuiscono messaggi all’interno di un’app mobile o web, ma presentano diversi modelli di rendering e comportamenti di persistenza.
Argomenti correlati related-topics
- Comprensione del funzionamento di Journey Optimizer: scopri come percorsi, campagne, profili e canali si adattano all’architettura del prodotto.
- Introduzione alle funzionalità decisionali: confronto affiancato di decisioning e gestione delle decisioni e scelta dell’approccio corretto per l’implementazione.
- Introduzione ai percorsi: scopri come creare esperienze cliente sequenziali e attivate da eventi, passo dopo passo.
- Guida introduttiva alle campagne: scopri i tre tipi di campagne (Azione, Attivata da API, Orchestrata) e quando utilizzarle.
- Gestione dei conflitti e definizione delle priorità: scopri come utilizzare i set di regole, i limiti di frequenza, i punteggi di priorità e le ore non interattive per evitare messaggi eccessivi.
- Introduzione ai canali di comunicazione: sfoglia tutti i canali disponibili, i relativi prerequisiti e come configurarli.
This section contains structured knowledge intended to support interpretation, retrieval, and question answering related to this topic.
For complete understanding, this information should be combined with the documentation on this page. Neither source is intended to stand alone; the page describes the feature, while this section provides additional context that helps disambiguate terminology, intent, applicability, and constraints.
- TL;DR: This reference guide defines the essential Journey Optimizer terms and disambiguates pairs of similar-sounding capabilities.
Intents:
- Look up definitions for core Journey Optimizer journey, campaign, audience, content, decision, and data terms
- Disambiguate Decisioning versus Decision Management
- Disambiguate the three campaign types (Action, API-triggered, Orchestrated)
- Disambiguate Frequency capping versus journey arbitration
- Disambiguate Content Cards versus In-App messages
Glossary:
- Journey: A series of connected steps that guide customers through experiences over time, where each step occurs based on customer actions or time triggers (product-specific)
- Campaign: A coordinated marketing action delivering content to a specific audience across one or more channels; unlike journeys, campaigns execute actions simultaneously (product-specific)
- Engageable Profiles: The unique customer profiles engaged through journeys, campaigns, or decisioning activities over a rolling 12-month window; this is the key license metric, and each profile is counted once per sandbox (product-specific)
- Test Profile: Fictitious profiles used for testing and previewing messages before sending to real customers (product-specific)
- Decisioning: The current-generation decision framework, recommended for new implementations, available for Code-based Experience, Push, Mobile message, and Email (product-specific)
- Decision Management: The legacy offer decisioning feature, still supported for existing implementations, supporting Email, In-App, Push, Mobile message, and Direct mail (product-specific)
- Rule set: A named group of business rules applied to journeys and campaigns, combining frequency capping, journey entry limits, and quiet hours into a single reusable policy (product-specific)
Guardrails:
- Many foundational concepts (real-time customer profiles, sandboxes, schemas, datasets) are Adobe Experience Platform concepts, not Journey Optimizer-specific ones.
- Engageable Profiles is measured over a rolling 12-month window and each profile is counted once per sandbox regardless of how many journeys or campaigns it enters.
- Decisioning is recommended for all new implementations; Decision Management is legacy and no longer recommended for new implementations.
- Adobe Journey Optimizer and Journey Optimizer B2B Edition are two separate products; this documentation covers Adobe Journey Optimizer (B2C customer journeys).
Terminology:
- Canonical name: Decisioning — Acronym: n/a — variants: current-generation decision framework
- Synonyms: “Action campaigns” = “Scheduled campaigns”
- Do not confuse: “Decisioning” (current, recommended; Code-based Experience, Push, Mobile message, Email) ≠ “Decision Management” (legacy; Email, In-App, Push, Mobile message, Direct mail)
- Do not confuse: “Frequency capping” (a profile receives too many messages over time) ≠ “Journey arbitration” (a profile qualifies for multiple journeys simultaneously)
- Do not confuse: “Content Cards” (persistent cards embedded in the app UI) ≠ “In-App messages” (transient overlays, banners, or modals)
- Do not confuse: “Action campaigns” (scheduled batch sends) ≠ “API-triggered campaigns” (real-time, event-driven) ≠ “Orchestrated campaigns” (complex, multi-step workflows with a visual canvas)
FAQ:
- Q: Should new implementations use Decisioning or Decision Management? — Decisioning is the current-generation framework recommended for all new implementations; Decision Management is legacy and still supported but no longer recommended for new implementations.
- Q: How is a journey different from a campaign? — A journey guides customers through connected steps over time based on actions or time triggers, whereas campaigns execute actions simultaneously to a specific audience across one or more channels.
- Q: What is the key license metric for Journey Optimizer? — Engageable Profiles, the unique profiles engaged over a rolling 12-month window, counted once per sandbox.
- Q: What are the three campaign types? — Action campaigns (scheduled batch sends), API-triggered campaigns (real-time, event-driven messaging via API), and Orchestrated campaigns (complex, multi-step workflows with a visual canvas).
- Q: Are real-time customer profiles, sandboxes, and schemas defined here? — No. Those are Adobe Experience Platform concepts; refer to the Adobe Experience Platform glossary for their definitions.
Personas:
- admin: Can configure channel settings, including sender details, subdomain, IP pool, and message type. Can manage sandboxes, where data, audiences, journeys, campaigns, and settings exist independently. The page states that sending to suppressed addresses is blocked to protect deliverability and sender reputation. Where: “Data & configuration terms”.
- developer: Can trigger API-triggered campaigns through an external API call for real-time, event-driven messaging such as order confirmations or password resets. Can personalize these campaigns using profile attributes plus API payload context. The page states that API-triggered campaigns are activated through an external API call. Where: “Campaign types”.
- marketer: Can build journeys made of connected steps that guide customers through experiences over time. Can create Action campaigns, API-triggered campaigns, or Orchestrated campaigns to deliver content across one or more channels. The page states that campaigns execute actions simultaneously to a specific audience, unlike journeys. Where: “Journey & campaign terms”.
Onboarding:
- Level: Beginner
- First minimal step: Start with the five core concepts.
- Success check: You can quickly identify which capability fits your needs using the disambiguation tables below.
- Previous: See how journeys, campaigns, profiles, and channels fit together in the product architecture: Understanding Journey Optimizer (start/understanding-ajo.md)
- Next: Compare Decisioning and Decision Management side by side and choose the right approach for your implementation: Get started with Journey Optimizer decision capabilities (experience-decisioning/gs-decision.md); Learn how to build event-triggered, sequential customer experiences step by step: Get started with journeys (building-journeys/journey.md)