Use Experience Fragments (XFs) and Content Fragments (CFs) created in Adobe Experience Manager (AEM) in Target activities to aid optimization and personalization.
Using Experience Fragments and Content Fragments created in AEM in Target activities let you combine the ease-of-use and power of AEM with powerful Artificial Intelligence (AI) and Machine Learning (ML) capabilities in Target to test and personalize experiences at scale.
AEM brings together all of your content and assets in a central location to fuel your personalization strategy. AEM lets you easily create content for desktops, tablets, and mobile devices in one location without writing code. There’s no need to create pages for every device. AEM automatically adjusts each experience for each device using your content.
Target lets you deliver personalized experiences at scale based on a combination of rules-based and AI-driven machine learning approaches that incorporate behavioral, contextual, and offline variables.
Experience Fragments and Content Fragments represent a huge step forward to link the content/experience creators and managers to the optimization and personalization professionals who are driving business outcomes using Target.
Consider the following as you work with AEM Experience Fragments and Content Fragments in Target:
These features require that you are an Adobe Experience Manager (AEM) customer. Ensure that you meet the requirements for each fragment type: Experience Fragment or Content Fragment.
Experience Fragments and Content Fragments are available for the following activity types:
Experience Fragments and Content Fragments are not available for the following activity types:
You can consume Experience Fragments in Target activities using the Visual Experience Composer (VEC) and the Form-Based Experience Composer.
You can consume Content Fragments in Target activities using the Form-Based Experience Composer only.
Adobe Experience Manager Experience Fragments and Content Fragments might seem similar on the surface, but each fragment type plays key roles in different use cases.
For more information about how Experience Fragments and Content Fragments are similar, different, and when and how to use each see Understand Content Fragments and Experience Fragments in the AEM Sites videos and tutorials guide.