在此页面上：开始使用Adobe Experience Manager内容片段，并了解其创作和发布生命周期如何确定Journey Optimizer中可用的片段。
通过将 Adobe Experience Manager as a Cloud Service 和 Adobe Experience Manager Managed Service 与Adobe Journey Optimizer集成，您可以在历程和营销活动中使用AEM内容片段。 对于Adobe Experience Manager Managed Service，集成支持 AEM长期支持(LTS) SP2 上的 创作 和 发布 层；此版本中不提供来自Adobe Experience Manager的实时更新。 请联系您的Adobe Managed Services代表进行实例设置，然后配置Adobe Experience Manager存储库访问权限以添加您的Managed Services存储库。
要了解有关AEM内容片段的更多信息，请参阅Experience Manager文档中的使用内容片段。
内容片段生命周期
内容片段根据它们所在的Adobe Experience Manager层而遵循不同的生命周期阶段。 请参阅Adobe Experience Manager文档以了解详情
内容在 创作层 中创建和管理，其中片段可以具有状态，如“新建”、“草稿”、“已发布”、“已修改”或“未发布”。 这些状态仅适用于创作层，并且支持内容创建和审阅。
发布内容片段时，会在 发布层 上创建一个副本，并通过未经身份验证的公共端点公开。 对于Adobe Experience Manager as a Cloud Service，Journey Optimizer支持与 创作层 和 发布层 的集成。
因此，Journey Optimizer只会显示已发布或已修改的内容片段，并且始终使用最新发布的版本。 在重新发布内容片段之前，发布后所做的任何更改都不会反映在Journey Optimizer中。
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 introduces Adobe Experience Manager Content Fragments in Journey Optimizer and explains how their author and publish lifecycle determines which fragments are available for journeys and campaigns.
Intents:
- Understand how Adobe Experience Manager Content Fragments become available in journeys and campaigns
- Learn the Content Fragment lifecycle across the Author and Publish tiers
- Identify which Content Fragment statuses Journey Optimizer surfaces
- Understand support for Adobe Experience Manager Managed Service and as a Cloud Service
Glossary:
- Content Fragment: Adobe Experience Manager content used in Journey Optimizer journeys and campaigns (product-specific)
- Author tier: The tier where content is created and managed, where fragments can have statuses such as New, Draft, Published, Modified, or Unpublished (product-specific)
- Publish tier: The tier where a copy of a published Content Fragment is created and exposed through a public, unauthenticated endpoint (product-specific)
Guardrails:
- For Adobe Experience Manager Managed Service, integration supports Author and Publish tiers on AEM Long Term Support (LTS) SP2; real-time updates from Adobe Experience Manager are not available in this release.
- For Healthcare customers, the integration is enabled only upon licensing the Journey Optimizer Healthcare Shield and Adobe Experience Manager Enhanced Security add-on offerings.
- Journey Optimizer surfaces only Published or Modified Content Fragments and always uses the latest published version.
- Changes made after publication are not reflected in Journey Optimizer until the Content Fragment is republished.
- The New, Draft, Published, Modified, and Unpublished statuses apply only on the Author tier.
Terminology:
- Canonical name: Adobe Experience Manager Content Fragment — Acronym: AEM Content Fragment — variants: Content Fragment, AEM CF
- Synonyms: “as a Cloud Service” = “Adobe Experience Manager as a Cloud Service”
- Do not confuse: “Author tier” (content creation and review, statuses New/Draft/Published/Modified/Unpublished) ≠ “Publish tier” (public, unauthenticated endpoint copy)
FAQ:
- Q: Which Content Fragments appear in Journey Optimizer? — Only Published or Modified Content Fragments, and Journey Optimizer always uses the latest published version.
- Q: Are edits made after publication reflected automatically? — No; changes made after publication are not reflected in Journey Optimizer until the Content Fragment is republished.
- Q: What does Managed Service integration support? — Author and Publish tiers on AEM Long Term Support (LTS) SP2; real-time updates are not available in this release.
- Q: What statuses can a fragment have on the Author tier? — New, Draft, Published, Modified, or Unpublished; these statuses apply only on the Author tier.