Virtual Happy Hour this month, Jun 28, we'll be getting a sneak preview at our soon to launch SaaS CMS!

Try our conversational search powered by Generative AI!

Packages [expand] [collapse]
Released in version
6.1.5
6.1.4
6.1.3
6.1.2
6.1.1
6.1.0
6.0.0
5.7.2
5.7.1
5.7.0
5.6.3
5.6.2
5.6.1
5.6.0
5.5.6
5.5.5
5.5.4
5.5.3
5.5.2
5.5.1
5.5.0
5.4.0
5.3.4
5.3.3
5.3.2
5.3.1
5.3.0
5.2.2
5.2.1
5.2.0
5.1.0
5.0.2
5.0.1
5.0.0
4.4.2
4.4.1
4.4.0
4.3.1
4.3.0
4.2.0
4.1.0
4.0.0
3.0.0
2.5.1
2.5.0
2.4.2.9000
2.4.1.9000
2.4.0.9000
2.3.0.9000
2.2.2.9000
2.2.1.9000
2.2.0.9000
2.1.0.9000
2.0.3.8000
2.0.2.8000
2.0.1.8000
2.0.0.8001
1.2.1.8000
1.2.0.8000
1.1.9.7192
1.1.7.7518
1.1.6.7514

Release notes for Optimizely CMS and Customized Commerce updates

Important

Release notes moved to a new location. As of May 15th, 2024, the release notes on the World site no longer receive updates. See Release notes by product on the Optimizely Support site.

Go to your product's release notes page and click Follow to receive an email notification whenever release notes are added.

This topic lists Optimizely updates, delivered as NuGet packages and services. You decide which updates apply to your project.

Select a product, package, or service in the left menu, and then select one of the following filters from Item type and click Filter.

  • Bug – Display bug fixes.
  • Critical bug – Display only critical bug fixes.
  • Feature –  Display only new features (all features).
  • UI Feature – Display only end-user (user interface) features.
  • Security - Display only security updates.

Note: NuGet packages listed here may not be immediately available in the Optimizely NuGet feed.

Latest changes

Item type
Filter on date
Items/Page
Area ID Type Description Released
MAI-2190
  Marketing Automation Connectors Scheduled Job: Improve error handling CMS 11

Improved error handling and logging.

EPiServer.ConnectForMarketingAutomation 5.7.2; (Or a related package);
May 14, 2024
MAI-2191
  Marketing Automation Connectors Scheduled Job: Improve error handling CMS 12

Improved error handling and logging.

EPiServer.ConnectForMarketingAutomation 6.1.5; (Or a related package);
May 14, 2024
MAI-2133
  CMS 12 Salesforce: Excessive failed login attempts.

Fixed an issue that could cause a crash if an excessive number of login requests occur, such as invalid saved credentials become invalid (due to expired password, security token reset and so on); the login request to Salesforce fails and throws an exception with the message "invalid_grant".

EPiServer.Marketing.Automation.Forms 3.1.3; EPiServer.MarketingAutomationIntegration.Salesforce 5.1.3; EPiServer.ConnectForMarketingAutomation 6.1.4; (Or a related package);
Oct 03, 2023
MAI-2129
  CMS 11 Salesforce: Excessive failed login attempts.

Fixed an issue in the Salesforce connector, which was making an excessive number of authentication calls when credentials became invalid.

EPiServer.MarketingAutomationIntegration.Salesforce 4.3.3; EPiServer.ConnectForMarketingAutomation 5.7.1; Episerver.Marketing.Automation.Forms 2.4.2; (Or a related package);
Sep 01, 2023
MAI-2118
  Marketing Connector Criteria disappeared after upgrading to CMS 12.15

Fixed an issue where Marketing Connector Criteria disappeared after you upgraded to CMS 12.15.

EPiServer.ConnectForMarketingAutomation 6.1.3; (Or a related package);
Aug 31, 2023
MAI-1893
  Upgrade marketing automation connectors to .NET 5

Upgraded the following marketing automation connectors to support Optimizely Content Cloud version 12 (CMS 12). 

  • Acoustic (Silverpop)
  • Delivra
  • Eloqua
  • Marketo
  • Microsoft Dynamics CRM
  • Salesforce
  • Salesforce Marketing Cloud (ExactTarget)

The following connectors will be released at a later date.

  • Hubspot
  • Pardot
EPiServer.MarketingAutomationIntegration.MSDynamics 6.0.0; EPiServer.MarketingAutomationIntegration.Silverpop 5.0.0; EPiServer.MarketingAutomationIntegration.Salesforce 5.0.0; EPiServer.MarketingAutomationIntegration.Marketo 5.0.0; EPiServer.MarketingAutomationIntegration.ExactTarget 5.0.0; EPiServer.MarketingAutomationIntegration.Eloqua 5.0.0; EPiServer.Marketing.Connector.Delivra 2.0.0; EPiServer.Marketing.Automation.Forms 3.0.0; EPiServer.ConnectForMarketingAutomation 6.0.0; (Or a related package);
Dec 21, 2021
MAI-1886
  Allow user to accept or deny mai_trk_* cookies

In accordance with GDPR regulations, you can choose whether you want to accept cookies for Marketing Automation connectors. (Normally, the cookie is created when you submit a marketing automation form.)

Customers are responsible for presenting the cookie option dialog box to the user, obtaining the response, and then passing the response to Optimizely through the IPersonalizationEvaluator.AcceptCookies property. If the user chooses not to accept the cookies, some or all functionality of the connector will not work; the form will post successfully but personalization features will not.

EPiServer.ConnectForMarketingAutomation 5.7.0; EPiServer.Marketing.Automation.Forms 2.4.0; EPiServer.Marketing.Connector.Delivra 1.2.0; EPiServer.MarketingAutomationIntegration.Eloqua 4.2.0; EPiServer.MarketingAutomationIntegration.ExactTarget 4.3.0; EPiServer.MarketingAutomationIntegration.HubSpot 4.2.0; EPiServer.MarketingAutomationIntegration.Marketo 4.6.0; EPiServer.MarketingAutomationIntegration.Salesforce 4.3.0; EPiServer.MarketingAutomationIntegration.Silverpop 4.5.0; (Or a related package);
Jul 20, 2021
MAI-1871
  MAI Connectors: Use absolute expiration when caching entity data.

The MAI connectors store entity data in a cache with a sliding expiration of 10 minutes.
This causes an issue where if the data is updated directly on the provider portal itself (as opposed to updating via form submission), it won't be reflected on personalized blocks and form auto-fill unless the cache is not accessed in the cache expiration interval of 10 minutes.

This behavior has been changed from version 5.6.3, by setting the cache to expire after a fixed interval of 10 minutes.

EPiServer.ConnectForMarketingAutomation 5.6.3; (Or a related package);
Mar 23, 2021
MAI-1852
  Marketing connectors: Error occurred when duplicate fields were present on visitor group fields.

When you configured a visitor group, an error occurred if duplicate field names were present in the marketing provider.

EPiServer.ConnectForMarketingAutomation 5.6.2; (Or a related package);
Nov 03, 2020
MAI-1851
  Eloqua: When Account Name is a separate contact field, datasources are not displayed.

In Eloqua, the Company field is mapped to the accountName parameter. If you have both Company and accountName fields in your Eloqua instance, an error occurs.

Note: To map a form field to Company, use the accountName field from the datasources dropdown.

EPiServer.MarketingAutomationIntegration.Eloqua 4.1.2; EPiServer.Marketing.Automation.Forms 2.3.1; EPiServer.ConnectForMarketingAutomation 5.6.1; (Or a related package);
Oct 20, 2020
1 2 3 4 5 Next