Exporting Experience Fragments to Adobe Target (2023)

You can exportexperience fragments, based on Adobe Experience Manager as a Cloud Service (AEM), to Adobe Target (Target). They can then be used as offers for Target activities to test and customize experiences at scale.

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

• HTML (default): Support for web and hybrid content delivery
• JSON: Support for serving content without headers
• HTML und JSON

To prepare your instance to export AEM Experience Fragments to Adobe Target, you must:

• Integration mit Adobe Target
• Add cloud settings
• Add legacy settings

After that you can:

• Export an Experience Fragment to Adobe Target
• Use your experience snippets in Adobe Target
• And alsoDelete an Experience Fragment that has already been exported to Adobe Target

Experience Fragments can be exported to the default Adobe Target workspace or Adobe Target custom workspaces.

previous requirements

Several actions are required:

1. You need tointegrate AEM with Adobe Target.

2. Experience Fragments are exported from the AEM author instance, so you must do thisConfigure AEM Link Externalizeron the author instance to ensure that all references within the experience fragment are externalized for web delivery.

   USE

   For link rewriting not covered by default, theExperience the snippet link rewrite provideris available. This allows custom rules to be developed for your instance.

Add cloud settings

Before exporting a snippet, you need to add theCloud-KonfigurationforAdobe targetto the fragment or folder. This also allows you to:

• Specify the format options to use for the export
• Select a target workspace as the target
• Select an outsourcer domain to rewrite references in the experience snippet (optional)

The desired options can be selected inpage propertiesthe desired folder and/or fragment; the specification is inherited as needed.

1. Navigate toexperience fragmentsConsole.

2. Openpage propertiesfor the appropriate folder or fragment.

   USE

   (Video) Part 1 - AEM (v6.4) and Target: Experience Targeting

   If you add the cloud settings to the Experience Fragment's parent folder, all children inherit the settings.

   If you add cloud settings to the same Experience Fragment, all variations inherit the settings.

3. ChooseCloud-ServicesEyelash.

4. LowCloud-Service-Konfiguration, chooseAdobe targetfrom the drop-down list.

   USE

   The JSON format of an Experience Fragment offer can be customized. To do this, define a Customer Experience Fragment component, and then consider how to export its properties to the component's Sling model.

   Check out the core component:Core Components - Experience Fragments

   See Also

   Exportación de fragmentos de experiencia a Adobe Target¿Utiliza Fragmentos de experiencia de Adobe Experience Manager (AEM)?

5. LowAdobe targetchoose:

   • the right configuration
   • the required format option
   • an Adobe Target workspace
   • possibly the domain of the client

   CAUTION

   The outsourcer domain is optional.

   An AEM externalizer is configured when you want the exported content to point to a specific onePostDomain. See for detailsAEM Link Externalizer-Konfiguration.

   Also note that outsourcer domains are only relevant to the content of the experience fragment that is sent to Target and not to metadata such as view offer content.

   For example for a folder:

   

6. save near.

Add legacy settings

AfterAdd cloud configurationTo use Launch by Adobe for the initial integration of AEM with Adobe Target, you must also manually integrate with Adobe Target using a legacy configuration.

Creating a target cloud configuration

To allow AEM to interact with Adobe Target, create a Target cloud configuration. To create the configuration, provide your Adobe Target client code and user credentials.

The target cloud configuration is only created once since you can associate the configuration with multiple AEM campaigns. If you have multiple Adobe Target customer codes, create a configuration for each customer code.

You can configure cloud settings to sync Adobe Target segments. If you enable sync, segments will be imported from Target in the background as soon as the cloud settings are saved.

Use the following procedure to create a target cloud configuration in AEM:

1. navigate toLegacy Cloud ServicesBy theAEM-Logo>Tool>Cloud-Services>Legacy Cloud Services.
   For example: (http://localhost:4502/libs/cq/core/content/tools/cloudservices.html)

   IsAdobe Cloud experienceThe overview page opens.

2. insideAdobe targetsection, clickconfigure now.

   (Video) Create Experience Fragments And Authoring them in AEM 6.4

3. insidecreate configurationDialog:

   1. Enter the settingstitle.
   2. ChooseAdobe target configurationPresentation.
   3. ClickCreate.

Now you can select the new configuration to edit it.

1. The editing dialog opens.

   

2. insideAdobe target configurationSpecify values ​​for these properties in the dialog box.

   • authentication: Default is IMS (user credentials are obsolete)

   • customer number: the customer code of the target account

   • ID card of the prisoner: the identification of the tenant

   • IMS configuration: Select the required configuration from the drop-down list

   • API-Typ: Default is REST (XML is deprecated)

   • A4T Analytics Cloud-Konfiguration: Select the Analytics cloud settings used for target activity metrics and goals. You need this if you're using Adobe Analytics as a reporting source when targeting content.

   • Use precise targeting:By default, this check box is checked. When this option is selected, the cloud service configuration waits for the context to load before loading the content. See the note below.

   • Sync segments from Adobe Target:Select this option to download segments defined in Target for use in AEM. You should select this option when the API type property is REST, since inline segments are not supported and you must always use target segments. (Note that the AEM term "segment" corresponds to the audience "audience".)

   • Customer Library:this is AT.js by default (mbox.js is deprecated)

     USE

     The target library file,AT.JS, is a new implementation library for Adobe Target, designed for both typical web deployments and single-page applications.

     mbox.js is deprecated and will be removed at a later date.

     Adobe recommends using 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 delivery options for single page apps
     • AT.js contains the components that were included in target.js, so there is no longer a call to target.js

     You can choose AT.js or mbox.js inclient librarydrop down menu.

   • Use the tag management system to deploy the client library- Select this option to use the Adobe Launch client library or another tag management system (or DTM that is deprecated).

   • AT.js custom: Navigate to upload your custom AT.js. Leave it blank to use the default library.

     USE

     When you sign up for the Adobe Target setup wizard, precise targeting is enabled by default.

     Precise targeting means that the cloud service configuration waits for the context to load before loading the content. As a result, in terms of performance, precise targeting can result in a delay of a few milliseconds before content is loaded.

     Precise targeting is always enabled on the author instance. However, on the publish instance, you can disable precise targeting globally by unchecking the box next to "Precise targeting" in the cloud service settings (http://localhost:4502/etc/cloudservices.html). You can also toggle precise targeting on and off for individual components, independently of your settings in the Cloud Service Settings.

     (Video) AEM Experience Fragments vs Content Fragments

     If you havevonIf you have created target components and change these settings, your changes do not affect these components. You must make any changes to these components directly.

3. ClickConnect to Adobe Targetto initialize the connection with Target. If the connection is successful, the messagesuccessful connectionis displayed. ClickOKin the message and thenOKim Dialog.

Add a target frame

After configuring the target cloud configuration, add a target framework. The framework identifies the default parameters that are sent to Adobe Target from those available.ContextHubTarget components use the parameters to determine which segments apply to the current context.

You can create multiple frames for a single target configuration. Multiple frameworks are useful when you need to send different sets of parameters to Target for different areas of your website. Create a frame for each set of parameters you need to send. Map the appropriate framework to each section of your website. Please note that a website can only use one frame at a time.

1. On the Target Settings page, click the+(plus sign) next to Available settings.

2. In the Create Frame dialog box, specify atitle, ChooseAdobe target milestoneand clickCreate.

   The frame page opens. Sidekick provides components that present information from theContextHubthat you can depict

3. Drag the client context component that represents the data you want to use for mapping onto the drop target. Alternatively, pull theContextHub-Storeframe component.

   USE

   When mapping, parameters are passed to an mbox via simple strings. You cannot allocate arrays from ContextHub.

   For example to useprofile dataDraw your website visitors to drive your targeting campaignprofile datacomponent on the page. The profile data variables available for mapping to target parameters are displayed.

4. Choose the variables that you want to make visible to the Adobe Target system by selecting thesharecheck boxes in the appropriate columns.

   USE

   Parameter synchronization is one-way: from AEM to Adobe Target.

Your frame will be created. To replicate the framework to the publish instance, use theActivate framechoice of partner.

Export an Experience Fragment to Adobe Target

To export an Experience Fragment from AEM to Target (after specifying cloud settings):

1. Go to the Experience Fragment Console.

2. Select the experience fragment that you want to export to the destination.

   USE

   It must be a variation of Experience Fragment Web.

3. tap/clickExport to Adobe Target.

   USE

   If the experience fragment has already been exported, selectUpdate bei Adobe Target.

   (Video) Different personalization techniques with Adobe Target with Khanjan Saraiya

4. tap/clickExport without publicationÖPostas necessary.

   USE

   choosePostimmediately posts the experience snippet and sends it to Target.

5. tap/clickOKin the confirmation dialog.

   Your experience shard should now be in Target.

   USE

   diverse Detailsof the export can be viewed inlist viewfrom the console andCharacteristics.

   USE

   When viewing an Experience Fragment in Adobe Target, theLast updatedThe date shown is the date the snippet was last modified in AEM, not the date the snippet was last exported to Adobe Target.

Using your Experience Fragments in Adobe Target

After completing the above tasks, the experience snippet will appear on the Deals page in Target. Please take a look at thosedestination-specific documentationto find out what you can achieve there.

Delete an Experience Fragment that has already been exported to Adobe Target

Deleting an Experience Fragment that has already been exported to Target may cause issues if the fragment is already being used in an offer at Target. Removing the snippet would render the offer unusable as AEM serves the content of the snippet.

To avoid such situations:

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

• If the experience fragment is currently being used by an activity in Target, an error message will warn the AEM user of the possible consequences of removing the fragment from the activity.

  The error message in AEM does not prohibit the user from deleting (forcing) the Experience Fragment. When the Experience Fragment is removed:

  • Target offers with AEM Experience Fragment may exhibit undesirable behavior

    • The offer may still appear because the HTML Experience Fragment was sent to Target
    • References in the Experience Fragment may not work correctly if the referenced resources have also been deleted in AEM.

  • Of course, further modification of the experience shard is not possible because the experience shard no longer exists in AEM.