These steps should only be carried out by Hybrid and On-Premise implementations.
For Hosted implementations, please contact Adobe Customer Care team.
The integration between Adobe Campaign Classic and Adobe Analytics authentication supports Adobe Identity Management Service (IMS):
If you are managing a migrated external account, you must implement Adobe IMS and connect to Adobe Campaign via an Adobe ID. The user logged in via Adobe ID IMS should be the owner of the Data connector account in Adobe Analytics and have a set of permissions for the Product profile mentioned below.
If you are implementing a new connector, implementing Adobe IMS is optional. Without an Adobe ID User, Adobe Campaign will use a technical user to sync with Adobe Analytics.
For this integration to work, you have to create an Adobe Analytics product profile which will be used exclusively for the Analytics connector. Then, you will need to create an Adobe I/O project.
Product Profile determines the level of access a user has on your different Analytics Components.
If you already have an Analytics Product Profile, you should still create a new Adobe Analytics product profile used exclusively for the Analytics connector. This will ensure that your Product profile is set with the correct permissions for this integration.
For more information on Product profiles, refer to the Admin console documentation.
From the Admin console, select your Adobe Analytics Product.
Click New Profile.
Add a Product profile name, we suggest using the following syntax:
reserved_campaign_classic_<Company Name>. Then, click Next.
This Product profile should be used exclusively for the Analytics Connector to prevent misconfiguration errors.
Open your newly created Product profile and select the Permissions tab.
Configure the different capabilities clicking Edit and select the permissions to assign to your Product profile by clicking the plus (+) icon.
For more information on how to manage permissions, refer to the Admin console documentation.
For the Report Suites capability, add the Report Suites you need to use later on.
If you don’t have any report suites, you can create it following these steps.
For the Metrics capability, add the Metrics you will need to configure later on.
If needed, you can switch on the Auto-include option which will add every permissions item into the included list and will automatically add new permission items.
For the Dimensions capability, add the Dimensions you will need to configure later on.
For the Report Suite Tools capability, add the following permissions:
For the Analytics Tools capability, add the following permissions:
Your Product profile is now configured. You then need to create the Adobe I/O project.
Access Adobe I/O and log in as System Administrator of your Organization.
For more information on Admin roles, refer to this page.
Click Create a new project.
Click Add to Project and select API.
Select Adobe Analytics and click Next.
Choose Service Account (JWT) as authentication type and click Next.
Select the Option 1: Generate a Key-Pair option and click Generate a Key-Pair.
The config.zip file will then be automatically downloaded.
Select the Product profile created in the previous steps detailed in this section.
Then, click Save Configured API.
From your project, select Adobe Analytics and copy the following information under Service Account (JWT):
Use the private key generated in step 6.
If you already set up Triggers using these credentials, your private key must be the same for this connector configuration.
Encode the private key using the following command:
base64 ./private.key > private.key.base64. This will save the base64 content to a new file
Extra lines can sometimes be automatically added when copy/pasting the private key. Remember to remove it before encoding your private key.
Copy the contents from the file
Login via SSH to each container where the Adobe Campaign instance is installed and add the Project credentials in Adobe Campaign by running the following command as
neolane user. This will 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 can now start using the Analytics connector and track your customer behaviors.