Configuring Adobe I/O for Adobe Experience Cloud Triggers

CAUTION

If you are using an older version of Triggers integration through oAuth authentication, you need to move to Adobe I/O as described below. Legacy oAuth authentication mode will be retired on April 30, 2021. Learn more

Note that during this move to Adobe I/O, some incoming triggers may be lost.

Prerequisites

This integration only applies starting Campaign Classic 20.3, 20.2.4, 19.1.8 and Gold Standard 11 releases.

Before starting this implementation, please check you have:

  • a valid Organization identifier: the Identity Management System (IMS) organization identifier is the unique identifier within the Adobe Experience Cloud, used for example for the VisitorID service and the IMS Single-Sign On (SSO). Learn more
  • a Developer access to your Organization. If you need to request the System Administrator privileges of the IMS Org, follow the procedure detailed in this page to provide this access for the all Product Profiles.

Step 1: Create/update Adobe I/O Project

  1. Access Adobe I/O and log in with the System Administrator right for the IMS Organization.

    NOTE

    Make sure you are logged into the correct Organization portal.

  2. Extract existing integration client identifier (Client ID) from the instance configuration file ims/authIMSTAClientId. Non existing or empty attribute indicates client identifier is not configured.

    NOTE

    If your Client identifier is empty, you can directly Create a New project in Adobe I/O.

  3. Identify the existing project using the extracted client identifier. Look for existing projects with the same client identifier as the one extracted in previous step.

  4. Select + Add to Project and choose API.

  5. In the Add an API window, select Adobe Analytics.

  6. Choose Service Account (JWT) as the authentication type.

  7. If your Client ID was empty, select Generate a key pair to create a public and private key pair.

  8. Upload your public key and click Next.

  9. Choose the product profile called Analytics-< Org Name > and click Save configured API.

  10. From your project, select Service Account (JWT) and copy the following information:

    • Client ID
    • Client Secret
    • Technical account ID
    • Organization ID

CAUTION

Adobe I/O certificate will expire after 12 months. You need to generate a new key pair every year.

Step 2: Add the project credentials in Adobe Campaign

To add the project credentials in Adobe Campaign, run the following command as ‘neolane’ user on all the containers of the Adobe Campaign instance to insert the Technical Account credentials in the instance configuration file.

nlserver config -instance:<instance name> -setimsjwtauth:Organization_Id/Client_Id/Technical_Account_ID/<Client_Secret>/<Base64_encoded_Private_Key>

The private key should be encoded in base64 UTF-8 format. To do so:

  1. Use the private key generated in the Step 1: Create/update Adobe I/O Project section. The private key needs to be the same as the one used to create the integration.

  2. Using this this website, copy paste your private key to the corresponding field.

    NOTE

    An extra line can sometimes be automatically added when copy/pasting the private key. Remember to remove it before encoding your private key.

  3. Click Encode.

  4. Use your newly generated private key encoded in base64 UTF-8 format to run the command detailed above.

Step 3: Update pipelined tag

To update pipelined tag, you need to update the authentication type to Adobe I/O project in the configuration file config-< instance-name >.xml as follows:

<pipelined ... authType="imsJwtToken"  ... />

On this page