Adobe constantly evaluates product capabilities to identify older features that should be replaced with more modern alternatives to improve overall customer value, always under careful consideration of backward compatibility. As Adobe Campaign Classic works with 3rd party tools, compatibility is updated on a regular basis, in order to implement supported versions only. Versions which are no longer compatible with Adobe Campaign Classic are listed below and in the Compatibility matrix.
To communicate the impending removal/replacement of Campaign Classic capabilities, the following rules apply:
This process gives customers at least one release cycle to adapt their implementation to a new version or successor of a deprecated capability, before actual removal.
Adobe Campaign releases and new capabilities are listed in the Release Notes.
This section lists features and capabilities that have been marked as deprecated with latest Campaign Classic releases.
Generally, features that are planned to be removed in a future release are set to deprecated first. These features and capabilities are either no longer available for new Campaign Classic customers, or should not be used for any new implementation. They are also removed from product documentation.
Customers are advised to review if they make use of the feature/capability in their current deployment, and make plans to change their implementation. Please refer to the target removal date to plan your environment and project updates accordingly.
|Adobe Analytics Data Connector
Starting Campaign 21.1.3 release, the Adobe Analytics Data Connector is deprecated.
If you are using this connector, you need to adapt your implementation accordingly. Learn more
Target removal date: March 1, 2022
|Technical Deliverability Monitoring Report
Starting Campaign 21.1 release, the Technical Deliverability Monitoring Report is deprecated.
If needed, you can receive this report daily by email until the feature removal date. To request it, open a specific Support Case and specify the name of the instance and the email address(es) to send the report to.
Adobe recommends you to engage with the Deliverability Team to define the best tools to monitor your instance deliverability performances.
Target removal date: End of 2021
|OAuth Authentication (OAuth and JWT)
Starting Campaign 20.3 release, Triggers integration authentication originally based on oAUTH authentication setup to access pipeline has now been changed and moved to Adobe I/O.
If you are using Triggers integration, you need to adapt your implementation accordingly. Learn more
For more information on OAuth Authentication depreciation, refer to this page
Target removal date: Nov 2021
This section lists features and capabilities that have been removed from Campaign Classic.
|Area - Feature||Replacement|
Starting Campaign 21.1.3 release, the Fax channel is no longer available. Learn more
Starting Campaign 21.1.3 release, the demdex domain used to import and export audiences to the Adobe Experience Cloud is no longer available. Learn more
|Windows NT authentication
Starting Campaign 20.3 release, Windows NT authentication has been removed from the available authentication methods when configuring a new database with a Microsoft SQL Server.. Learn more
|File-based email archiving
Starting Campaign 20.2 release, file-based email archiving is no longer available. Email archiving is now available through a dedicated BCC email address. Learn more
Starting Campaign 20.2 release, the Leads Management package is no longer available. Similar functionality can be implemented via other native workflow activities and data model modifications.
|Campaign APIs documentation - jsapi.chm file||Starting Campaign 19.1 release, Campaign Classic APIs are available in a dedicated page. If you were using the legacy jsapi.chm file, you should now refer to the new online version.|
|Campaign Orchestration - Predictive marketing||Starting Campaign 18.10 release, the predictive marketing capabilities are no longer available.|
|Web applications - Microsites||Starting Campaign 18.10 release, Microsites are no longer available. You can improve security by restricting access to only dedicated domains on Adobe Campaign configuration files, and use personalized URLs in Campaign by using DNS aliases. Learn more|
|Push Notifications - iOS Binary Connector||Per Apple's recommendation, Adobe has removed the legacy iOS Binary Connector starting Campaign 18.10 release. The more capable and more efficient HTTP/2-based connector is already available.|
Starting Campaign 18.6 release, for security reasons, decryptString API is no longer available by default for new installations.
In the context of a postupgrade to 18.6 (and later), this API is no longer activated, and has been replaced by the decryptPassword function. Learn more
|Mobile channel - MMS and WAP Push messages||Starting Campaign 18.4 release, MMS and Wap Push channels are no longer available. As a replacement, you can leverage SMS and Push deliveries.|
|Mobile channel - LINE v1||Starting Campaign 18.4 release, LINE Connect package is no longer available. Adobe recommends using the new LINE Channel package as a replacement. Learn more|
The following systems are deprecated for Campaign Classic. Please refer to the Compatibility matrix to upgrade to a newer version or move to a new system before the compatibility ends.
Starting 20.2 release, Legacy SMS connectors are deprecated. See Deprecated features section
Adobe Campaign Classic is compatible with all the systems and tools listed in the Compatibility matrix. When specific versions of these 3rd party systems and tools reach end-of-life (EOL) with their respective creators, Adobe Campaign is no longer compatible with those versions: they are announced as deprecated, and then are removed from our compatibility matrix in the subsequent product release. Please ensure you are on supported versions of any systems listed in the compatibility matrix to avoid any issues.
Adobe Campaign Classic Client Console can no longer run on the following systems as they have been deprecated by their editor. Customers running Campaign Client Console on one of these versions need to upgrade to newest version before target removal date. Refer to the Compatibility matrix.
Starting Campaign 20.1 release, Campaign Classic Client Console 32 bits is no longer compatible with Campaign latest versions. You need to use 64 bits Client Console.
Starting 21.1.3 release, the support for Debian 8 is deprecated.
Starting 19.1 release, Adobe Campaign is no longer compatible with the following operating systems.
Starting 19.1 Spring Release, Adobe Campaign is no longer compatible with the following web server.
Starting 19.1 Spring Release, Adobe Campaign is no longer compatible with the following tools.
Adobe does not support the following database engines as they have been deprecated by their editor. Customers running in these versions need to upgrade to newest version or move to another one.
Refer to Campaign Compatibility matrix to access the list of compatible versions.
FEDERATED DATA ACCESS (FDA)
Starting 20.2 release, Adobe Campaign is no longer compatible with the following FDA Server:
Starting 19.1 Spring Release, Adobe Campaign is no longer compatible with the following FDA Servers:
Campaign Classic is not compatible with the following servers in Federated Data Access (FDA).
Starting 19.1 Spring Release, Adobe Campaign is no longer compatible with the following RDBMS Servers:
Adobe Campaign is not compatible with the following SMS connectors:
Starting Campaign 21.1 release, the following CRM connectors are no longer compatible with Campaign: