En esta página: Busque los términos y conceptos esenciales de Adobe Journey Optimizer para que pueda navegar por la plataforma con seguridad y colaborar eficazmente con su equipo.
Esta guía de referencia define los términos esenciales que se encontrará al utilizar Adobe Journey Optimizer. Comprender estos conceptos le ayuda a navegar por la plataforma con seguridad y a colaborar eficazmente con su equipo.
¿Es su primera vez en Journey Optimizer? Comience con los cinco conceptos principales.
Para pares de términos que suenan similares y que a menudo se confunden, como Toma de decisiones vs. Administración de decisiones o Tarjetas de contenido vs. Mensajes en la aplicación, consulte Cuando los términos tienen un aspecto similar en la parte inferior de esta página.
Recorrido y términos de la campaña journey-campaign-terms
Términos de cliente y audiencia customer-audience-terms
Contenido y términos de personalización content-terms
Decisión y condiciones de la oferta decision-terms
Términos de configuración y datos data-config-terms
Conflicto y términos de priorización conflict-terms
Cuando los términos tienen un aspecto similar: guía de desambiguación disambiguation
Adobe Journey Optimizer ha crecido durante varios años, lo que significa que algunas áreas de funcionalidades comparten nombres similares. Utilice las tablas siguientes para identificar rápidamente qué capacidad se adapta a sus necesidades.
Toma de decisiones vs. administración de decisiones decisioning-vs-dm
Ambas funciones seleccionan y entregan ofertas, pero sirven para diferentes etapas del ciclo de vida del producto.
Si está usando Administración de decisiones y desea cambiar, consulte la guía de migración.
Tipos de campañas campaign-types-disambiguation
Journey Optimizer ofrece tres tipos de campañas que se activan de forma diferente y sirven para casos de uso diferentes.
Para obtener una descripción general completa de todos los tipos de campañas y cuándo utilizarlos, consulte Introducción a las campañas.
Límite de frecuencia frente a arbitraje de recorrido capping-vs-arbitration
Ambos son mecanismos establecidos por reglas en el conjunto de herramientas Conflicto y priorización, pero abordan problemas diferentes.
Tarjetas de contenido o mensajes en la aplicación content-cards-vs-in-app
Ambos canales envían mensajes dentro de una aplicación móvil o web, pero tienen diferentes modelos de procesamiento y comportamientos de persistencia.
Temas relacionados related-topics
- Descripción del funcionamiento de Journey Optimizer: vea cómo encajan los recorridos, las campañas, los perfiles y los canales en la arquitectura del producto.
- Empiece a usar las capacidades de decisión: compare la toma de decisiones y la administración de decisiones en paralelo y elija el método adecuado para su implementación.
- Introducción a recorrido: aprenda a crear experiencias secuenciales de cliente activadas por eventos paso a paso.
- Empiece a usar las campañas: comprenda los tres tipos de campañas (de acción, activadas por API y orquestadas) y cuándo utilizarlas.
- Administración de conflictos y priorización: aprenda a usar conjuntos de reglas, límites de frecuencia, puntuaciones de prioridad y horas de silencio para evitar mensajes excesivos.
- Introducción a los canales de comunicación: Examine todos los canales disponibles, sus requisitos previos y cómo configurarlos.
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)