2024 release notes 2024-rn
This page lists new capabilities, improvements, and fixes coming with 2024 Campaign v8 Releases. For the latest release, refer to this page.
For any new implementation or upgrade to an existing environment, install the latest release.
In this page
- Campaign v8.7 - Release 8.7.1 | Release 8.7.2
- Campaign v8.6 - Release 8.6.1 | Release 8.6.2 | Release 8.6.3
- Campaign v8.5 - Release 8.5.3
Release 8.7.2 release-8-7-2
Sept 3, 2024
New features new-8-7-2
-
New SMS sending connector - The SMS sending connector has been modernized and improved to enable transceiver mode SMPP connections, enable persistent SMPP connections, and ensure better compatibility for environments transitioning from Adobe Campaign Standard. A new SMS External account is now available for all new SMS implementations. Existing implementation are still supported, however recommendation is to move to this new modern and extended connector. Read more.
-
Rich Push Notification (GA) - You can now send rich push notifications. 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. With this version, a set of templates for rich push notifications are now available for your iOS and Android apps. Read more.
-
Branding - Branding options are now available for all channels, including SMS and Direct mail. Read more
Fixes fixes-8-7-2
The following issues are fixed in this release:
NEO-48232, NEO-56832, NEO-72504, NEO-74855, NEO-75898, NEO-76097, NEO-76958, NEO-77014, NEO-77795, NEO-78843, NEO-79328.
Release 8.7.1 release-8-7-1
May 2, 2024
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
The following FDA connectors have been added. Refer to this page.
-
Databricks is now supported as an external database with Adobe Campaign Federated Data Access (FDA).
-
A new Amazon Redshift FDA ODBC connector is now available. It offers improved connectivity, easier maintenance and enhanced compatibility. This new version brings the following improvements:
- The new connector is based on the ODBC interface which aligns with our most recent FDA connectors. This ensures long term support.
- It also introduces a new data loading mechanism using s3 buckets, significantly improving performance.
The legacy connector can still be used. If you want to try out the new one, please reach out to your Adobe representative.
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 June 30, 2025.
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
andcreated
. ThecreatedBy-id
attribute value is now populated with the current login ID by default. Values provided by users in API calls are ignored. -
To increase security over all communication between applications, mTLS is now supported for external API calls.
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
Release 8.6.3 release-8-6-3
July 30, 2024
New features new-8-6-3
-
Rich Push Notification - You can now send rich push notifications. 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. With this version, a set of templates for rich push notifications are now available for your iOS and Android apps. Read more.
-
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
General improvements improvements-8-6-3
- To increase security over all communication between applications, mTLS is now supported for external API calls.
Fixes fixes-8-6-3
The following issues are fixed in this release:
NEO-79328, NEO-78843, NEO-77795, NEO-77014, NEO-76958, NEO-76097, NEO-75898, NEO-72504, NEO-70263, NEO-67620, NEO-63197, NEO-58596, NEO-56832.
May '24 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.6.2 release-8-6-2
Feb 23, 2024
Fixes fixes-8-6-2
This release fixes the following issue:
- Fixed a performance issue that could occur on the mid-sourcing instance (NEO-72595).
Release 8.6.1 release-8-6-1
Feb 14, 2024
New features new-8-6-1
-
Starting this release, you have access to the new Campaign Web user interface, available through the central Adobe Experience Cloud environment. Experience Cloud is Adobe’s integrated family of digital marketing applications, products, and services. From its intuitive interface, you can quickly access your cloud applications, product features, and services. Learn how to connect to Adobe Experience Cloud, and access Adobe Campaign Web interface in this page.
note availability AVAILABILITY Campaign Web user interface is only available to users connecting to Adobe Campaign with their Adobe ID. Learn more about Adobe Identity Management System (IMS). -
Adobe Campaign v8 now integrates with Adobe Experience Manager as a Cloud Service, with authoring exclusively available via the Adobe Campaign Web User Interface. Learn more
-
You can now use your Adobe Experience Manager Assets library alongside your Experience Cloud Assets even if the Integration with the Adobe Experience Cloud package is installed on your Adobe Campaign instance. Learn more
General improvements improvements-8-6-1
- Campaign v8.6 brings improved throughput for email deliveries tracking indicators. With our optimized processes, tracking ingestion and compute time is reduced, and you can check your delivery key indicators much faster.
Deliverability updates deliverability-8-6-1
-
By February 2024, any company sending more than 5,000 email messages through Google or Yahoo! will have to start using an authentication technology known as Domain-based Message Authentication Reporting and Conformance (DMARC). Make sure to have DMARC record set up for all the subdomains that you are using with Adobe Campaign. Learn more
-
Starting June 1st, 2024, Google and Yahoo! will be requiring senders to comply with One-Click List-Unsubscribe. Adobe Campaign now supports this option. Learn more
Fixes fixes-8-6-1
The following issues are fixed in this release:
NEO-67892, NEO-67235, NEO-66797, NEO-66462, NEO-65091, NEO-65036, NEO-64984, NEO-64680, NEO-63973, NEO-63879, NEO-63815, NEO-63657, NEO-63539, NEO-63387, NEO-63294, NEO-63174, NEO-62964, NEO-62750, NEO-62686, NEO-62455, NEO-62406, NEO-61580, NEO-61199, NEO-60786, NEO-59544, NEO-59198, NEO-59059, NEO-58637, NEO-55197, NEO-52542, NEO-50488, NEO-47789
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