This webpage describes the regular updates Acquia has made to Campaign Studio. Note that some release dates may be in the future to enable subscribers to prepare their environments for upcoming product versions.
Note
For previous release information, see the individual release note pages for 2023, 2022, 2021, and 2020.
For a list of known issues in Campaign Studio, see Known issues.
Campaign Studio - December 12, 2024
Type | Related Ticket | Release Note |
---|---|---|
Change | MAUT-11819 | Support for the following is removed from Campaign Studio:
|
Fix` | MAUT-12001 | Execution of campaign events occasionally failed because of timeout. |
Fix | MAUT-11998 | Invalid URLs did not show content of the 404 landing page but instead redirected to the 404 landing page. |
Fix | MAUT-11975 | Segment builds failed when the global timezone was configured to System Default Timezone. |
Fix | MAUT-11967 | Translation messages for Scheduled by were missing. |
Fix | MAUT-11966 | Expired campaigns triggered events for contacts. |
Fix | MAUT-11941 | Translation exceptions were not handled when the translation for the given locale was not available. |
Fix | MAUT-11857 | Publish permission was not followed when creating contacts through imports. |
Fix | MAUT-11656 | Input Field did not work for some operators of DateTime type fields in segments. |
Fix | MAUT-6104 | The Beefree Empty theme did not load an invalid CSS file on the unsubscribe page and returned a 404 response. The response was visible in the contact history. |
Campaign Studio - November 13, 2024
Type | Related Ticket | Release Note |
---|---|---|
Change | MAUT-11720 | Campaign Studio is updated to add validation for date and datetime values within segment filters and the Contact Field Value field in campaign events. |
Change | MAUT-11719 | Campaign Studio is updated to:
|
Change | MAUT-11880 | Campaign Studio is updated to apply security fixes from Mautic Community Release 4.4.13. |
Fix | MAUT-11908 | Campaign Studio did not block access to certain non-application paths. |
Fix | MAUT-11527 | When users unpublished and republished a campaign, Campaign Studio did not add any events to the existing campaign contacts that were halted because of unpublishing of the campaign. |
Fix | MAUT-11906 | A 500 error occurred when segments with a segment membership is empty filter were deleted in batch. |
Fix | MAUT-11802 | HTML tags were removed from the HTML-type field when importing a contact. |
Fix | MAUT-11799 | Special characters in the Where condition caused an issue in searching entities through a GET API request. |
Fix | MAUT-11791 | Segment filters with relative dates without explicit signs were not calculated correctly. |
Fix | MAUT-11742 | When users deleted or added the options to select and multiselect fields, Campaign Studio removed some of the previously-saved options in Custom object fields. |
Fix | MAUT-11471 | Issues occurred in displaying the Preferred channel dropdown and center-aligning the Save preferences button. |
Fix | MAUT-11383 | When users set the segment filter value to yesterday and applied the After operator to the date field, Campaign Studio generated an incorrect date value. |
Fix | MAUT-11274 | Single and double quotes in the Select type field values caused an issue in saving Custom fields. |
Fix | MAUT-6104 | The email builder incorrectly loaded a CSS file resulting in a 404 response, visible as a page hit in the contact history. |
Campaign Studio - September 26, 2024
Type | Related Ticket | Release Note |
---|---|---|
Fix | MAUT-11865 | Segment building did not happen regularly when the Birthday or Anniversary filter was used. |
Campaign Studio - September 23, 2024
Type | Related Ticket | Release Note |
---|---|---|
CHANGE | MAUT-11723 | The Delete Contact campaign action is updated to have no limits for the number of contacts it can delete. This update is made with a consideration that the action itself will not delete the contacts and their events but will mark them for deletion. Those marked contacts will be then safely deleted without negatively affecting other operations in Campaign Studio. |
CHANGE | MAUT-11677 MAUT-11678 MAUT-11702 | Campaign Studio is updated to improve usability for date ranges and relative dates in Campaign Condition > Contact Field Value. |
FIX | MAUT-11750 | Email dynamic content did not function when it was utilized as a template and then used in another email. |
FIX | MAUT-11748 | Special characters were not supported in landing pages. |
Campaign Studio - September 4, 2024
Type | Related ticket | Release note |
---|---|---|
Feature | MAUT-11725 | In segment filters, Campaign Studio includes the Including (Select) operator with a multi-select box. In the multi-select box, users can select multiple indexable custom fields of Text data type. |
Change | MAUT-11747 | Campaign Studio is updated to remove support for gated videos. |
fix | MAUT-11774 | Campaign Studio did not display thumbnail images for custom themes since the previous release. |
fix | MAUT-11765 | Dynamic content in emails did not function when a variation included a Segment Membership filter. |
fix | MAUT-10689 | In the Contact field value campaign condition, the excluding operator did not function when a select or multi-select type field was used. |
Campaign Studio - August 12, 2024
Type | Related ticket | Release note |
---|---|---|
CHANGE | MAUT-11587 | Campaign Studio is updated to display an error message if a global token is used within another global token. |
CHANGE | MAUT-11560 | Campaign Studio is updated to display an error message to prevent users from creating infinite loops in campaign restart actions. |
CHANGE | MAUT-11455 | Campaign Studio is updated to stop allowing HTML type global tokens in the Subject line of emails. |
CHANGE | MAUT-8534 | Campaign Studio is updated to display an error message for saved rows that do not fulfil the character limit requirements. |
FIX | MAUT-11679 | Users could not save campaign descriptions with multiline content. |
FIX | MAUT-11655 | Segment rebuilds did not correctly detect the value for anniversaries on the contact record. |
Fix | MAUT-11589 | Incorrect points got updated in Salesforce because of concurrency issues. |
Fix | MAUT-11559 | An error occurred when a non-admin user created a new BeeFree category. |
Fix | MAUT-11544 | Users could not log in to instances through single sign-on (SSO) because of an issue with the one-click sign-in functionality. |
Fix | MAUT-11541 | Campaign Studio did not have a mechanism to stop segment filters from saving invalid regular expressions. |
Fix | MAUT-11420 | When an email was saved, the scheduled job for sending the winner variant of the A/B test was deleted. |
Fix | MAUT-11391 | In a few cases, email tracking links were incorrectly assigned to inappropriate contacts. This fix ensures that all links are assigned appropriate contacts. |
Fix | MAUT-10724 | The campaign membership job was not executed for campaigns where the Publish Up date was set to a past date. |
Fix | MAUT-8476 | An error occurred when users created a custom object with multiple select fields. |
Fix | MAUT-8151 | Duplicate contacts were created during contact import when a contact import task was Unpublished and Published immediately. |
Campaign Studio - July 24, 2024
Type | Related ticket | Release note |
---|---|---|
CHANGE | MAUT-11561 | When Sparkpost sends webhook events with blocked status, Campaign Studio does not process them, resulting in contacts not getting marked as DNC. |
FIX | MAUT-11617 | In campaign conditions using custom objects with Date type fields, Campaign Studio did not display the date picker. |
FIX | MAUT-11616 | In campaign conditions using custom objects, Campaign Studio did not refresh the operators when the fields were changed. |
Fix | MAUT-11515 | Custom object date and time fields did not have the same operators as compared to custom fields. |
Fix | MAUT-11460 | The dynamic content variations in the email builder did not function when filters were applied on custom items. |
Campaign Studio - July 11, 2024
Type | Related ticket | Release note |
---|---|---|
CHANGE | MAUT-11636 | The email builder is updated to have the {resubscribe_url} token to allow customers to resubscribe to email communications. |
Campaign Studio - July 8, 2024
Type | Related ticket | Release note |
---|---|---|
CHANGE | MAUT-11443 MAUT-11442 MAUT-11440 MAUT-11290 MAUT-11289 MAUT-11287 | Improvements are made to segmentation usability for numerical ranges, date ranges, and relative dates. |
CHANGE | MAUT-11435 | Segment filter groups can be duplicated. |
FIX | MAUT-11467 | Segments did not work when empty or not empty operator was used with a custom object Date type filter. |
FIX | MAUT-11107 | The not equal operator did not work with custom object field filters in segments. |
Fix | MAUT-11461 | When the default language of the instance was set to Dutch and users scheduled a segment email, Campaign Studio returned an invalid date format error. |
Campaign Studio - May 30, 2024
Type | Related ticket | Release note |
---|---|---|
FEATURE | MAUT-11379 | Campaign Studio supports email preheader text. |
CHANGE | MAUT-11396 | Text type global tokens are supported in the body of text messages. |
CHANGE | MAUT-7055 | Text type global tokens are supported in email subject lines. |
CHANGE | MAUT-11380 |
|
CHANGE | MAUT-11343 | Campaign Studio displays a help text when using operators in segment filters that are not using database indexes. |
CHANGE | MAUT-10899 |
|
CHANGE | MAUT-10897 | Changes made to the Internal Name field of an email is recorded in the audit log. |
CHANGE | MAUT-7478 | Campaign Studio displays an error message if the Zoom account does not have webinars enabled. |
FIX | MAUT-11469 | The included Custom Object must be created and linked to the contact if the API request to the BULK endpoint includes the data. |
FIX | MAUT-11203 | Form fields that are mappable but were not mapped were auto-mapped when the field was edited. |
FIX | MAUT-10925 | In contact imports, Don’t overwrite value if exists was not functional for some field types. |
FIX | MAUT-6848 | Zoom Webinars with a past event dates were not available in segment filters. |
Campaign Studio - May 18, 2024
Type | Related ticket | Release note |
---|---|---|
FEATURE | MAUT-11184 | A one click unsubscribe header is added to the email if Send to unsubscribed contacts is set to No in the Advanced tab on the Emails page and if the email body contains an unsubscribed link. |
CHANGE | MAUT-8856 | Campaign Studio adds an unsubscribe link in the email body if Send to unsubscribed contacts is set to No in the Advanced tab on the Emails page. Campaign Studio does not add an unsubscribe link in the email body if Send to unsubscribed contacts is set to Yes in the Advanced tab on the Emails page. When a user manually adds an unsubscribe link to the body of an email, Campaign Studio honors this link and does not automatically remove it. |
Campaign Studio - May 11, 2024
Type | Related ticket | Release note |
---|---|---|
FIX | MAUT-11483 | Segment filters with the regex operator on the Number type custom fields did not function. |
FIX | MAUT-11485 | Segment filters did not function if the Or operator was used more than once with the Number type custom fields. |
Campaign Studio - May 3, 2024
Type | Related ticket | Release note |
---|---|---|
FIX | MAUT-11473 | CSV imports did not update the Select data type field values for existing contacts. |
Campaign Studio - April 29, 2024
Type | Related ticket | Release note |
---|---|---|
Feature | MAUT-11283 | The setting of Send to unsubscribed contacts determines whether an email is counted towards the Frequency Rule calculation.
|
Feature | MAUT-11278 | Emails with Send to unsubscribed contacts set to Yes are not sent to hard bounced email addresses. |
Feature | MAUT-11277 | Emails with Send to unsubscribed contacts set to Yes are sent to unsubscribed contacts. |
CHANGE | MAUT-11367 | Based on the setting of Send to unsubscribed contacts on the Advanced tab on the Emails page, the status of Send to unsubscribed contacts is displayed in the following:
|
CHANGE | MAUT-11334 | In the Send email campaign action dialog box, Priority and Attempt fields are displayed only if Send to unsubscribed contacts is set to No. |
CHANGE | MAUT-11324 | DNC contacts are not counted towards the Pending email status. |
CHANGE | MAUT-11323 | The Repeatable email field is added to the Send email campaign action dialog box. |
FIX | MAUT-11342 | On the Manage saved rows page in the email or landing page builder, when you edit a saved row and click the Save and Close button, the button becomes inactive and gets stuck in the Saving state. |
Fix | MAUT-11209 | When contacts were merged, the link between the contact and the custom item was lost. |
FIX | MAUT-10790 | Contacts were missing from campaigns even though they were part of a segment. |
Fix | MAUT-8383 | Unsubscribe links with a line break in an anchor tag broke contact tracking. |
Campaign Studio - March 28, 2024
Type | Related ticket | Release note |
---|---|---|
Feature | MAUT-11307 | Users can save changes of emails and landing pages by using the Save button in the email and landing page builders. |
Feature | MAUT-8113 | Campaign Studio provides the bulk delete action for global tokens. |
Fix | MAUT-11243 | The file manager in the email and landing page builders did not work appropriately when users had a large number of files. |
Fix | MAUT-11028 | Segments with custom object date filters did not rebuild correctly. |
Campaign Studio - February 22, 2024
Type | Related ticket | Release note |
---|---|---|
Feature | MAUT-10774 MAUT-10775 | Campaign Studio supports integration with Acquia DAM in the Email and Landing Page builders. |
Change | MAUT-11111 | All the deprecated plugins are unpublished and removed from Campaign Studio. |
Change | MAUT-11097 | Campaign Studio skips the broken linkages between Custom Objects and Contacts to complete the Custom Object Import process. |
Fix | MAUT-10790 | In the Campaign Build process, some contacts got skipped even when they were members of the segment associated with the campaign. |
Fix | MAUT-8637 | Salesforce sync returned an error when contacts were deleted before the sync. |
Campaign Studio - January 23, 2024
Type | Related ticket | Release note |
---|---|---|
Change | MAUT-11084 | The landing page alias supports underscore. |
Change | MAUT-8990 | Campaign Studio is upgraded to use PHP 8. |
Fix | MAUT-11037 | The Campaign Studio user interface incorrectly displayed the Contact added to segment event for contacts that were already in a segment. |
Fix | MAUT-10983 | The PATCH API in custom items incorrectly updated fields that are not part of the request payload. |
Fix | MAUT-10924 | If the Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows checkbox was selected when configuring the Campaign Studio app in Salesforce, the system displayed authorization errors in Campaign Studio. |
Fix | MAUT-10790 | Contacts in a segment were missing from the associated campaign. |
Fix | MAUT-10678 | CSV imports were saving incorrect values for select field types. |
The information contained herein is subject to change without notice and is not warranted to be error-free. If you encounter any errors, contact Acquia Support.