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.
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.
Upload your public key and click Next.
Choose the product profile called Analytics-< Org Name > and click Save configured API.
From your project, select Service Account (JWT) and copy the following information:
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>
You should encode the private key in base64 UTF-8 format. Remember to remove the new line from the key before encoding it, except for the private key. The private key needs to be the same that was used to create the integration. To test the base64 encoding of the private key, you can use this website.
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" ... />