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.
To communicate the impending removal/replacement of Campaign Standard capabilities, the following rules apply:
- Announcement of deprecation comes first. While deprecated capabilities can still be available for existing users, they will not be further enhanced, nor documented.
- Removal of deprecated capabilities will occur in the following release at the earliest. Actual target date for removal is announced in this page.
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.
This section lists features and capabilities that have been marked as deprecated with latest Campaign Standard releases. Generally, features that are planned to be removed in a future release are set to deprecated first, with an alternative provided. These features and capabilities are either no longer available for new Campaign Standard 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 to use the alternative provided. Please refer to the target removal date to plan your environment and project updates accordingly.
Area | Feature | Replacement | Target removal date |
Email design | Legacy email editor | The legacy email editor is now deprecated. Use the new Email Designer to create and personalize your email content. Learn more. Read out this section to learn how to adapt your email templates for the new editor. Please note that new Campaign Standard instances cannot access the legacy email editor starting 19.0 release. |
Oct, 2019 |
Area | Feature | Replacement | Target removal date |
Users and Security | Geographical units | Organizational and Geographical units are identical constructs in Campaign. Users should use Organizational units alone to build their user permission/data access hierarchy. Learn more. Please note that new Campaign Standard instances, as well as existing instances with no geographical units created, cannot have this capability implemented starting 18.7 release. |
Oct, 2019 |