2024 releases

With the Service Account (JWT) credential being deprecated by Adobe, Campaign outbound integrations with Adobe solutions and apps now rely on OAuth Server-to-Server credential. If you have implemented outbound integrations, such as Campaign-Analytics integration or Experience Cloud Triggers integration, you must upgrade your Campaign environment to v7.4.1 and migrate your Technical Account to oAuth before January 27, 2025. Learn more

Once you have migrated your Campaign technical operators to Developer Console and transitioned to IMS for end-user authentication, you can now enable the user interface and API restrictions to remove options and capabilities which are specific to native authentication. Learn more

Adobe Campaign is now compatible with Microsoft Server 2022 as operating system.

Adobe Campaign is now compatible with RHEL 9 as operating system.

CAUTION

As an on-premise customer using RHEL 9, if you want to use DKIM (Domain Keys Identified Mail) authentication, you must update your system settings as detailed in this section.

Adobe Campaign is now compatible with Microsoft SQL Server 2022 and Oracle 23c as Relation Database Management Systems, and in Federated Data Access (FDA).

Adobe Campaign now requires at least a Java Development Kit (JDK) 11. On Windows, the JRE must be available as described in this section.

The Campaign (Neolane) SDK for mobile applications is now deprecated. You must now transition to Adobe Experience Platform SDK. Learn more.

In the meantime, to ensure service continuity, Campaign v7.4 comes with:

• a new Campaign SDK 1.0.27 for iOS, compatible with iOS 16 and 17, and the latest Apple iOS Privacy Request requirements.
• a new Campaign SDK for Android 14.