在此页面上:查找基本的Adobe Journey Optimizer术语和概念,以便您能够放心地导航平台并与团队进行有效协作。
本参考指南定义了您在使用Adobe Journey Optimizer时将会遇到的基本术语。 了解这些概念有助于您放心地导航平台并与团队进行有效协作。
对于经常混淆的听起来相似的术语对,例如 决策与决策管理 或内容卡与应用程序内消息,请参阅本页底部的当术语看起来相似时。
历程和促销活动术语 journey-campaign-terms
客户和受众术语 customer-audience-terms
内容和个性化术语 content-terms
决策和优惠条款 decision-terms
数据和配置条款 data-config-terms
冲突和优先级术语 conflict-terms
当术语相似时:消除歧义指南 disambiguation
Adobe Journey Optimizer经历了几年的发展,这意味着一些功能领域有着相似的名字。 使用下表快速确定哪些功能符合您的需求。
决策与决策管理 decisioning-vs-dm
这两种功能都选择并提供选件,但它们服务于产品生命周期的不同阶段。
如果您当前正在使用决策管理并且想要切换,请参阅迁移指南。
营销活动类型 campaign-types-disambiguation
Journey Optimizer提供三种激活方式不同的营销活动类型,分别用于不同的用例。
有关所有营销活动类型以及何时使用每种营销活动的完整概述,请参阅营销活动入门。
频率上限与历程仲裁 capping-vs-arbitration
两者都是冲突和优先化工具集下的规则集机制,但它们解决的问题不同。
内容卡与应用程序内消息 content-cards-vs-in-app
两个渠道在移动或Web应用程序中传递消息,但它们具有不同的渲染模型和持久性行为。
相关主题 related-topics
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, SMS, and Email (product-specific)
- Decision Management: The legacy offer decisioning feature, still supported for existing implementations, supporting Email, In-App, Push, SMS, 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, SMS, Email) ≠ “Decision Management” (legacy; Email, In-App, Push, SMS, 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.