The following troubleshooting tips help solve the most common problems you may encounter when you integrate AEM with Adobe Campaign:

General Troubleshooting Tips

For both integrations, you can check whether HTTP-calls are sent (AEM > Adobe Campaign, Adobe Campaign > AEM):

When integrations are failing, make sure that these calls arrive on the other end (to avoid firewall/SSL issues).

For AEM functionality, you will see that json calls are requested from the AEM author interface; these should not result in an HTTP-500 error. If you see HTTP-500 errors, check the error.log for more information on this.

Raising the debug level for campaign-classes in AEM also helps to troubleshoot issues.

If the connection fails

Check that you have configured the aemserver operator in Adobe Campaign.

If images do not appear in the Adobe Campaign console

Check the HTML source and validate that you can open the URL from the client machine. If the URL has localhost:4503 in it, then change the configuration of Day CQ Link Externalizer on your author instance to point to a publish instance that can be reached from the Adobe Campaign console machine.

If you see http instead of an expected https links in the synchronization dialog

With the following setup:

Hosted Adobe Campaign using https for communication with AEM Author

Reverse proxy terminating SSL

On premise AEM Author instance

When trying to synchronize content in Adobe Campaign delivery, AEM returns a list of newsletters. However, the urls to the newsletters in the list are http addresses. When selecting one of the items in the list an error occurs.

To solve this issue:

The dispatcher or reverse proxy needs to be configured to pass the original protocol as a header.

If the custom template I created cannot be selected in Page Properties

When creating a mail template for Adobe Campaign, you must include the property acMapping with the value mapRecipient in the jcr:content node of the template, or you will not be able to select the Adobe Campaign template in Page Properties of AEM (field is disabled).

If you get the error "com.day.cq.mcm.campaign.servlets.util.ParameterMapper" in your logs

When using your custom template, you get the error "com.day.cq.mcm.campaign.servlets.util.ParameterMapper" in your logs. In this event, be sure to install Featurepack 6576 from Package Share. This is an issue where if the acMapping property is set to a value other than recipient.firstName, a blank value is created on the Adobe Campaign Manager side.