AEM experience fragments

Use experience fragments created in Adobe Experience Manager (AEM) in Target activities to aid optimization or personalization.

NOTE

This feature requires that you are an Adobe Experience Manager (AEM) customer. For more information, see Requirements below.

Using experience fragments created in AEM in Target activities lets 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 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. With Target, you can easily set up and run A/B Test and Multivariate (MVT) activities to determine the best offers, content, and experiences.

Experience 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.

Requirements

You must be provisioned with the experience fragments functionality within Target. In addition, you must be using AEM as a Cloud Service or AEM 6.4 (or later). Your account representative can help ensure that you meet the requirements to use this feature:

  • Adobe Experience Manager as a Cloud Service
  • Adobe Experience Manager 6.5.
  • Adobe Experience Manager 6.4.
  • Adobe Target Standard or Adobe Target Premium account.
NOTE

Adobe Experience Manager 6.3 and 6.4 have reached end-of-life and are no longer supported (except for customers who purchased extended support).

Contact Adobe Target Customer Care to enable the integration and to provide you with authentication details.

Creating and configuring experience fragments in AEM

In order to use AEM experience fragments in Target, you must perform the following steps:

Step 1: Integrate AEM with Target

For more information, see:

Step 2: Create the experience fragment

Experience fragments are created in AEM. For more information, see:

Step 3: Configure AEM to share the experience fragment with Target

  1. From within AEM, select the desired experience fragment or its containing folder, then click Properties.

  2. Click the Cloud Services tab, then from the Cloud Service Configuration drop-down list, select Adobe Target.

    NOTE

    The previous step assumes that someone in your organization has created the Adobe Target configuration.

  3. Click Save & Close.

Step 4: Publish the experience fragment and export it into Target

Depending on your AEM version, see the following links for step-by-step instructions:

Using experience fragments in Target activities

After performing the preceding tasks, the experience fragment displays on the Offers page in Target.

NOTE
  • Target currently looks for experience fragments to import every ten minutes. The imported experience fragment should be available in Target within ten minutes, but this time frame should shorten going forward.

  • The experience fragment is imported into Target as an HTML offer. That experience fragment “primary” version remains in AEM. You cannot edit the experience fragment in Target.

You can hover over an experience fragment in the list, then click the View icon View icon to see additional information about the experience fragment, including its public offer delivery URL and its AEM path.

You can consume experience fragments in Target activities using the Visual Experience Composer (VEC) or the Form-Based Experience Composer.

NOTE

To fully use the Target AI and ML functionality, you can select Auto-Allocate or Auto-Target while creating an A/B Test.

Experience fragments are not supported in Recommendations activities. However, to use experience fragments for recommendations you can create an A/B Test activity (including Auto-Allocate and Auto-Target) or an Experience Targeting (XT) activity and include recommendations as an offer.

To consume experience fragments using the VEC:

NOTE

Experience fragments exported as JSON in Target cannot be used in activities created using the VEC; only HTML experience fragments are supported in VEC-based activities. If you would like to use JSON experience fragments, use them in activities created using the Form-based experience composer.

  1. In Target, while creating or editing an experience in the Visual Experience Composer, click the location on the page where you want to insert AEM content, then select the desired option to display the Choose an Experience Fragment list.

    • Insert Before
    • Insert After
    • Swap with Experience Fragment

    The Experience Fragment list displays the content created in AEM that is now natively available from within Target.

    NOTE

    The Swap with Experience Fragment option is not available for images. If you want to use this option with an image, click the container element that contains the desired image.

  2. Select the desired experience fragment, then click Done.

  3. Finish configuring the activity.

    For more information about configuring the various activity types, see the following topics:

To consume experience fragments using the Form-based Experience Composer:

  1. In Target, while creating or editing an experience in the Form-Based Experience Composer, select the location on the page where you want to insert AEM content, then select Change Experience Fragment to display the Choose an Experience Fragment list.

    The Experience Fragment list displays the content created in AEM that is now natively available from within Target.

  2. Select the desired experience fragment, then click Save.

  3. Finish configuring the activity.

Considerations

  • Target currently looks for experience fragments to import every ten minutes. The imported experience fragment should be available in Target within ten minutes, but this time frame should shorten going forward.
  • The experience fragment is imported into Target as an HTML or JSON offer. The experience fragment “primary” version remains in AEM. You cannot edit the experience fragment in Target.
  • You cannot create experience fragments using Adobe I/O. Create experience fragments using AEM, as explained above.
  • If you update your experience fragment in AEM, the experience fragment must be published and exported to Target again so Target can use the latest changes.

Removing ClientLibs and extraneous HTML from Experience Fragments exported to Target

When using experience fragment offers with Target on a page delivered by AEM, the targeted page already contains all of the necessary Client Libraries. Note also that extraneous HTML elements in the offer are also not necessary.

Sometimes entire HTML pages wrap the experience fragment and cause problems. Ensure that the experience fragment is a small piece of HTML and not a full HTML page with HTML, HEAD, BODY, and so forth.

For more information, see the following blog post: AEM 6.5: Removing ClientLibs from Experience Fragments exported to Target.

Training video: Using AEM experience fragments with Adobe Target

The following video shows you how to set up and use experience fragments:

NOTE

The AEM deeplink feature discussed at 4:54 has been removed.

For more detailed information, see Using Experience Fragments with Adobe Target on the AEM Sites Videos and Tutorials page.

On this page