Talks about how to Integrate AEM with Adobe Target Via Adobe Launch

Article summary

Summary

Discusses how to integrate AEM with Adobe Target Via Adobe Launch

Its the great community members that help the overall AEM community and drives the success of AEM Developers using Adobe Experience Manager.

Digital Marketing Solution(s) Adobe Experience Manager 6.4
Audience Developer, Administrator
Required Skills AEM Authoring, Adobe Launch Authoring, Adobe IO console, Adobe Target
Version 6.4

Introduction

This article is part 2 of integrating AEM with other experience cloud solutions. Here, we will integrate AEM with Adobe Target via Adobe Launch.

For details on the integration of AEM with Adobe Launch, you can have a look at Integrate AEM with Adobe Launch Via Adobe I/O

AEM 6.4 offers an out of the box integration between AEM 6.4 and Adobe Launch, which allows AEM administrators to easily configure AEM 6.4 and Adobe Launch via an easy to use interface, which reduces the level of effort and the number of errors when configuring these two tools. And just by adding Adobe Target extension to Adobe launch will help us use all features of Adobe Target on the AEM web page(s).

Prerequisites

  • AEM 6.4
  • Customer needs to be properly provisioned with Adobe Launch and Adobe I/O from Adobe support
  • Adobe Target provisioned

General Steps

  1. Integrate AEM with Adobe Launch as specified in Integrate AEM with Adobe Launch Via Adobe I/O
  2. Create a property in Adobe Launch
  3. Add Extension, Adapter, Environment, Data Element, Rule and Publish it.
  4. Create a new Adobe Launch Configuration or edit the existing one.
  5. Create an A/B test activity via Visual experience composer in the Adobe Target
  6. Validate the integration

Note:

  • Customer needs to be properly provisioned with Adobe Launch and Adobe I/O from Adobe support
  • For any Integration with Adobe I/O, Adobe support needs to provision IMS before cloud solution API can be used.
  • If you have configured Launch for the first time then
    • Navigate to Admin Console > Products > Launch, by Adobe
    • Click on Permissions > Property Rights > + Add All
    • Click on Permissions > Company Rights > + Add All

Configure Adobe Launch

Create a property

  1. Log in to the Adobe Launch
  2. Click New Property
  3. Give Name: TestTarget and Domain: localhost.local
  4. Click Save

Documentation:  Adobe Launch Property

Create a Property

Create an Extension

  1. Click on Extensions tab
  2. Select Catalog and install Adobe Target
  3. The configure Extension will have all the values fetched already
  4. Click Save

Documentation: Adobe Launch Extensions

Create Extensions

Create a Data Elements

  1. Click on Data Elements tab
  2. Click Add Data Element and specify the name as PageName
  3. Select Extension as Core ->  Data Element Type as JavaScript Variable -> Default Value as not available -> Check Force lowercase value + Clean text -> Duration as PageView
  4. Path to variable as digitalData.pageName
  5. Click Save

Documentation: Adobe Launch Data Elements

Data Element

Create a Rule (for Target)

  1. Click on Rules tab
  2. Click on Add Rule and provide a name All Pages - Top
  3. Click on EVENTS -> Select Extension as Core -> Event Type as Library Loaded (Page Top) -> Name: Core - Library Loaded (Page Top) -> Order as default (50) and Click Keep Changes
  4. Click on ACTIONS -> Select Extension as Adobe Target -> Action Type as Load Target -> Name: Adobe Target - Load Target and Click Keep Changes
  5. Click on + icon and add another Action ->  Select Extension as Adobe Target -> Action Type as Add Params to All Mboxes -> Name: Adobe Target - Add Params to All Mboxes -> On the right add Name as “pageName” & Value as %PageName% (This is the data elemet created in the previous step ) and Click Keep Changes
  6. Click on + icon and add another Action ->  Select Extension as Adobe Target -> Action Type as Fire Global Mbox -> Name: Adobe Target - Fire Global Mbox -> and Click Keep Changes
  7. Save the rule
Documentation: Adobe Launch Rules
Create Rule

Create an Adapter

  1. Click on Add Adapter
  2. Name: akamai and Type: Akamai

Documentation: Adobe Launch Adapter

Create Adapter

Create the Environments

  1. Click on Environments Tab and Click on Add Environment
  2. Select Dev environment and provide name: DevTarget
  3. Select Adapter: akamai (created this in the previous step)
  4. Click Save

Do this for Stage and Production Environment as well.

Documentation: Adobe Launch Environments

Environments

Publish the Libraries

Now that we have created the Rule, Data element, Adapter, and the environments. We would need to build and deploy the property to the respective environments.

  1. Click on Publishing tabs and click on Add New Library
  2. Provide any name and select the Environment as DEV
  3. Click on Add All Changes Resources 
  4. Click Save

Now we can see the Library under the All Libraries section.

  1. Click on the drop-down icon of the new library created and click Build for development 
  2. Once build is successful, Click on the drop-down icon of the new library created and click Submit for Approval

Do this "build and submit" process for both Stage and Prod until the library reaches the Published section.

Documentation: Adobe Launch Publishing

Publishing

Configure AEM (for Adobe Target integration)

Add a configuration container (Configuration Browser)

  1. Open Tools > General > Configuration Browser
  2. Create a new configuration container structure for your site (Title Target) or select an existing one
  3. Click the Cloud Configurations capability

And Click Create

container

Create an Adobe Launch Configurations

  1. Open Tools > Cloud Services > Adobe Launch Configurations
  2. Select Target
  3. Create a new Adobe Launch Configuration

And 

  1. Title: LaunchConfig18april
  2. IMS Configuration: AEMLaunch16April2018 (This is the IMS configuration created in the article [1])
  3. Company: Select your Adobe Launch Company
  4. Property: Select the property created in Adobe Launch: TestTarget
  5. Include Production Code on Author: Forces inclusion of the production tag on the authoring instance: Keep is closed

Move to Stage and click Next (Library URI will automatically get populated) and then move to Production and save.

LaunchConfig

Map an Adobe Launch integration to a site in AEM

Now we will Map the Adobe Launch configuration created in the previous step to the desired web page

Assuming, we need to map this to We.Retail->Spain-> Espanol page, 

  1. Go to http://localhost:<port>/editor.html/content/we-retail/es/es.html
  2. Select the Open Properties
  3. Move to Advance Tab
  4. Scroll down to Configuration and click on cancel inheritance
  5. Select the Config Path (this must be the same as the configuration container created under the Configurations & Capabilities section above), in our case it is Target
  6. Click Save
MapConfig

Configure Adobe Target

Create A/B Test Activity

  1. Click Create Activity 
  2. Select A/B Test 
  3. Add "http://localhost:4502/content/we-retail/es/es.html" in Enter Activity URL 
  4. Click Next

Allow your browser to load scripts

Some browsers block the display of a page if the secure content is mixed with insecure content.

If the Visual Experience Composer (VEC) tries to open a page containing mixed (secure and insecure) content, a message displays showing how to disable blocking in your browser so you can open an HTTP site or a site that has mixed calls (HTTPS and HTTP).

You need to allow loading of the script. See here for more details.

Create Experiences

  1. On the top left, you can give a name to the activity: TestTargetViaLaunch
  2. From the left rail, Select Experience B and make changes to the page
  3. Scroll down to Featured Products and left click on Sleek Insulated Coat and Click Edit Background Color and assign any color to it.
  4. And click Next

           You can do any changes here like the text/image/CSS changes, remove, re-size etc.

Experience B

Select Audiences, Goals and Activate

Audience/Targeting
  1. Keep the audience as All Visitors-> Traffic Allocation Method as Manual
  2. Change the Experience A to 10 and Experience B to 90
  3. Click Next

Set Goals

  1. Go to Goal Metric -> Select Metric to Engagement and Action to Page Views
  2. Keep other things as default
  3. Click Save & Close

Note: You need to activate newly created Activity.

           

Targeting
Goal

Validate Integration

To validate AEM-Target integration, we need to go the web page where we have mapped the Adobe Launch configuration.

  1. Go to: http://localhost:4502/content/we-retail/es/es.html (Open in multiple browsers to view both versions of A/B Experiences )

Now use your creativity to extend this integration.

 

Validation

See also

Join the AEM community at: Adobe Experience Manager Community

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