Tuesday Tech Bytes – Adobe Campaign Classic – Week 03 – Integrations

[#1]

Integrations in Adobe Campaign

Quick links: Tuesday Tech Bytes Series 2023

Lets check out few Integrations of Adobe Campaign with Adobe Analytics, Adobe Experience Manager (AEM), Snowflake.

Analytics Integration:

Adobe Campaign can be integrated with Adobe Analytics to send all the utm parameters like no of clicks, no of opens, unique clicks, sent, total bounces, unsubscribes from the attributes and indicator values in the Adobe Campaign Schemas.

Pre-requisites:

1.  The Web Analytics connector add-on must be installed on your environment, through the dedicated package.
2. Create the report suite and configure all the variables required in Adobe Analytics
3. Get all the Variables and events information from the Adobe Analytics Team to map them into the Adobe Analytics External account.

Now in Adobe Campaign Classic, Install the Integration with the Adobe Experience Cloud built-in package (Tools > Advanced > Import Package > Install a standard package > Select 'Integration with Analytics' > Start)

Creating External Account for Analytics in Campaign:

Navigate to /Administration/Platform/External Accounts/
 > Create new external account.
> In General tab,

Provide the Label and internal name: Analytics_External_Account

Type: Web Analytics

Click the “Configure” option as shown above and map it with the parameters in Report suite.

Next page would appear as shown below and Map all the eVars and event variables from Analytics to Adobe Campaign

Also, make sure to add all the tracking Url's to whose these parameters to be automatically added when used in the Campaign’s Delivery Templates in the Analytics External account created. Click on “Enrich the Formula” option in the External account as shown below:

Few useful parameters which are sent to Analytics team in Url parameters are Delivery ID, Delivery Label, broadlogID etc. We need to use the created External account in our delivery Template, by adding it to our delivery properties section as shown below:

Issues Faced during Integration:-

1. There can be few API Limits between Adobe Campaign and Adobe Analytics while sending the data after Integration is done. Whenever a campaign-analytics integration is created, an adobe IO project is auto-generated and the JWT credentials of that project is used for authentication, Please check the number of call per minute supported at both the ends to avoid issues.
2. To check the logs we can navigate to Home-> Monitoring ->  web@default -> Open the log Journal. If the issue is still not solved, please check the Verbose logs also

Snowflake Integration:

The entire connectivity and use of Snowflake Integration is clearly given to us in last year's Tech Bytes Quick Links. Please have a look on it.

Here, we would be looking into few issues faced during Integration

1. During this Integration, we don’t have enough privileges to the database, hence raised the support ticket with Adobe Team for required privileges. They have asked to add the Named right, but even that didn’t work. So we went back to the Snowflake Team and asked to check the roles and permissions to create Temp Schemas in Snowflake for the Data running in Adobe Campaign, they gave given us enough permissions to access the Views and then the issue is resolved. To set the FDA Rights, PFA the below documentation link https://experienceleague.adobe.com/docs/campaign-classic/using/installing-campaign-classic/accessing...
2. If we want to find out the type of Encryption of Data between Snowflake and Adobe Campaign, Please refer to the below documentation from Adobe 

   https://docs.posit.co/drivers/1.8.0/pdf/Simba%20Snowflake%20ODBC%20Connector%20Install%20and%20Confi...

   The Security details are in page no 54 and SSL Details are in page 79 in above link

3. If any reset of passwords happens at snowflake end, they have to be clearing cache in the server, which will have some down time impact at Adobe Campaign end.

4. In build 9356, the attributes of the Views were not automatically populated in ACM when we extend a new schema from Snowflake, instead we got until the element tag only for that Schema, after the build Upgrade to 9359, all the attributes are populating fine, but we still need to check the datatypes for those attributes match between snowflake and ACM.

   For datetime and Floating values, This needs to be cross checked keenly.

5. For the Worktables creation in Snowflake, they will get created in the same predefined schema. Currently there is no provision to change the schema under which a temporary table is created. It will be created under a pre-defined schema only as per the native ACC design.

AEM Integration:

This Integration enables us to manage the content of emails in AEM and forms content also and use the same in Adobe Campaign. Two-sided connectivity is required for this. It has several steps:

1. Install the AEM Integration Package in Campaign.
2. Create an operator for AEM in Campaign
3. Configure Campaign integration in AEM
4. Configure the AEM Externalizer
5. Configure the campaign-remote user in AEM
6. Configure the AEM external account in Campaign

Prerequisites:

Admin access in ACM with configured Database and admin access to AEM also.

1) Install the AEM Integration Package in Campaign:-

Go to Tools > Advanced > Import package

Click Install a standard package and then click Next and select  AEM Integration package.

Once the Installation of package is finished, click the Finish Button.

2)Create an operator for AEM in Campaign:-

Please go to Administration > Access Management > Operators node and select the Select the aemserver operator. Go to Edit Tab of operator and the “Access Rights” and then click the Edit the access parameters link.

Log out of the console and In Campaign installation location and edit the serverConf.xml file as an administrator. This file is typically located under:

Windows:- C:/Program Files/Adobe/Adobe Campaign Classic v7/conf 

Linux:- /usr/local/neolane/nl6/conf/eng 

Make sure you set the parameters allowHTTP="true",sesionTokenOnly="true", allowUserPassword="true" for the AEM Operator and reset the password for this operator in AEM also.

Steps 3,4,5 are done at AEM end, Basic architecture at AEM can be as shown below:

Content is generally published in author instance which is available internal to the Organization users, so to make it available to all recipients, we will publish the content to AEM replication agent.

6)Configure the AEM external account in Campaign:-

Go to Administration > Platform > External accounts and from the External account list, select AEM instance.

Enter the parameters like Server, Account, Password etc.

Then configure the AEMResourceTypeFilter Option , under  Administration > Platform > Options to filter types of Experience Manager resources that can be used in Adobe Campaign.

Example values can be : dir1/dir2,dir3/dir4/dir5 OR dir1/dir2

Now, once we configure the External Account, it can be used in our ACM Delivery Templates, by going into the Delivery Properties section and select the created AEM External account as shown below:

Issues faced in AEM Integration:

• Sometimes we get issues in AEM only, we need to whitelist Ips in Campaign and AEM

• Make sure the operators who are accessing Images from AEM have access to those Folders in AEM, or else we would face access related issues.