Latest release

This page lists new capabilities, improvements and fixes coming with the latest Campaign v8 Release.

Release 8.4.3

CAUTION

Client Console upgrade is mandatory. Learn how to upgrade your Client Console in this page.

January 27, 2023

Improvements

  • Fixed a delivery indicator synchronization issue between the marketing server and the mid-sourcing server. (NEO-50724)
  • Fixed an issue which could lead to an error when exporting a workflow. (NEO-50555)
  • Fixed an issue when extending a schema that was previously extended. (NEO-49118)
  • Fixed an issue when using two enrichment activities with the same identifier in the link definition. (NEO-48851)
  • Fixed two delivery preparation failure issues. Delivery preparation could fail when the number of potential offers being manipulated was too high. The second issue occurred when the image URLs were defined as URLs to track in a text format delivery. (NEO-48807)
  • Fixed an issue which could lead to a workflow failure where a workflow would overwrite the warehouse name defined in the external account for non-FFDA accounts. (NEO-43209)
  • Improved security on web applications to prevent DDoS attacks. (NEO-50757)
  • The management of consolidated tracking data has been improved in the Consolidated tracking (nms:trackingStats) FFDA table to avoid duplicates. (NEO-46409)
  • Fixed a logical operator issue in workflow queries when using an enableIf in a logical operator condition. The previous logical condition was overwritten. (NEO-45815)
  • The generation of active profiles has been optimized in the billing workflow to improve performance. (NEO-47658)
  • Fixed an issue with HTML file import when image nodes (img) contained URLs with personalization fields. (NEO-48396)
  • Fixed an issue with Snowflake (all deployments) when using the sorting parameter in a Split workflow activity. (NEO-45899)
  • Fixed an issue that led to an error when a user with read access rights on the nmsDeliveryMapping folder tried to run a campaign or workflow. (NEO-48230)
  • Fixed a performance issue in the HTML tab of a delivery which could occur for large HTML code. (NEO-47440)
  • Fixed an issue which prevented users from using the Merge selected lines workflow option. (NEO-48488)
  • Fixed an issue on Snowflake FDA connector which led to records being dropped when using the “0 or 1 cardinality simple join” option during enrichment. (NEO-48737)
  • The remaining references to the log4j library have been removed from the Campaign installation on Windows. (NEO-44851)
  • Fixed an issue which could lead to an error when adding the Recipients who have opened (estimatedRecipientOpen) indicator in the additional data of a Query workflow activity. (NEO-46665)
  • The management of tracking URLs has been improved in workflows with multiple deliveries to improve performance. (NEO-50894)
  • Fixed an issue which could cause the replication of schemas that uses Xtkfolder to fail. (NEO-46787)
  • Fixed an issue cause could cause the “lastModified” custom column to be dropped in the NmsSubscription table. (NEO-48402)

Release 8.4.2

October 28, 2022

Improvements

  • Fixed an issue which prevented the Success delivery indicator from being updated correctly when using Adobe Campaign Enhanced MTA. (NEO-50462)

Release 8.4.1

September 30, 2022

What’s new?

Adobe Campaign integration with Adobe Experience Platform

New destination and source connectors are now available to allow seamless integration between Adobe Campaign and Adobe Experience Platform:

  • Use Adobe Campaign Managed Cloud Services destination connector to send Experience Platform segments over to Adobe Campaign for activation,
  • Use Adobe Campaign Managed Cloud Service source connector to send Adobe Campaign delivery and tracking logs over to Adobe Experience Platform.

For more information, refer to the detailed documentation.
Twitter channel availability

The Twitter social channel is now available with Campaign v8. You can:

  • Send messages on Twitter: Adobe Campaign lets you post messages directly to your twitter account. You can also send direct messages to all your followers.

  • Collect new contacts: Adobe Campaign can automatically recovers the profile data, which enables you to carry out targeting campaigns and implement cross-channel strategies.

Learn how to connect Campaign and Twitter in the detailed documentation.

Learn how to post tweets and send direct messages with Campaign in this page.

Security enhancement

To optimize security, security tokens have been removed from URLs generated by Campaign:

  • This change only applies to GET URLs. Other types, including POST URLs, are not affected.

  • If you use custom code, security tokens are not retrieved from the GET URL securitytoken parameter anymore. You have to generate a new security token using the following JSSP code:

    getNewSecurityToken(jsspContext.getSessionToken(), jsspContext.getSecurityToken(), true);

    You can also use the Login API to fetch security tokens.

  • There is no change in session token management.

Improvements

  • Following the end of life of Microsoft Internet Explorer 11, the HTML rendering engine in the console is now using Microsoft Edge Chromium. Additionally, installation of Microsoft Edge WebView 2 runtime is now required for any client console installation.
  • Improved workflow execution with Workflow high availability which allows you to run simultaneous workflows across different containers to prevent the loss of workflow service and avoid related execution errors. Note: This new capability is released in Limited Availability to a set of customers only.
  • Privacy requests are now performed in batch for a given privacy namespace. This improvement increases execution time for GDPR/privacy delete requests.

Compatibility updates

  • Campaign v8 SDK now supports iOS 16 for Push Notifications.

Refer to the Campaign Compatibility matrix.

Patches

  • Fixed an issue which impacted the Delivery log status updates on the MID instance, when the FeatureFlag_GZIP_Compression option was enabled. (NEO-49183)
  • Fixed an issue which could lead deliveries to stay in Pending status even if contact date was reached. (NEO-48079)
  • Fixed an issue in workflows which could prevent files from being updated on server when using the Data loading (file) activity. The process stopped at 100% but never ended. (NEO-47269)
  • Fixed an issue during postupgrade on japanese environments. (NEO-46640)
  • Fixed an issue that could occur if a delivery reached a precise size during MTA process. (NEO-46097)
  • Fixed an issue which prevented tracking logs from returning data related to the recipient’s browser. (NEO-46612)
  • Fixed an issue which led to personalization issues when sending SMS messages using an external delivery mode. (NEO-46415)
  • Fixed an issue which could generate duplicates in tracking logs. (NEO-46409)
  • Fixed an issue which prevented the Replicate Staging data (ffdaReplicateStagingData) technical workflow from stopping even when an error occurred during its execution. (NEO-46280)
  • To prevent slowness when sending proof to seed addresses, all consecutive replications of seed members are now grouped to one replication request. (NEO-44844)
  • Fixed an issue which displayed an error when trying to preview a delivery in any Message Center archived event. (NEO-43620)
  • Fixed an issue when injecting data into Snowflake cloud database with a Campaign Query activity and a Change Data Source activity: the process was failing when a backslash character is present in the data. The source string was not escaped, and data was not processed correctly on Snowflake. (NEO-45549)
  • Fixed an issue when using the Query activity and filtering a table. When a column name contained the word “Update”, a compilation error occured with an invalid identifier and the following message: “number of rows updated”. (NEO-46485)
  • The Database cleanup technical workflow now also handles custom staging schemas. (NEO-48974)
  • Fixed an issue which could slow down the delivery analysis, during the exclusion of denylisted recipients step, when targeting large volumes of recipients. (NEO-48019)
  • Improved stability when handling invalid XML strings during SOAP calls. (NEO-48027)
  • Fixed an issue which led to the creation of unnecessary DeliveryParts when the delivery was using calendar and split modes. (NEO-48634)
  • Fixed a performance issue when using calendar-based waves. (NEO-48451)
  • Fixed an issue which could lead to an error message in the delivery list screen after creating a new target mapping on a custom schema. (NEO-49237)
  • Fixed an issue which could cause data loss if the staging workflow was in error and the retention period fully passed. (NEO-48975)

Release 8.3.9

CAUTION

Client Console upgrade is mandatory. Learn how to upgrade your Client Console in this page.

October 7, 2022

Improvements

  • Fixed an issue which impacted the Delivery log status updates on the MID instance, when the FeatureFlag_GZIP_Compression option was enabled. (NEO-49183)
  • The Database cleanup technical workflow now also handles custom staging schemas. (NEO-48974)
  • Fixed an issue which could lead deliveries to stay in Pending status even if the contact date was reached. (NEO-48079, NEO-48251)
  • Improved stability when handling invalid XML strings during SOAP calls. (NEO-48027)
  • Fixed an issue which could slow down the delivery analysis, during the exclusion of denylisted recipients step, when targeting large volumes of recipients. (NEO-48019)
  • To prevent slowness when sending proof to seed addresses, all consecutive replications of seed members are now grouped into one replication request. (NEO-44844)
  • Fixed an issue which led to personalization issues when sending SMS messages using an external delivery mode. (NEO-46415)
  • Fixed an issue which displayed an error when trying to preview a delivery in any Message Center archived event. (NEO-43620)
  • Fixed an issue in workflows which could prevent files from being updated on server when using the Data loading (file) activity. The process stopped at 100% but never ended. (NEO-47269)
  • Fixed an issue which led to the creation of unnecessary DeliveryParts when the delivery was using calendar and split modes. (NEO-48634)
  • Fixed a performance issue when using calendar-based waves. (NEO-48451)
  • Fixed an issue which could lead to an error message in the delivery list screen after creating a new target mapping on a custom schema. (NEO-49237)
  • Fixed an issue that could occur if a delivery reached a specific size during MTA process. (NEO-46097)
  • Fixed an issue which prevented tracking logs from returning data related to the recipient’s browser. (NEO-46612)
  • Fixed an issue during postupgrade on Japanese environments. (NEO-46640)
  • Fixed an issue when using the Query activity and filtering a table. When a column name contained the word “Update”, a compilation error occurred with an invalid identifier and the following message: “number of rows updated”. (NEO-46485)
  • Fixed an issue which prevented the Replicate Staging data (ffdaReplicateStagingData) technical workflow from stopping even when an error occurred during its execution. (NEO-46280)
  • Fixed an issue which could cause data loss if the staging workflow was in error and the retention period fully passed. (NEO-48975)
  • Fixed an issue when injecting data into Snowflake cloud database with a Campaign Query activity and a Change Data Source activity: the process was failing when a backslash character is present in the data. The source string was not escaped, and data was not processed correctly on Snowflake. (NEO-45549)

Release 8.3.8

May 18, 2022

What’s new?

Time Sensitive notifications

With iOS 15, Apple added a notion of sensitive notification that gives control to the app developer to bypass Focus mode when a notification is considered as sensitive and then needs to reach the user in real-time.

For more information, refer to the detailed documentation.
Core Privacy Service Integration

Campaign v8 now integrates with Adobe Privacy Core Service. Privacy requests pushed from the Privacy Core Service to all Experience Cloud solutions are automatically handled by Campaign via a dedicated workflow.

For more information, refer to the detailed documentation.
Response Manager

Campaign Response Management lets you measure the success and ROI of your marketing campaigns or offer propositions across all channels: email, mobile, direct mail, etc.

For more information, refer to the detailed documentation.
Distributed Marketing

Campaign Distributed Marketing lets you implement collaborative campaigns between central entities (headquarters, marketing departments, etc.) and local entities (sales points, regional agencies, etc.). Through a shared workspace (campaign packages), you can create campaign templates and propose them to your local entities.

For more information, refer to the detailed documentation.

Compatibility updates

  • Campaign v8 SDK now supports Android 12 and iOS 15 for Push Notifications.
  • Campaign v8 is now compatible with Windows 11.

Refer to the Campaign Compatibility matrix.

Improvements

  • Microsoft Exchange Online OAuth 2.0 authentication for POP3 is now supported in Campaign. Read more
  • Critical fixes have been applied regarding the Microsoft Dynamics Connector web API.
  • The new Operator and group schema write (operatorWrite) named right has been added to allow users to insert, update and delete Operators (xtk:operator) and Operator groups (xtk:group) schemas.
  • Multiple LINE active accounts can now be configured on a single mid-sourcing.
  • The number of default connections for the web process has been increased from 50 to 150.
  • Campaign comes with a set of new guardrails to prevent insertion of duplicated keys in Snowflake database. Read more

Patches

  • Fixed an issue which occurred when using seeds and control groups in the same recurring delivery. (NEO-41197)
  • Fixed an issue on FFDA which led to email sending being blocked for all récipients belonging to the same deliveryPart during the sending process (up to 256) when personalization blocks contained one of the following characters: ' & < > ". These characters are now supported in personalization blocks (example: firstname=“Brian O’Neil”). (NEO-43184)
  • Fixed an issue which could lead the tracking workflow to fail when using a custom schema as a target mapping. We now ensure that the type of the foreign link to a custom targeting schema is correct when generating broadLog schema via the target mapping wizard. (NEO-43506)
  • Fixed an issue which could lead the FFDA deployment workflows to fail for languages other than English. (NEO-44561)

Release 8.2.10

February 2, 2022

Patches

  • Fixed an issue which caused the delivery preparation to fail if the maximum number of messages, defined in the typology rule, was reached.
  • Fixed an issue during the configuration of the Adobe Analytics connector when the email address contained an “s” character.
  • Fixed an issue during postupgrade which could cause the deliveryMapping table to lose data from a custom delivery mapping.
  • Fixed an issue which could lead to recipients receiving the same message multiple times for the same delivery when the email address contained a single quote character ('). This character is now escaped. (NEO-41198)
  • Fixed an ID generation issue when sending proofs with seeds or substitution addresses. (NEO-42637)
  • Fixed an issue which could prevent you from sending proofs using the substitution of address method. (NEO-40417)
  • Fixed an issue which prevented you from installing the LINE package. (NEO-42503)

Release 8.2.8

October 28, 2021

Inbound Interaction

Real-time interaction management is now available for inbound channels. Use Campaign Inbound Interaction module to present the best offer to your customers as they visit your website or reach out to your call center. This capability comes with Campaign v8 as an option and requires specific configuration on your instance. Reach out to your Adobe representative to have access to the Inbound Interaction module.

For more information, refer to the detailed documentation.
Campaign Optimization

Campaign Optimization module is now available. This module lets you control, filter and monitor the sending of deliveries. To avoid conflicts between campaigns, Adobe Campaign can test various combinations by applying specific constraint rules. This guarantees that the messages sent meet the needs and expectations of customers and company communication policies.

For more information, refer to the detailed documentation.
Unicity Service

Unicity Service is a new Cloud Database Manager component. It helps users preserve and monitor the integrity of unique key constraints within Cloud Database tables. This allows you to reduce the risk of inserting duplicate keys.

As Cloud Database does not enforce unicity constraints, Unicity Service introduces at application level, a set of new guardrails reduce the risk of inserting duplicates when managing the data with Adobe Campaign.

Unicity Service initiates a new built-in workflow called ffdaUnicity to monitor unicity constraints and alert when duplicates are detected.

For more information, refer to the detailed documentation.

Improvements

  • The Snowflake connector has been improved in terms of performance.
  • For monitoring and testing purposes, the audit logs of the Replicate Staging data workflow now include the number of records that have been sent to the FFDA (Full Federated Data Access) database.
  • The SQL code activity now allows you to choose in which database the SQL script will be stored: the default data source or a chosen active FDA external account.
  • A set of pre-defined warehouses is now available and can be used to run various queries in parallel such as segmentation, ETL or peaks. Read more

Other changes

  • The Encrypted identifier field has been added to the visitor schema (nms:visitor). This field is calculated and is to be used for web applications.
  • Fixed an issue that caused the delivery analysis to fail when some IP affinities existed in some mid-sourcing containers but not in all of them. Now the IP affinities are all stored in the database, so that any container can access the affinities present in all the other containers. (NEO-37564)
  • You can now import a package with multiple schemas and navigation tree nodes.

Patches

  • After a user had removed, in a data schema, the <autoStg> attribute from a table definition element, or changed its value from true to false, the related staging table was not deleted. This issue has been fixed.
  • Fixed an issue that caused an error when creating records with a dedicated form due to Id management with an FFDA datasource.
  • Fixed an issue that could prevent offers from being inserted into a delivery if the offers were managed by an enrichment activity in a workflow.
  • Fixed an issue that could slow down the import of packages.
  • Fixed an issue that could prevent email deliveries with seed addresses from being sent.
  • Fixed an issue that could prevent propositions from being saved in the offer propositions table.
  • Fixed an issue that caused network timeout issues to be incorrectly logged as script interruption issues instead of network errors. This issue occurred in the case of HTTP requests that were included in JavaScript activities.
  • Fixed an issue that prevented offers from being replicated to the live offer environment on Snowflake.
  • Fixed an issue that ignored the ‘autoStg’ attribute for non-extended built-in schemas.
  • Fixed an issue that prevented users from selecting the Country/Region link when previewing a profile.
  • Fixed an issue that caused the datepicker in custom reports to result in a script error. (NEO-36345)
  • Fixed an issue that caused the system to crash when regenerating configuration in case of bad configuration files.
  • Fixed an issue that prevented the marketing and the control instances from being successfully upgraded.
  • Fixed an issue that could cause the billing workflow to crash on marketing instances.
  • Fixed an issue that could lead to duplicate keys in FFDA Snowflake out-of-the-box tables. (NEO-38583)
  • Fixed an issue which could lead to workflow temporary schemas being lost when editing two deduplication activities one after the other. (NEO-34063)
  • Fixed an issue that returned incorrect results when running the Amazon Redshift HoursDiff and MinutesDiff functions while trying to extract the time component.(NEO-31673)
  • Fixed an issue which could prevent users from login to the console due to a proxy configuration issue. (NEO-38388)
  • Fixed a regression issue which prevented the Purge folder functionality from working correctly. (NEO-37459)
  • Fixed an issue that could prevent you from previewing mobile deliveries that were attached to a workflow.
  • Fixed an issue which could prevent the Read list workflow activity from working when the list was identified in the database with a negative ID. (NEO-39607)

Release 8.1.20

September 7, 2021

Security enhancements

  • Fixed a security issue to reinforce protection against directory traversal attacks. (NEO-28547)

Improvements

  • Following its end of life, Flash has been removed from all related Campaign features and components, and replaced with HTML5. The Gauge type of chart has been removed. (NEO-30330) Read more
  • When installing the client console on Windows, the installer now checks if there is a parent registry node and creates one if it is missing. This prevents potential issues when launching the console. (NEO-34854)
  • The tracking signature feature has been improved to prevent errors linked to the way third-party tools (email clients, internet browsers, etc.) handle special characters. URL parameters are now encoded.

Other changes

  • Previously deprecated Microsoft CRM connectors (Office 365 and on-premise deployments) have been removed from the interface. Read more
  • Following the migration to Tomcat 8, the IIS setup script has been updated to fix IIS integration issues. (NEO-31019)
  • A guardrail has been added to only allow the billing technical workflow to run on the marketing instance.
  • The data source identification has been improved in the data and schema tabs of the workflow transitions’ View population window.
  • Missing database indexes were added to the following schemas to prevent database update issues: xtk:rights, nms:dlvExclusion, nms:seedMember, nms:trackingUrl

Patches

  • Fixed an issue which prevented the Hot clicks report from working when offers were linked to the delivery. (NEO-26295)
  • Fixed an issue with the Sub-worfklow activity when its execution did not generate an output table. (NEO-36242)
  • Fixed various issues when exporting the Descriptive analysis report to PDF. (NEO-25847)
  • Fixed an issue which could lead to deliveries failing when using an external mail delivery. (NEO-37435)
  • Fixed an error when connecting to Microsoft CRM using web API. The error message has been removed since functionalities were not impacted.
  • Fixed a tracking log deduplication issue when the mid server was set as a relay between tracking and marketing servers. (NEO-36285)
  • Fixed a regression which prevented Vault from being used as a specific code store.
  • Fixed an issue which prevented you from using variables in an Enrichment workflow activity when the incoming transition was from an FDA data source.
  • Fixed an issue with FFDA preventing the proper replication of operator groups and rights.
  • Fixed an issue which could result in sending an incorrect unsubscription link through the delivery.
  • Fixed an issue in replication management impacting the duration of the postupgrade.
  • Fixed an issue which could prevent the Hot click from displaying.
  • Fixed an issue that could lead to broken URLs in email messages.

Release 8.1.14

July 23, 2021

What’s new?

New workflow activity: Change Data Source

The new Change Data Source workflow activity allows you to change the data source of a workflow's working table. This provides enhanced flexibility in managing data across different data sources (FDA, FFDA & local database).

In Adobe Campaign workflows, data is managed using working (or temporary) tables. As the workflow executes, working tables share data across workflow activities. By default, working tables are created on the same database as the source of the data we query on.

With Campaign v8, the main profiles table is stored on the cloud database directly. So querying on the Profiles table will create a working table on the cloud database as well. In certain cases, it can make sense to move the working table to another data source in order to perform specific operations.

For more information, refer to the detailed documentation.
LINE channel availability

The LINE channel is now available with Campaign v8, including the following enhancements when combined with the transactional messaging module:

  • Fixed an issue which could prevent visitors from being targeted in a LINE delivery.

  • Fixed an issue which could cause errors when retrieving visitors from the execution instance to the marketing instance.

  • Fixed issues during the processing of real-time events.

Other improvements

  • Fixed an issue which could prevent the Hot clicks report from displaying for specific deliveries.
  • Fixed an issue with the Deduplication workflow activity which could result in an inaccurate duplicate counting.
  • Fixed an issue when using a workflow query with the “ID is not empty” filter which could result in an empty item being displayed in the transition population.
  • Fixed an issue which prevented additional fields from being created in a new target mapping.

On this page