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 with Campaign with Campaign will be retired on November 30, 2021. Learn more
Note that during this move to Adobe I/O, some incoming triggers may be lost.
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:
Access Adobe I/O and log in with the System Administrator right for the IMS Organization.
Make sure you are logged into the correct Organization portal.
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.
If your Client identifier is empty, you can directly Create a New project in Adobe I/O.
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.
Select + Add to Project and choose API.
In the Add an API window, select Adobe Analytics.
Choose Service Account (JWT) as the authentication type.
If your Client ID was empty, select Generate a key pair to create a public and private key pair.
The keys will then be automatically downloaded with a default expiry date of 365 days. Once expired, you will need to create a new key pair and update the integration in the configuration file. Using the Option 2, you can choose to manually create and upload your Public key with a longer expiry date.
Choose any existing Product profile or create a new one if needed. No permission is required for this Product profile. For more information on Analytics Product Profiles, refer to Adobe Analytics documentation.
Then, click Save configured API.
From your project, select Adobe Analytics and copy the following information under Service Account (JWT):
Adobe I/O certificate will expire after 12 months. You need to generate a new key pair every year.
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:
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.
Encode the private key using the following command:
Extra lines can sometimes be automatically added when copy/pasting the private key. Remember to remove it before encoding your private key.
Use your newly generated private key encoded in base64 UTF-8 format to run the command detailed above.
To update [!DNL 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" ... />