在此頁面上：開始使用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.