Exporting Experience Fragments to Adobe Target exporting-experience-fragments-to-adobe-target
- 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 as a Cloud Service (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 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
- HTML & JSON
To prepare your instance for exporting AEM Experience Fragments to Adobe Target you need to:
After that you can:
Experience Fragments can be exported to the default workspace in Adobe Target, or to user-defined workspaces for Adobe Target.
Prerequisites prerequisites
Various actions are required:
-
You have to integrate AEM with Adobe Target.
-
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.
note note NOTE 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 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
- select an externalizer domain for rewriting references in the Experience Fragment (optional)
The required options can be selected in Page Properties of the required folder, or fragment, or both; the specification is inherited as necessary.
-
Navigate to the Experience Fragments console.
-
Open Page Properties for the appropriate folder or fragment.
note note NOTE 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. -
Select the Cloud Services tab.
-
Under Cloud Service Configuration, select Adobe Target from the drop-down list.
note note 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: Core Components - Experience Fragments -
Under Adobe Target select:
- the appropriate configuration
- the required format option
- an Adobe Target workspace
- if necessary - the externalizer domain
note caution CAUTION The externalizer domain is optional. An AEM externalizer is configured when you want the exported content to point to a specific publish domain. For more details see Configuring the AEM Link Externalizer. Also note that Externalizer Domains are only relevant to the content of the Experience Fragment that is sent to Target, and not metadata such as View Offer Content. For example, for a folder:
-
Save & Close.
Add the Legacy Configuration add-the-legacy-configuration
After adding the Cloud Configuration to use Launch by Adobe, to initially integrate AEM with Adobe Target, you also need to manually integrate with Adobe Target using a legacy configuration.
Creating a Target Cloud Configuration creating-a-target-cloud-configuration
To enable AEM to interact with Adobe Target, create a Target cloud configuration. To create the configuration, you provide the Adobe Target client code and user credentials.
You create the Target cloud configuration only once because you can associate the configuration with multiple AEM campaigns. If you have several Adobe Target client codes, create one configuration for each client code.
You can configure the cloud configuration to synchronize segments from Adobe Target. If you enable synchronization, segments are imported from Target in the background as soon as the cloud configuration is saved.
Use the following procedure to create a Target cloud configuration in AEM:
-
Navigate to Legacy Cloud Services via the AEM logo > Tools > Cloud Services > Legacy Cloud Services.
For example: (http://localhost:4502/libs/cq/core/content/tools/cloudservices.html)The Adobe Experience Cloud overview page opens.
-
In the Adobe Target section, click Configure Now.
-
In the Create Configuration dialog:
- Give the configuration a Title.
- Select the Adobe Target Configuration template.
- Click Create.
You can now select the new configuration for editing.
-
The edit dialog opens.
-
In the Adobe Target Settings dialog, provide values for these properties.
-
Authentication: this defaults to IMS (User Credentials is deprecated)
-
Client Code: the Target account Client Code
-
Tenant ID: the tenant ID
-
IMS Configuration: select the required configuration from the drop-down list
-
API Type: defaults to REST (XML is deprecated)
-
A4T Analytics Cloud Configuration: Select the Analytics cloud configuration that is used for target activity goals and metrics. You need this if you are using Adobe Analytics as the reporting source when targeting content.
-
Use accurate targeting: By default this check box is selected. If selected, the cloud service configuration will wait for the context to load before loading content. See note that follows.
-
Synchronize Segments from Adobe Target: Select this option to download segments that are defined in Target to use them in AEM. Select this option when the API Type property is REST, because inline segments are not supported and you always need to use segments from Target. (The AEM term of ‘segment’ is equivalent to the Target ‘audience’.)
-
Client library: this defaults to AT.js (mbox.js is deprecated)
note note NOTE The Target Library file, AT.JS, is a new implementation library for Adobe Target that is designed for both typical web implementations and single-page applications. mbox.js has been deprecated and will be removed at a later stage. Adobe recommends that you use AT.js instead of mbox.js as the client library. AT.js offers several improvements over the mbox.js library: - Improved page load times for web implementations
- Improved security
- Better implementation options for single-page applications
- AT.js contains the components that were included in target.js, so there is no longer a call to target.js
You can select AT.js or mbox.js in the Client library drop-down menu. -
Use Tag Management System to deliver client library - Select this option to use the client library from Adobe Launch or another tag management system (or DTM, which is deprecated).
-
Custom AT.js: Browse to upload your custom AT.js. Leave blank to use the default library.
note note NOTE By default when you opt into the Adobe Target configuration wizard, Accurate Targeting is enabled. Accurate targeting means that the cloud service configuration waits for the context to load before loading content. As a result, in terms of performance, accurate targeting may create a few millisecond delay before loading content. Accurate targeting is always enabled on the author instance. However, on the publish instance you can opt to turn accurate targeting off globally by clearing the check mark next to Accurate Targeting in the cloud service configuration (http://localhost:4502/etc/cloudservices.html). You can also still turn accurate targeting on and off for individual components regardless of your setting in the cloud service configuration. If you have already created targeted components and you change this setting, your changes do not affect those components. You must make any changes to those component directly.
-
-
Click Connect to Adobe Target to initialize the connection with Target. If the connection is successful, the message Connection successful is displayed. Click OK on the message and then OK on the dialog.
Adding a Target Framework adding-a-target-framework
After you configure the Target cloud configuration, add a Target framework. The framework identifies the default parameters that are sent to Adobe Target from the available ContextHub components. Target uses the parameters to determine the segments that apply to the current context.
You can create multiple frameworks for a single Target configuration. Multiple frameworks are useful when you need to send a different set of parameters to Target for different sections of your website. Create a framework for each set of parameters that you need to send. Associate each section of your website with the appropriate framework. Note t*hat a web page can use only one framework at a time.
-
On your Target configuration page, click the + (plus sign) next to Available Configurations.
-
In the Create Framework dialog, specify a Title, select the Adobe Target Framework, and click Create.
The framework page opens. Sidekick provides components that represent information from the ContextHub that you can map.
-
Drag the Client Context component that represents the data that you want to use for mapping to the drop target. Alternatively, drag the ContextHub Store component to the framework.
note note NOTE When mapping, parameters are passed to an mbox via simple strings. You cannot map arrays from ContextHub. For example, to use Profile Data about your site vistors to control your Target campaign, drag the Profile Data component to the page. The profile data variables that are available for mapping to Target parameters appear.
-
Select the variables that you want to make visible to the Adobe Target system by selecting the Share checkbox in the appropriate columns.
note note NOTE Synchronizing parameters is one way only - from AEM to Adobe Target.
Your framework is created. To replicate the framework to the publish instance, use the Activate Framework option from the sidekick.
Exporting an Experience Fragment to Adobe Target exporting-an-experience-fragment-to-adobe-target
To export an experience fragment from AEM to Target (after specifying the Cloud Configuration):
-
Navigate to the Experience Fragment console.
-
Select the Experience Fragment you would like to export to target.
note note NOTE It has to be an Experience Fragment Web variation. -
Select Export to Adobe Target.
note note NOTE If the Experience Fragment has already been exported, select Update in Adobe Target. -
Select Export without publishing or Publish as required.
note note NOTE Selecting Publish will publish the experience fragment right away and send it to Target. -
Select OK in the confirmation dialog.
Your experience fragment should now be in Target.
note note NOTE Various details of the export can be seen in List View of the console and Properties. note note NOTE 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.
Using your Experience Fragments in Adobe Target using-your-experience-fragments-in-adobe-target
After performing the preceding tasks, the experience fragment displays on the Offers page in Target. See specific Target documentation to learn about what you can achieve there.
Deleting an Experience Fragment already 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.
-