November Happy Hour will be moved to Thursday December 5th.

AI OnAI Off
Products
Packages [expand] [collapse]
Services
Released in version
All versions
5.1.1
5.1.0
5.0.0
4.2.0
4.1.2
4.1.1
4.1.0
4.0.0
3.3.0
3.2.0
3.1.0
3.0.0
2.0.0
1.4.2
1.4.1
1.4.0
1.3.2.9000
1.3.1.9000
1.3.0.9000
1.2.1.9000
1.1.1.9000
1.1.0.9000
1.0.8.8000
1.0.7.8000
1.0.6.8000
1.0.5

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
Clear filters
Area ID Type Description Released
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-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
MAI-1758
  Eloqua: Unable to set visitor group criteria with fields that have no value

In the Eloqua connector, for a contact, only fields with a value are being returned. As a result, visitor groups with a criterion based on a field not having a value (for example, Null or Empty) are not matched correctly.

EPiServer.MarketingAutomationIntegration.Eloqua 4.1.1; EPiServer.ConnectForMarketingAutomation 5.5.6; (Or a related package);
Mar 08, 2020
MAI-1506
  Eloqua: Form and form field mappings lost if database upgraded via web.config settings

Form and form field mappings are lost if the database is upgraded from 3.x to 4.x via the updateDatabaseSchema attribute of the <episerver.framework> element in the web.config.

EPiServer.MarketingAutomationIntegration.Eloqua 4.1.0; (Or a related package);
Dec 09, 2018
MAI-971
  MAI Connectors: Crytographic error if site deployed to server with different machine key.

If credentials are saved and the site/database is deployed to a server whose machine key is different, the site throws cryptographic error and becomes unusable.

EPiServer.ConnectForMarketingAutomation 4.0.0; EPiServer.MarketingAutomationIntegration.Eloqua 3.0.0; EPiServer.MarketingAutomationIntegration.ExactTarget 3.0.0; EPiServer.MarketingAutomationIntegration.HubSpot 3.0.0; EPiServer.MarketingAutomationIntegration.Marketo 3.0.0; EPiServer.MarketingAutomationIntegration.MSDynamics 3.0.0; EPiServer.MarketingAutomationIntegration.Pardot 3.0.0; EPiServer.MarketingAutomationIntegration.Salesforce 3.0.0; EPiServer.MarketingAutomationIntegration.Silverpop 3.0.0; Episerver.Marketing.Automation.Forms 1.1.9; (Or a related package);
Aug 13, 2017
MAI-973
  Eloqua connector does not work with RestSharp 105.2.2 and higher.

Eloqua connector does not work with RestSharp 105.2.2 and higher.

EPiServer.MarketingAutomationIntegration.Eloqua 3.0.0; (Or a related package);
Aug 13, 2017
MAI-569
  Eloqua connector appears to erase saved values of Eloqua contact database fields

If a user submitted an Eloqua form more than once, Eloqua cleared all values on default fields (such as "first name", "last name", "address line 1") that were saved for that user.

EPiServer.MarketingAutomationIntegration.Eloqua 1.4.1; (Or a related package);
Mar 05, 2017
MAI-327
  Eloqua - XML comments are not being displayed in Visual Studio intellisense.

XML comments on public methods are now displayed in Visual Studio intellisense.

EPiServer.MarketingAutomationIntegration.Eloqua 1.3.2.9000; EPiServer.ConnectForMarketingAutomation 2.4.1.9000; (Or a related package);
Oct 02, 2016