Deprecated features

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.

FeatureDetails
Campaign (Neolane) legacy SDK

The Campaign (Neolane) SDK for mobile applications is now deprecated. Instead, use the Adobe Experience Platform Mobile SDK by configuring the Adobe Campaign extension in the Data Collection UI. The Adobe Experience Platform Mobile SDK helps power Adobe's Experience Cloud solutions and services in your mobile apps. SDKs configuration is managed through the Data Collection UI for flexible configuration and extensible, rules-based integrations. Learn how to configure the Mobile App channel in Campaign v8 documentation.

Target removal date: July 31, 2025

Social Marketing with Facebook

Social Marketing with Facebook is now deprecated. You can use X (formerly known as Twitter) integration to post on social media, or work with Adobe to create a custom channel.

ACS Connector

ACS Connector (Prime offering) is now deprecated. You can use Campaign export/import capabilities to extract and inject data in both products.

Removed features

This section lists features and capabilities that have been removed from Campaign Classic.

FeatureDetails
Adobe Analytics Data Connector

The Adobe Analytics Data Connector has been removed on August 17,2022. It had been deprecated with Campaign 21.1.3 release.

If you are using this connector, you need to adapt your implementation accordingly. Learn more

Technical Deliverability Monitoring Report

The Technical Deliverability Monitoring Report is no longer available. It had been deprecated with Campaign 21.1.3 release.

OAuth Authentication (OAuth and JWT)

Triggers integration authentication originally based on OAuth authentication setup to access pipeline has now been changed and moved to Adobe I/O. This authentication mode had been deprecated with Campaign 20.3 release.

If you were using Triggers integration, learn how to adapt your implementation in this page.

For more information on OAuth Authentication depreciation, refer to this page

ReportingFollowing Adobe Flash Player EOL, the Gauge report and Chart rendering engine are no longer available. Learn more
Fax channelStarting Campaign 21.1.3 release, the Fax channel is no longer available. Learn more
Demdex domainStarting 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 authenticationStarting 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 archivingStarting 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
Lead managementStarting 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 fileStarting 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 marketingStarting Campaign 18.10 release, the predictive marketing capabilities are no longer available.
Web applications - MicrositesStarting 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.
Push Notifications - iOS Binary ConnectorPer 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.
decryptString API

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 messagesStarting 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 v1Starting Campaign 18.4 release, LINE Connect package is no longer available. Adobe recommends using the new LINE Channel package as a replacement. Learn more

End of compatibility

CAUTION
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.

Client console

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.

  • Windows Server 2003, 2008, 2008 R2
  • Windows 7, XP, Vista
NOTE
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.

Operating systems

  • Starting 7.3.1 release, Adobe Campaign is no longer compatible with Windows 8 and Windows Server 2012.

  • Starting 22.1 release, Adobe Campaign is no longer compatible with CentOs 8.x (64 bits). CentOS Linux 8 reached End Of Life (EOL) on December 31st, 2021. Learn more.

    If you were using this operating system, adapt your implementation accordingly. CentOS 7.x (64 bits) and RHEL 8.x/7.x (64 bits) are still supported.

  • Starting 21.1.3 release, Adobe Campaign is no longer compatible with Debian 8.

  • Starting 19.1 release, Adobe Campaign is no longer compatible with the following operating systems.