Integration with Adobe Target using IMS | Adobe Experience Manager (2023)

The integration of AEM with Adobe Target via the Target Standard API requires configuration of Adobe IMS (Identity Management System) using the Adobe Developer Console.

Claim

Before beginning this procedure:

• Adobe supportmust set up your account to:

  • Adobe-console
  • Adobe Developer Console
  • Adobe Target and
  • Adobe IMS (Identity Management System)

• Your organization's system administrator must use the Administration Console to add the required developers in your organization to the appropriate product profiles.

  • This allows the specific developers to enable integrations in the Adobe Developer Console.
  • For more details seeManage developers.

Configure an IMS configuration - Generate a public key

The first phase of the configuration is to create an IMS configuration in AEM and generate the public key.

1. Open it in AEMToolsmenu.

2. I denSecurityselect sectionAdobe IMS configurations.

3. chooseTo createto openAdobe IMS technical account configuration.

4. Use the drop-down listCloud konfiguration, ChooseAdobe goals.

5. ActivateCreate a new certificateand enter a new alias.

6. Confirm withCreate certificate.

   

7. chooseTo download(ofDownload public key) to download the file to your local drive so it's ready to use whenConfigure IMS for Adobe Target integration with AEM.

   WARNING

   Keep this configuration open, it will be needed laterComplete the IMS configuration in AEM.

   (Video) Adobe Experience Manager Adobe Target

   

Configure IMS for Adobe Target integration with AEM

Using the Adobe Developer Console, create a project (integration) with Adobe Target that uses AEM and then assign the necessary permissions.

Create the project

Open the Adobe Developer Console to create a project with Adobe Target that uses AEM:

1. Open the Adobe Developer Console for projects:

   https://developer.adobe.com/console/projects

2. All the projects you have will be displayed. chooseCreate new project- the location and use depends on:

   See Also

   Manage Users and Products | Adobe Experience Cloud ServicesAdd Adobe Target with tags | Adobe Experience platform
   • If you don't have a project yet,Create a new projectwill be in the middle, at the bottom.
     
   • If you already have existing projects, they will be listed andCreate a new projectwill be at the top right.
     

3. chooseAdd to projectfollowed byAPI:

   

4. chooseAdobe goals, AndFollow:

   REMARK

   If you're subscribed to Adobe Target but don't see it listed, you shouldClaim.

   

5. Upload your public key, and when you're done, continue withFollow:

   

6. Confirm the credentials and continueFollow:

   

7. Select the desired product profiles and continueSave the configured API:

   REMARK

   The product profiles displayed depend on whether you:

   • Adobe Target Standard onlyStandard workspaceis available
   • Adobe Target Premium - All available workspaces are listed as shown below

   

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

8. The creation is confirmed.

Assign rights to the integration

You must now assign the necessary rights for the integration:

1. Open AdobeAdministration console:

   • https://adminconsole.adobe.com

2. Navigate toProducts(top toolbar), and then selectAdobe Target - <your tenant ID>(from the left panel).

3. chooseProduct profiles, then your desired workspace from the list presented. For example Standard workspace.

4. chooseAPI credentials, then the required integration configuration.

5. chooseEditorasProduct role; instead ofObserver.

Data saved to the Adobe Developer Console Integration Project

From the Adobe Developer Console - Projects, you can see a list of all your integration projects:

• https://developer.adobe.com/console/projects

chooseScreen(to the right of a specific project element) to see more details about the configuration. These include:

• project overview
• Insight
• References
  • Servicekonto (JWT)
    • Credentials
    • Generate JWT
• APIs
  • For example Adobe Target

Some of these are required to complete the integration of Adobe Target into IMS-based AEM.

Complete the IMS configuration in AEM

Returning to AEM, you can complete the IMS configuration by adding required values ​​from the Adobe Developer Console integration to Target:

1. Go back toIMS configuration open in AEM.

2. chooseFollow.

3. Here you canproject configuration details in the Adobe Developer Console:

   • title: Your message.
   • authorization server: Copy/paste itaudline ofLoad capacitysection below, e.g.https://ims-na1.adobelogin.comin the example below
   • API key: Copy this fromOverviewsection
   • The client's secret: Generate this inOverviewsection and copy
   • Load capacity: Copy this fromGenerate JWTsection

   

4. Confirm withTo create.

5. Your Adobe Target configuration will be displayed in the AEM console.

   

Verify the IMS configuration

To verify that the configuration is working as expected:

1. Open:

   • https://localhost/libs/cq/adobeims-configuration/content/configurations.html

   For example:

   • https://localhost:4502/libs/cq/adobeims-configuration/content/configurations.html

2. Choose your configuration.

3. chooseCheck healthfrom the toolbar followed byaccount.

   (Video) 6 Integrating Adobe target with Adobe Experience Manager

   

4. If successful, you will see the message:

   

Configure the Adobe Target Cloud service

The configuration can now be referenced so that a cloud service can use the Target Standard API:

1. openToolsmenu. Then withinCloud servicessection, selectLegacy cloud services.

2. Scroll down toAdobe goalsand chooseConfigure now.

   OfCreate configurationdialog box opens.

3. Enter onetitleand, if you will, aName(if left blank, it will be generated from the title).

   You can also select the desired template (if more than one is available).

4. Confirm withTo create.

   OfEdit itemdialog box opens.

5. Enter dataAdobe Target Settingsfane:

   • Approval: IMS

   • Tenant ID: The Adobe IMS tenant ID. Also seeTenant ID and client codesection.

     REMARK

     For IMS, this value must be obtained from the Target itself. You can log into Target and extract the tenant ID from the URL.

     If the web address e.g. is:

     https://experience.adobe.com/#/@yourtenantid/target/activities

     Then you would useyour tenant.

   • Customer code: SeTenant ID and client codesection.

   • IMS configuration: Select the name of the IMS configuration

     (Video) Adobe Experience Manager (AEM) - Adobe Target Personalization Integration for AB Tests using XFs

   • API-type: REST

   • A4T Analytics Cloud-konfiguration: Select the Analytics cloud configuration used for goals and goal activity metrics. You need this if you use Adobe Analytics as a reporting source when targeting content. See note if you cannot see your cloud configurationKonfigurer A4T Analytics Cloud-konfiguration.

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

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

   • Customer library: Choose whether you want the AT.js client library or mbox.js (legacy).

   • Use Tag Management System to provide client library: Use DTM (deprecated), Adobe Launch, or another tag management system.

   • Custom AT.js: Leave blank if you have checked the Tag Management box or to use default AT.js. You can also upload your custom AT.js. Shown only if you have selected AT.js.

   REMARK

   Configuring a cloud service to use the Target Classic APIis deprecated (using the Adobe Recommendations Settings tab).

6. ClickConnect with purposeto initialize the connection to Adobe Target.

   If the connection is successful, the message is displayedThe connection was successfulsee you later.

7. chooseOkayon the message followed byOkayin the dialog box to confirm the configuration.

8. You can now proceed toAdd a target frameto configure ContextHub or ClientContext parameters passed to the Target. Note that this may not be required to export AEM Experience Fragments to Target.

Tenant ID and client code

MetAdobe Experience Manager 6.5.8.0, the Customer Code field was added to the target configuration window.

When configuring the Tenant ID and Client Code fields, keep the following in mind:

1. For most customers, the tenant ID and client code are the same. This means that both fields contain the same information and are identical. Be sure to enter the tenant ID in both fields.
2. For legacy purposes, you can also enter different values ​​in the Tenant ID and Client Code fields.

In both cases, remember that:

• By default, the customer code (if added first) is also automatically copied to the Tenant ID field.
• You have the option to change the default tenant ID set.
• Therefore, the backend calls to Target will be based on the tenant ID, and the client-side calls to Target will be based on the client code.

As mentioned earlier, the first case is the most common for AEM 6.5. Either way, take carebothfields contain the correct information depending on your requirements.