AEM author and publish instance running on localhost port 4502 and 4503 respectively
Access to your organizations Adobe Experience Cloud - https://
Experience Cloud provisioned with the following solutions
You should have permission to Develop, Approve, Publish, Manage Extensions, and Manage Environments in Launch. If you are unable to complete any of these steps because the user interface options are not available to you, reach out to your Experience Cloud Administrator to request access. For more information on Launch permissions, see the documentation.
For this integration, the following audiences need to be involved, and to perform some tasks, you might need administrative access.
AEM offers an out of the box integration with Experience Platform Launch. This integration allows AEM administrators to easily configure Experience Platform Launch via an easy to use interface, thereby reducing the level of effort and number of errors, when configuring these two tools. And just by adding Adobe Target extension to Experience Platform Launch will help us use all features of Adobe Target on the AEM web page(s).
In this section, we would be cover the following integration steps:
A property is a container that you fill with extensions, rules, data elements, and libraries as you deploy tags to your site.
Log in using your Adobe ID, and make sure you are in the right organization.
From the solution switcher, click on Launch and then select the Go To Launch button.
Make sure you are in the right organization and then proceed with creating a Launch property.
For more information on creating properties, see Create a Property in the product documentation.
Click on the New Property button
Provide a name for your property (For example, AEM Target Tutorial)
As the domain, enter localhost.com since this is the domain where the WKND demo site is running on. Although the ‘Domain’ field is required, the Launch property will work on any domain where it’s implemented. Primary purpose of this field is to pre-populate menu options in the Rule builder.
Click the Save button.
Open the property that you just created and click on the Extensions tab.
at.js. Customers still using Target older library,
mbox.js, should upgrade to at.js to use Launch.
The Target extension consists of two main parts:
Under Extensions, you can see the list of Extensions that are already installed for your Launch property. (Experience Platform Launch Core Extension is installed by default)
Click on the Extension Catalog option, and search for Target in the filter.
Select the latest version of Adobe Target at.js and Click on Install option.
Click on Configure button, and you can notice the configuration window with your Target account credentials imported, and the at.js version for this extension.
When Target is deployed via asynchronous Launch embed codes, you should hard-code a pre-hiding snippet on your pages before the Launch embed codes in order to manage content flicker. We will learn more about the pre-hiding snipper later. You can download the pre-hiding snippet here
Click Save to complete adding the Target extension to your Launch property, and you should now be able to see the Target extension listed under the Installed extensions list.
Repeat the steps above to search for “Experience Cloud ID Service” extension and install it.
Grant the Adobe I/O integration the access to select workspaces with the appropriate role to allow a central team to make API-driven changes in only a few workspaces.
At this point, you have successfully integrated AEM with Adobe Target using Adobe Experience Platform Launch as detailed in Option 1.
For using AEM Experience Fragment offers to power you personalization activities, lets proceed to the next chapter, and integrate AEM with Adobe Target using the legacy cloud services.