1. Install AEM Integration package in campaign [By default, no security zone is configured for this operator. To connect to Adobe Campaign via AEM, you must select one. In the serverConf.xml file, the allowUserPassword attribute of the selected security zone must be set to true to authorize AEM to connect Adobe Campaign via login/password.]
2. Configuring an AEM external account
a. Use IP over localhost
b. do not put "/" in end of the url
c. Test with admin user or campaign-remote (set the password in AEM first) or use new user having rights same as campaign-remote.
d. Make sure that the Enabled checkbox is selected
3. In AEM set connection with campaign with Campaign cloud configuration.
a. You need to configure two OSGI configuration settings to the reference the Publish server:
AEM Campaign Integration - Configuration: Go the OSGi configuration view at http://localhost:4502/system/console/configMgr-> search for AEM Campaign Integration - Configuration -> Edit the Public URL field to reference your published server (not localhost).
//This step is also necessary to replicate certain authoring instance configurations into the publishing instance
// The Externalizer is an OSGi service that lets you transform a resource path into an external and absolute URL. This service provides a central place to configure those external URLs and build them.
Note:- For the Adobe Campaign integration, make sure you configure the publish server
4. Turn off Antivirus for this test run
5. For integration to work your needs allowUserPassword to be configured. If you do not have access to server who ever have access ask them to verify & change. Example:- If your campaign server is hosted by adobe, file a support request at https://support.neolane.net/webApp/extranetLogin to create a security zone for your aem server following  & configure allowUserPassword.
If it is already configured using fiddler capture the network traffic between aem/ac and attach the aem logs with export of dump.