Latest releases latest-release

Adobe Campaign is regularly updated. This regular frequency of updates aims at getting the latest and greatest in your hands, keeping your environment secure and improving your experience with our product. Adobe strongly recommends all customers to upgrade to the latest version. This page lists new capabilities, improvements and fixes coming with Campaign v8 (console) latest releases. Learn more about Campaign versions and updates in this page.

As a Managed Cloud Services user, your instance is upgraded by Adobe with every new version. Adobe will contact you and upgrade your environments. Campaign client console must be upgraded to the same version as Campaign servers. Learn how to upgrade your client console in this page.

In addition, as a customer, ensure that you are using the latest supported versions of the systems listed in the Compatibility matrix.

Release 8.5.3 release-8-5-3

May 28, 2024

Migration to OAuth Server-to-Server credential change-8-5-3

Starting this version, 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. Learn more

Fixes fixes-8-5-3

The following issues are fixed in this release:

NEO-70263, NEO-64984, NEO-63657, NEO-63387, NEO-62964, NEO-62750, NEO-62686, NEO-59544, NEO-52542

May updates may-updates

The following change has been released in May and is now available to Campaign v8 users:

  • New Enhanced Security add-on: To make your network connection more secure and provide improved security for your resources, Adobe Campaign offers a new Enhanced Security add-on, which includes two features: Secure CMK integration and Secure VPN tunneling. Read more

Release 8.7.1 release-8-7-1

May 2, 2024

This release is in Limited Availability (LA). It is restricted to customers migrating from Adobe Campaign Standard to Adobe Campaign v8, and cannot be deployed on any other environment.
As a Campaign Standard user transitioning to Campaign v8, learn more about this transition in Campaign v8 web user interface documentation.

New features new-8-7-1

  • Rich Push Notification templates - You can now send rich push notifications via Android. Rich push notification is an enhanced form of mobile notification that goes beyond simple text messages by incorporating multimedia elements such as images, interactive buttons, or other rich media content. Read more.

  • Branding - As a Campaign Standard migrated user, your technical administrators can now define one or several brands to centralize the parameters that affect a brand’s identity. This includes the brand logo, the domain of the landing pages’ access URL, or message tracking settings. You can create these brands and link them to messages or landing pages. This configuration is managed in templates. Read more

  • Rest APIs - As a Campaign Standard migrated user, you can use Rest APIs to create integrations for Adobe Campaign and build your own ecosystem by interfacing Adobe Campaign with the panel of technologies that you use. Read more

  • Dynamic Reporting - As a Campaign Standard migrated user, you can access Dynamic Reporting which provides fully customizable and real-time reports to measure the impact of your marketing activities. It adds access to profile data, enabling demographic analysis by profile dimensions such as gender, city and age in addition to functional email campaign data like opens and clicks. Read more

Compatibility updates comp-8-7-1

  • Databricks is now supported as an external database with Adobe Campaign Federated Data Access (FDA). Learn more in this page.

Migration to OAuth Server-to-Server credential change-8-7-1

Starting this version, 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. Adobe will perform the JWT to OAuth migration for your outbound integrations, such as Campaign-Analytics integration or Experience Cloud Triggers integration.

If you have implemented inbound integrations with Campaign, you must migrate your Technical Account as detailed in this documentation. Existing Service Account (JWT) credentials will continue to work until January 27, 2025. In addition, the Developer Console will continue to support the creation of new Service Account (JWT) credentials until June 3, 2024. A new Service Account (JWT) credential cannot be created or added to a project after this date.

General improvements improvements-8-7-1

  • Several schemas have been changed from 32 to 64 bits. This only applies to customers migrating from Campaign Standard. Read more

  • In Campaign tables, the following attributes are now populated by default by the server date and time: lastModified and created. The createdBy-id attribute value is now populated with the current login ID by default. Values provided by users in API calls are ignored.

Fixes fixes-8-7-1

The following issues are fixed in this release:
NEO-72648, NEO-71534, NEO-71473, NEO-70263, NEO-70195, NEO-69651, NEO-68704, NEO-68192, NEO-67814, NEO-67702, NEO-67620, NEO-66022, NEO-65774, NEO-65633, NEO-64199, NEO-63706, NEO-63705, NEO-63287, NEO-63197, NEO-62575, NEO-60250, NEO-60192, NEO-58596, NEO-58314, NEO-58004, NEO-40054