Looking for a specific release of Adobe Campaign Standard?
Each release comes with new features and patches. Click on a release to view its content. Consult the Release Planning to find out when the next release will happen.
View the latest documentation updates for Adobe Campaign Standard. If you're looking for a previous release, consult these pages: 2018 Release Notes, 2017 Release Notes, 2015-2016 Release Notes. Also consult the list of Deprecated and Removed Features.
Release 19.2.4 - June 2019
- Fixed an issue which prevented users from editing fragments when empty style tags were used in the HTML. This is a follow-up fix for CAMP-33778 in 19.2.3.
Release 19.2.3 - June 2019
Introduced a series of improvements and fixes to optimize fragments in the 19.2 release. Newly created fragments will work seamlessly. Fragments that were previously built have been grayed-out and need to be migrated to the new format. To do so, click on each fragment and validate its migration to the new format. We recommend that you test a few fragments before migrating them all.
- Fixed an issue which prevented users from editing a fragment after unlocking it. This was affecting existing fragments when updating to 19.2. (CAMP-33778)
- Fixed an issue when using dynamic content. Extra spaces were added in the HTML.
- Fixed an issue which could prevent SMS sending from resuming after a disconnection of the SMS connector.
- Fixed an issue which could close SMPP connections when TLS was enabled.
- Fixed an issue which could close SMPP connections when TLS was enabled.
- The “Launch_URL_Campaign” option has been added in Campaign to manage properties of mobile applications created with Adobe Experience Platform Mobile SDK.
- Fixed an error that led to the Sandbox environment option being unchecked after uploading the certificate of a newly created mobile property and exiting the mobile application property page.
- Fixed an issue which prevented you from enriching a transactional message content with information from the Service resource. (CAMP-33707)
- Fixed an issue in Blacklist landing pages that occurred when trying to unsubscribe profiles from a service.
Release 19.2 - May 2019
To help increase efficiency in your work as an Admin user, you can easily monitor capacity and manage settings of your instances (starting with SFTP servers management).
Local notification messaging allows you to inform your users when new data becomes available within their mobile applications, even without having access to the Internet or the mobile application running in the foreground. Local notifications are triggered by a mobile application on a particular time and depending on an event.
|Workflow enhancement - Add a payload to external signal activity|
Start a workflow with a payload when defined conditions are successfully met from another workflow or a REST API call to integrate with your external systems. This also includes a new test activity where you can run tests on this functionality.
|Landing Pages enhancement - Google reCAPTCHA|
Leverage Google reCAPTCHA to prevent spam on your landing pages without requiring any action from your customers.
- Fixed a potential clickjacking security issue in reporting workspace.
Email Designer enhancements
- Fixed an issue that occurred when duplicating fragments and trying to use them in the Email Designer. (CAMP-33193)
- Fixed an issue that created unwanted spaces when using inline elements in the Email Designer interface. (CAMP-32163)
- Fixed an issue that deleted some additional HTML tag attributes added by the user after saving email content in the Email Designer. (CAMP-32162)
- Fixed an issue that displayed a Microsoft Office tag in the Email Designer HTML mode even after removing it. (CAMP-32141)
- If you created an email using a previous version of the Email Designer, upon opening this email content, a pop-up window now prompts the user to update to the latest version. (CAMP-31529)
- Fixed an issue that could distort images from an email created with the Email Designer when delivered to some messaging clients. (CAMP-31407)
- Fixed an issue that prevented some elements such as lists or buttons from being correctly displayed in plain text mode when created in HTML mode. (CAMP-32582, CAMP-32542)
- Fixed an issue that prevented displaying more than 50 organizational units in a content template or fragment properties. (CAMP-32932)
- Fixed an issue with the viewport background color when receiving an email created with the Email Designer on Outlook. (CAMP-31402)
- Fixed an issue that could prevent email contents created with the Email Designer from being responsive when opened in Outlook. (CAMP-31400)
- Fixed an issue that prevented dynamic content from working properly when used in an email subject. (CAMP-32837)
- Fixed an issue related to the email subject that was not properly escaped.
- Fixed an issue that prevented fragments from being loaded in the Email Designer left palette.
- Fixed an issue that prevented fragments created during email content edition from being displayed in the Email Designer left palette when refreshing the fragment list.
- Fixed several issues that occurred while using dynamic content in an email.
- Fixed an issue that occurred with the color picker when trying to define a color using RGB values.
- Fixed an issue that prevented the mirror page from being responsive when receiving the email on a mobile.
Transactional Messaging enhancements
Several improvements have been added to the Transactional messaging channel in order to optimize operation and performance.
- The transactional message duration has been extended to make sure that all messages are sent before they expire, especially when retries are performed.
- Transactional messaging performance has been increased by distributing the load on different sending threads.
- The transactional messaging process has been optimized to be able to start in parallel multiple analysis of the same message.
- Fixed an issue that could lead to inconsistent throughput and latency for transactional push notifications.
- Fixed an issue that displayed an incorrect target audience for transactional message execution deliveries.
- Fixed an issue that occurred when importing a package with an event configuration and the associated transactional message. For more on this, refer to the detailed documentation.
- Fixed an issue that deleted the collection data from the test profiles created for a transactional message containing product listings.
- A new option has been added to the SMS external account. It enables to limit the maximum number of MTA processes that send SMS in order to better control the number of parallel connections. For more information, refer to the SMS connector protocol and settings technote.
- When publishing a resource with API extension, if the API has already been published, it is now automatically updated each time it is published again. Previously this action was manual and failing to update the API could break the profile or service resource of this API. For more on this, refer to the detailed documentation.
- Zip code dimension has been removed from Dynamic Reporting. We recommend using City, Country, State dimensions instead.
- The ‘First Launch’ Lifecycle event trigger for In-App messages has been removed.
- When exporting a package with security groups, it now contains the roles that are assigned to each group. (CAMP-32960)
- In the Load file activity, a new option lets you check that the columns of the file you are uploading match the column definition. For more information, refer to the detailed documentation. (CAMP-32229)
- Workflows can now be started with a payload, allowing you to use and share external parameters between activities within the workflow. For more information, refer to the detailed documentation. (CAMP-29412 & CAMP-29413)
- Campaign Standard APIs now let you update profiles' geographical and organizational units using a payload. For more information, refer to the detailed documentation.
- Error messages when an object from the database is not accessible have been made clearer to understand.
- Auto sequence ID generation has been improved for custom resources. Primary keys for new custom resources are now in 64 bits by default.
- The custom resource publication test mode has been improved. A warning message is now displayed to users if the last custom resource publication failed and is not fixed. After a custom resource publication failure, you can rollback to last working version. For more information, refer to the detailed documentation.
- A new option was added in the Transfer file activity. It allows you to sort the files when using the File download action, in SFTP mode. For more information, refer to the detailed documentation. (CAMP-33109)
- Fixed an issue that could cause memory leak to the MTA when SMS settings were reloaded.
- Fixed an issue that could prevent publishing database updates in repair mode.
- Fixed an issue that caused discrepancy between Adobe Analytics Reports and Adobe Campaign Dynamic Reporting. (CAMP-25393)
- Fixed an error which caused the Report sharing workflow to fail.
- Fixed an error that prevented users from sending In-App messages with just Media URL.
- Fixed an issue that displayed a mobile app even if its certificate was not uploaded to the instance.
- Fixed an error that prevented personalization fields from working when using the Target all users of a Mobile app template.
- New Campaign Standard instances were provisioned. (CAMP-32635 & CAMP-32344)
- Fixed an error that prevented the customization of date formula in a workflow. (CAMP-30336)
- Fixed an issue when defining a custom date formula that could prevent the "Additional data" and "Segment code" fields from being available in the drop-down list. (CAMP-32383)
- Fixed an issue that could prevent the "Transfer file" and "Extract file" activities from finding the files rejects if they were encrypted. (CAMP-32377)
- Fixed an issue in APIs that could prevent the lineCount filter from rendering the exact total count. (CAMP-31424)
- Fixed an issue in landing pages that could prevent input fields from showing the updated value once it had been modified. (CAMP-31401)
- Fixed an issue which could lead a signal activity to activate unexpectedly.
- Fixed an issue which could prevent email preview from displaying when the audience is empty.
- Fixed an issue in the “Extract file” activity that could generate a file while the "Do not generate a file if the inbound transition is empty" option was activated.
- Fixed an issue that led the Deliverability workflow to turn off if it did not finish successfully.
- Fixed an issue which could prevent users from saving or scheduling reports. (CAMP-31133)
Release 19.1.3 - March 2019
Email Designer enhancements
- Fixed an issue which prevented a template from being modified after saving it.
- Fixed various issues when using a previously created template in an email.
- Fixed an issue which prevented components from being hidden in imported templates.
- Fixed an error when viewing typology rules. (CAMP-32059 & CAMP-31849)
- Fixed an issue which prevented typology rules from being edited. (CAMP-31750)
- Fixed an issue with the inMail process which could stop unexpectedly. (CAMP-31238)
Release 19.1 - February 2019
|Push channel Reporting improvements|
Several enhancements have been added to Push channel reporting to allow you to measure user engagement more intuitively. With this release, we are expanding the list of Push channel metrics to three different metrics: Impressions, Clicks, Opens (App Open) to help you measure and analyze users’ interaction with Push notifications more effectively. Along with this, we are also standardizing the definition and implementation of these metrics. The Push notification built-in report has also been improved with commonly used visualizations and metrics.
|Launch integration for Mobile App|
This release contains the integration of Adobe Campaign with the GA versions of Android and iOS extensions for Adobe Campaign Standard in Adobe Experience Platform Launch and Mobile SDKs. These extensions support push messaging, in-app messaging, and mobile app profile updates.
|Mobile In-App Messaging|
This release contains the GA version of In-App channel in Campaign. From a functional standpoint, the most notable additions to the Beta release are Dynamic reports for In-App channel and secure handshake between Mobile SDK and MCIAS (Marketing Cloud In-App Messaging Service that serves the In-App rules to the SDK). Secure handshake ensures that your users' PII data does not fall into malicious hands as well as enables you to maintain users' privacy on a shared device by clearing out message cache every time the user logs out.
The following workflow capabilities have been added:
- The generated landing page HTML code has been updated to prevent search engine indexing.
Email Designer enhancements
- A set of four best-in-class responsive email templates designed by Behance artists is now available.
- Our new on-boarding experience will help you start email creation faster and give you easier access to documentation and tutorials.
- You now have the flexibility to configure the number of columns and width based on your needs.
- When editing in mobile view, you can hide certain components just in mobile display for effective usage of space.
- You can now add custom social channels to your email template on top of the ones that are already available.
- Fixed an issue that prevented to scroll down the structure menu when using more than 18 structures. (CAMP-31173)
- Fixed an issue that displayed the preheader on top of the content when forwarding an email containing a preheader sent with Adobe Campaign. (CAMP-30736)
- Fixed an issue that prevented the subject line from being updated when clicking the Refresh AEM content option after modifying the subject in Adobe Experience Manager. (CAMP-29984)
- Fixed several issues that prevented the use of dynamic images from Adobe Target.
- Fixed an issue that prevented the preview from being updated when retrieving content at preparation time if the content had been previously imported from a URL.
- The YouTube icon has been added to the Social content component.
- The List view has been added for content components and fragments displayed in the Email Designer palette.
- Adobe Campaign is now fully FCM compliant for both SDK V4 and AEP SDK Apps.
- Adobe Campaign supports Push notifications on Wear OS by Android as well as watchOS by Apple.
- Warning and error messages that may display when navigating in the interface have been made clearer and easier to understand.
- You can now add to the profiles list columns related to opt-in and opt-out ("No longer contact …" fields).
- The Time zone drop-down list in the Profile creation screen has been moved from the Address section to the upper-section of the interface.
- You can now add separators when configuring custom resource screens, allowing you to organize your fields into categories.
- Adobe Campaign and Adobe Experience Cloud will drop support for Microsoft Internet Explorer 11 starting Spring 2019, and Campaign Standard 19.2 release. Please switch to Microsoft Edge or another supported browser. See Deprecated and removed features page.
- The Country code field from the Profile resource has been renamed to Country/Region code.
- Fixed an issue that prevented the message from being sent when adding a test profile to an email transactional message. (CAMP-29854)
- Fixed an issue that slowed down message sending from other channels if sending was low for one channel when message sending from all channels was triggered simultaneously.
- Fixed an issue that caused the MTA to start sending SMS messages when the external account connection was not yet established.
- Fixed an issue that occurred with the Scheduler activity execution frequency and start time. (CAMP-30745)
- Fixed an issue that could occur with PKEY generation when using extended profile resources. (CAMP-30285)
- Fixed an issue that could occur with calendar day based Fatigue rules. (CAMP-30136)
- Fixed an issue that could occur when trying to access custom resources with names ending with "Base". (CAMP-30109)
- Fixed an issue that prevented from using a PATCH call to subscribe a profile to a service. (CAMP-29728)
- Fixed an issue that could corrupt a workflow when importing an XML file through the Load File activity. (CAMP-29208 and CAMP-28205)
- Fixed an issue when linking custom resources which could prevent reverse cardinality links to be generated. (CAMP-30476)
- Fixed an issue that prevented from extending delivery logs when using the segment code only.
- Fixed an issue which could duplicate rows when using the File transfer activity in workflows.
- Fixed an issue which prevented scheduled reports from being sent at the chosen time.
- Fixed an issue which caused discrepancy between the "To deliver" and "Sent" KPIs for an In-App delivery in a workflow.
- Fixed an issue that prevented tracking from working for an In-App message authored with a custom HTML.
- Fixed an issue that prevented In-App delivery content from being saved when used in a workflow.
- Fixed an issue that prevented mobile applications from being displayed for administrators.
- Fixed an issue which caused the Deliverability Update technical workflow to fail. (CAMP-26387)
- Fixed an issue which caused discrepancy between the profiles targeted while creating an In-App delivery and the ones displayed in the delivery dashboard. (CAMP-28722)
- Fixed an issue with the Campaign and Assets Core Service integration which could prevent you from selecting a shared asset in an email.
Release 19.0 - January 2019
|Email Designer General Availability|
The new intuitive Email Designer (formerly known as Creative Designer) has moved to GA. It now supports all the features from the legacy content editor, including:
For more information, refer to the detailed documentation and the how-to video. Improvements and fixes are listed below.
As a consequence, the legacy email content editor is now deprecated. For more information, refer to this page.
|Product Listings in Transactional Emails|
You can now reference one or more product collections in a transactional email message. For example, you can automatically send a cart abandonment email listing all the products that were in the user’s cart with an image, price, and link to each product.
|Mobile View in the Email Designer|
You can now switch to a dedicated mobile view when editing email content. This allows you to fine-tune the responsive design of an email by separately editing all style options for mobile display, such as adapting margins, smaller font size, different background color, and so on.
|In-App Messaging Beta Improvements|
The In-App Messaging Beta feature has been enhanced with the following capabilities:
- A new option in the Load data activity now lets you apply a post-processing stage to the file containing the rejected records (ex. Zip format compression). (CAMP-24521)
- A new option in the Update data activity now allows you to configure the maximum batch size for the data to upload. (CAMP-28400)
- Improved profiles' address state selection. When selecting a country, the "State" drop-down list is now automatically updated with relevant states values. (CAMP-28874)
- A new option in the Extract file activity now prevents from generating a file if the inbound transition is empty. This avoids creating and uploading empty files on SFTP servers.
- The Delivery summary report has been improved.
- The list of available countries when defining a profile's address has been enriched. (CAMP-26707)
- An error message is now displayed when trying to import a built-in workflow.
- Fixed an issue that enabled the geographical unit capability on an email template or a content fragment created with the Email Designer, even though this capability was disabled in Adobe Campaign, which made the template or fragment unavailable when trying to access it again. (CAMP-28174)
- Fixed an issue that prevented Dynamic content conditions to be saved when editing content with the Email Designer. (CAMP-27905)
- Fixed an issue that removed the HTML version from the email content after editing the plain text version of a message and breaking HTML synchronization in the Email Designer. (CAMP-28507)
- Fixed an issue that prevented the Email Designer interface to open when using Internet Explorer 11. (CAMP-28273)
- Fixed an issue that distorted the Microsoft Outlook rendering of style settings applied to buttons with the Email Designer.
- Fixed an issue in the Email Designer that made editable a URL from a content fragment used in an email, which was not expected as the fragment is locked by default.
- Fixed an issue that prevented the Email Designer divider component to be displayed in Microsoft Office.
- Fixed an issue which caused a page freeze on certain Internet browsers when viewing a content synchronized from AEM using the legacy email content editor. (CAMP-29068)
- Fixed an error that occurred when clicking any image in an email when using the legacy email content editor. (CAMP-30424)
- Fixed an issue that prevented the newly created fragments to be displayed when editing an email with the Email Designer. (CAMP-29928)
- Fixed an issue that prevented button text to be displayed properly in emails created with the Email Designer and received using Outlook webmail client.
- It is now possible to create profile transactional messages using the Email Designer. (CAMP-28900)
- Fixed an error in the Email Designer that made the content editable when retrieving content from a URL automatically at preparation time, whereas it should be locked.
- Fixed an issue that showed incorrect delivery logs in Dynamic reporting. (CAMP-23446)
- Fixed an issue that could affect the numbers on the bounce Summary report (CAMP-28703)
- Fixed an issue with the Campaign and Assets Core Service integration which could prevent assets from being displayed when selecting Image shared from Adobe Experience Cloud in an email (CAMP-28732).
- Fixed an issue that prevented SMS messages containing the ‘œ’ character to be sent even though transliteration was authorized in the SMPP external account. (CAMP-29041)
- Fixed an issue that could display duplicate records when using a Segmentation activity in workflows. (CAMP-28743)
- Fixed an issue which prevented from deleting one of the value mappings on a column in a workflow activity. (CAMP-28708)
- Fixed an issue in the File transfer activity, when using wildcards with the "Test to see if file exists" option. (CAMP-28977)
- Fixed an issue in the File Transfer activity that could occur when updating external account settings. (CAMP-28894)
- Fixed an issue with custom filters in the query editor when using the "Email is not empty" condition. (CAMP-28741)
- Fixed an issue that could occur when exporting custom resource tables with more than 100k records. (CAMP-28150)
- Fixed an issue that prevented to delete transactional messages linked to triggers. (CAMP-28385)
- Removed passwords that were insecurely displayed in some SMS logs.
- Fixed an issue that caused the connections to the SMPP simulator to fail due to empty password sent by Adobe Campaign.
- Fixed an issue that prevented sending campaigns when SMS connections are unstable.
- Fixed an issue that displayed deleted deliveries in Dynamic reporting.
- Fixed an issue that could prevent from retrieving additional data from delivery logs, tracking logs and exclude logs tables, when using an Enrichment activity in a workflow.
- Fixed an issue with GDPR delete requests that could occur when using a "N cardinality collection link" link type and the "Deleting the target record implies deleting records references by the link" option.
- Fixed an issue with report sharing.
- Fixed an issue which could lead to throughput issues when sending a push notification.
- Fixed an issue with direct mail output files missing fields.
- Fixed an issue which allowed users to modify built-in workflows.
- Fixed an issue when creating a campaign based on a campaign template including a workflow with a configured extract activity. (CAMP-29198)
- Fixed an issue with the File extraction activity which prevented from using the same expression for several elements. (CAMP-29182)
- Fixed an issue, in the query editor, with the join condition between broadlog and tracking log for rtEvent. (CAMP-28780)
- Fixed an issue which prevented modifications to the "Specific action" landing page option from being saved. (CAMP-29422)
- Fixed an issue which prevented from exporting an event's payload in a workflow. (CAMP-29029)
- Fixed an issue that prevented blacklisted SMS numbers from being excluded in an SMS message. (CAMP-28898)
- Fixed an issue which could prevent SMPP providers from being notified in case of an error while processing incoming messages. (CAMP-29804)
- Fixed an issue which allowed external accounts with associated deliveries to be deleted. (CAMP-29738)
- The sending throughput has been improved and stabilized for SMS messages.
- Fixed an issue which prevented the "~" character from being used in an SMS message. (CAMP-29172)
- Fixed an issue in deliveries with the Send time optimization option. (CAMP-29231)