SaaS CMS has officially launched! Learn more now.

Packages [expand] [collapse]
Released in version

Release notes for Optimizely CMS and Customized Commerce updates


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
Area ID Type Description Released
  HubSpot: Replace API Key authentication with Private Apps Token

On November 30, 2022, HubSpot's API Key authentication option is no longer supported and is being replaced by Private Apps Token. See Connect for Hubspot and  Hubspot connector (CMS 12).

EPiServer.MarketingAutomationIntegration.HubSpot 4.3.0; (Or a related package);
Oct 25, 2022
  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
  Hubspot: Add Content-type header to the requests made to endpoint.

Update the Hubspot connector to place a content-type header in POST and PUT requests.

EPiServer.MarketingAutomationIntegration.HubSpot 4.1.1; (Or a related package);
Oct 18, 2020
  Hubspot: 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.HubSpot 4.1.0; (Or a related package);
Dec 09, 2018
  Hubspot: Data not updated if form submitted second time with same email

When a form mapped to Hubspot is submitted, it is only successful the first time. Subsequent submissions with the same email value are not successful.

EPiServer.MarketingAutomationIntegration.HubSpot 4.0.1; (Or a related package);
Oct 07, 2018
  Hubspot: Data not updated if form submitted second time with same email

When a form mapped to Hubspot is submitted, it is only successful the first time. Subsequent submissions with the same email value are not successful. It works fine if the email value is changed.

EPiServer.MarketingAutomationIntegration.HubSpot 3.2.1; (Or a related package);
Apr 22, 2018
  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
  HubSpot: Wrong message displayed after invalid credentials submitted

Steps to reproduce
1. Open Admin > Config > Connect for Marketing Automation page.
2. Enter invalid data into HubSpot API Key, for example, Test123.
3. Click the Save button.

A message warning about wrong credentials, as the other connectors provide.

Message appears: 'Your settings have been saved'.


EPiServer.MarketingAutomationIntegration.HubSpot 1.3.2; (Or a related package);
May 11, 2017
  Hubspot - XML comments are not being displayed in Visual Studio intellisense.

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

EPiServer.MarketingAutomationIntegration.HubSpot; EPiServer.ConnectForMarketingAutomation; (Or a related package);
Oct 02, 2016