여정 시작 jo-general-principle

여정과 캠페인의 차이는 무엇인가요?

Adobe Journey Optimizer에서는 다음 세 가지 방법을 제공합니다.

• 여정: 각 프로필이 각자의 속도로 단계를 이동하는 실시간 오케스트레이션. 조건부 논리(예: 온보딩, 장바구니 포기)를 사용하는 행동 기반의 여러 단계 경험에 가장 적합합니다.

• 캠페인(액션 및 API 트리거): 단순히 메시지를 대상자에게 전달하며, 예약한 일정에 따라서나 API 트리거를 통해 모든 프로필에 동시에 실행됩니다. 프로모션 캠페인, 뉴스레터, 트랜잭션 메시지에 적합합니다.

• 오케스트레이션된 캠페인: 관계형 데이터(프로필 + 제품/매장/예약)를 사용한 복잡한 세분화를 포함하는 다단계 배치 워크플로입니다. 모든 프로필이 한꺼번에 처리되며 정확한 사전 전송 수를 파악할 수 있습니다. 여러 엔터티의 데이터가 필요한 시즌 프로모션, 제품 출시, 캠페인에 적합합니다.

주요 차이점: 여정은 실시간 액션을 위해 개별 고객 상태를 유지합니다. 액션 및 API 트리거 캠페인은 간단한 메시지를 일괄적으로 전달합니다. 오케스트레이션된 캠페인은 다중 엔티티 세분화 기능을 갖춘 배치 워크플로 캔버스를 제공합니다.

오케스트레이션된 캠페인에 대해 알아보기

어떤 여정 유형을 사용해야 합니까?

트리거 메커니즘과 사용 사례를 기준으로 단일 이벤트 여정, 대상자 읽기 이벤트 가이드, 대상자 자격 조건 및 비즈니스 이벤트 규칙 중에서 선택하려면 결정 가이드 또는 비교 테이블을 사용하십시오.

라이브 여정을 편집할 수 있나요?

일부 제한된 요소(이름, 메시지 콘텐츠)를 편집할 수 있지만 구조를 변경하려면 새 버전을 만들어야 합니다. 여정 버전에 대해 알아보기

AI Knowledge Reference

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 page is the getting-started hub for Adobe Journey Optimizer journeys, explaining what journeys are, the four journey types, the six-step creation workflow, real-world use cases, and links to advanced capabilities.

Intents:

• Understand what journeys are and how they differ from campaigns and orchestrated campaigns
• Choose the right journey type (Unitary, Read Audience, Audience Qualification, or Business event) for a use case
• Follow the six-step journey creation workflow: Plan, Design, Test, Publish, Monitor, Optimize
• Use Simulation, Test mode, or Dry run to validate a journey before going live
• Publish a journey and monitor performance through reports and alerts
• Explore advanced capabilities such as expressions, timezone management, copy to sandbox, and throughput control

Glossary:

• Journey: An automated, multistep customer experience that orchestrates personalized interactions across channels in response to customer behavior, business events, or scheduled campaigns. (product-specific)
• Journey designer: The visual drag-and-drop canvas in AJO used to build and configure journey flows without writing code. (product-specific)
• Test mode: A journey validation mode that uses persistent Adobe Experience Platform test profiles (explicitly flagged as test profiles) to traverse a draft journey before it is published. (product-specific)
• Dry run: A special publication mode that executes the journey against real production data without sending communications or updating profiles. (product-specific)
• Simulation: A validation mode that uses temporary simulated users, manually created or auto-generated; simulated users do not persist in Adobe Experience Platform. (product-specific)
• Orchestrated campaigns: Multi-step batch workflows in AJO that use relational data (profiles + products/stores/bookings) and process all profiles together with exact pre-send counts. (product-specific)

Guardrails:

• Live journeys cannot be structurally edited; changes require creating a new version
• Test mode and dry run must be used before publishing to catch issues

Terminology:

• Canonical name: Journey — Acronym: none — variants: customer journey, AJO journey
• Synonyms: “journey designer” = “canvas” = “journey canvas”
• Do not confuse: “Journey” ≠ “Campaign” — Journeys maintain individual customer state for real-time, multi-step behavior-driven experiences; Campaigns deliver messages in batch to audiences on a schedule or via API trigger
• Do not confuse: “Simulation” ≠ “Test mode” ≠ “Dry run” — Simulation uses temporary simulated users; Test mode uses persistent AEP test profiles in a draft journey; Dry run executes against real production data without contacting customers or updating profiles

FAQ:

• Q: What is the difference between a journey and a campaign in Journey Optimizer? — Journeys provide 1:1 real-time orchestration where each profile progresses at its own pace through conditional logic; Campaigns deliver messages simultaneously to an audience on a schedule or via API trigger; Orchestrated campaigns are batch canvas workflows for complex multi-entity segmentation.
• Q: Can I edit a live journey? — Limited elements such as name and message content can be edited; structural changes require creating a new version of the journey.
• Q: What are the steps to build a journey? — The six-step workflow is: Plan, Design in the canvas, Test (test mode or dry run), Publish, Monitor performance, and Optimize/iterate.
• Q: How do I validate a journey without contacting real customers? — Use Simulation (temporary simulated users — note this does send real messages, but only to the execution addresses configured on those simulated users), Test mode (persistent AEP test profiles — note this does send real messages to those test profiles’ inboxes), or Dry run (real production data, action nodes bypassed, no messages sent). Dry run profiles count toward Engageable Profiles and live journey quota. See Choose a validation method for a full comparison.
• Q: What journey type should I use for a welcome email triggered by a subscription? — Use a Unitary journey, which is triggered by a specific individual event such as a subscription sign-up.