You're viewing help content for version:


Some functionality on this page requires the application of AEM

AEM and

  • The AEM Experience Fragments are exported into the default workspace of Adobe Target.
  • AEM must be integrated with Adobe Target according to the instructions under Integrating with Adobe Target.

You can export Experience Fragments, created in Adobe Experience Manager (AEM), to Adobe Target (Target). They can then be used as offers in Target activities, to test and personalize experiences at scale. 

There are three format options available for exporting an Experience Fragment to Adobe Target:

  • HTML (default): Support for web and hybrid content delivery
  • JSON: Support for headless content delivery

AEM Experience Fragments can be exported to the default workspace in Adobe Target, or to user-defined workspaces for Adobe Target. This is done via Adobe I/O, for which AEM must be integrated with Adobe Target using Adobe I/O.


The Adobe Target workspaces do not exist in Adobe Target itself. They are defined and managed in Adobe IMS (Identity Management System), then selected for usage across solutions using Adobe I/O integrations.


Adobe Target workspaces can be used to allow members of an organization (group) to create and manage offers and activities for this organization only; without giving access to other users. For example, country-specific organizations within a global concern.


For further information see also:


Various actions are required:

  1. Experience Fragments are exported from the AEM author instance, so you need to Configure the AEM Link Externalizer on the author instance to ensure that any references within the Experience Fragment are externalized for web delivery.


    For link rewriting not covered by the default, the Experience Fragment Link Rewriter Provider is available. With this, customized rules can be developed for your instance.

Add the Cloud Configuration

Before exporting a fragment you need to add the Cloud Configuration for Adobe Target to the fragment, or folder. This also enables you to:

  • specify the format option(s) to be used for the export
  • select a Target workspace as destination 

The required options can be selected in Page Properties of the required folder and/or fragment; the specification will be inherited as necessary.

  1. Navigate to the Experience Fragments console.

  2. Open Page Properties for the appropriate folder or fragment.


    If you add the cloud configuration to the Experience Fragment parent folder, the configuration is inherited by all the children.

    If you add the cloud configuration to the Experience Fragment itself, the configuration is inherited by all varations.

  3. Select the Cloud Services tab.

  4. Under Cloud Service Configuration, select Adobe Target from the drop down list.

  5. Note:

    The JSON format of an Experience Fragment offer can be customized. To do this define a customer Experience Fragment component and then annotate how to export its properties in the component Sling Model.

    See the core component:

    Under Adobe Target select:

    • the appropriate configuration
    • the required format option
    • an Adobe Target workspace

    For example, for a folder:

  6. Save & Close.

Exporting an Experience Fragment to Adobe Target


For media assets, such as images, only a reference is exported to Target. The asset itself remains stored in AEM Assets and is delivered from the AEM publish instance.

Due to this the Experience Fragment, with all related assets, needs to be published before exporting to Target.

To export an experience fragment from AEM to Target (after specifying the Cloud Configuration):

  1. Navigate to the Experience Fragment console.

  2. Select the Experience Fragment you would like to export to target.


    It has to be an Experience Fragment Web variation.

  3. Tap/click Export to Adobe Target.


    If the Experience Fragment has already been exported, select Update in Adobe Target.

  4. Tap/click Export without publishing or Publish as required.


    Selecting Publish will publish the experience fragment right away and send it to Target.

  5. Tap/click OK in the confirmation dialog.

    Your experience fragment should now be in Target.


    Various details of the export can be seen in List View of the console and Properties.


    When viewing an Experience Fragment in Adobe Target, the last modified date that is seen is the date that the fragment was last modified in AEM, not the date that the fragment was last exported to Adobe Target.


Alternatively, you can perform the export from the page editor, using comparable commands in the Page Information menu.

Using your Experience Fragments in Adobe Target

After performing the preceding tasks, the experience fragment displays on the Offers page in Target. Please have a look at the specific Target documentation to learn about what you can achieve there.


When viewing an Experience Fragment in Adobe Target, the last modified date that is seen is the date that the fragment was last modified in AEM, not the date that the fragment was last exported to Adobe Target.

Deleting an Experience Fragment already exported to Adobe Target

Deleting an Experience Fragment that has already been exported to Target may cause problems if the fragment is already being used in an offer in Target. Deleting the fragment would render the offer unusable as the fragment content is being delivered by AEM.

To avoid such situations:

  • If the Experience Fragment is not being currently used in an activity, AEM allows the user to delete the fragment without a warning message.

  • If the Experience Fragment is currently in use by an activity in Target, an error message warns the AEM user about possible consequences that deleting the fragment will have on the activity.

    The error message in AEM does not prohibit the user from (force-)deleting the Experience Fragment. If the Experience Fragment is deleted:

    • The Target offer with AEM Experience Fragment may show undesired behavior
      • The offer will likely still render, as the Experience Fragment HTML was pushed to Target
      • Any references in the Experience Fragment may not work correctly if referenced assets were deleted in AEM as well.
    • Of course, any further modifications to the Experience Fragment are impossible as the Experience Fragment does not exist anymore in AEM.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy