Packages [expand] [collapse]
Released in version

Release notes for Optimizely updates

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.

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
  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;
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;
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;
Dec 09, 2018
  HubSpot: Update settings UI to allow creation of multiple instances.
EPiServer.MarketingAutomationIntegration.HubSpot 4.1.0; EPiServer.ConnectForMarketingAutomation 5.3.0;
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;
Oct 07, 2018
  Create HubSpot Connector

Create Connector that uses the new framework.

Note: After upgrading the MAI package, the form may display 2 dropdown lists for selecting the mapping.
This occurs because, after the HubSpot connector updates the name of the .dll file around the MAI framework and you publish the site to another location (such as to the cloud or an IIS site), the old .dll file is not automatically deleted.

To remove the old.dll:

  1. Go to the Publish dialog.
  2. Click the Settings tab.
  3. Under File Publish Options, check Remove additional files at destination.
EPiServer.MarketingAutomationIntegration.HubSpot 4.0.0;
Jul 01, 2018
  Automate HubSpot form mapping upgrades

Automatically transform mappings in the properties table from the old format to the new one.

For the form object itself, the string value in the old format should contain the connector name. In the new format, it's a string and a couple guids. Since the guids are hardcoded for each name, this should be possible.

For field mappings, the string format is similar to forms but has additional field information. We should be able to transform with a string replace.

We should do this via database migration using epi-updatedatabase.

EPiServer.MarketingAutomationIntegration.HubSpot 4.0.0;
Jul 01, 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;
Apr 22, 2018
  MAI: Add support for CMS version 11.
EPiServer.MarketingAutomationIntegration.Eloqua 3.3.0; EPiServer.MarketingAutomationIntegration.ExactTarget 3.3.0; EPiServer.MarketingAutomationIntegration.Hubspot 3.2.0; EPiServer.MarketingAutomationIntegration.Marketo 3.2.0; EPiServer.MarketingAutomationIntegration.MSDynamics 3.2.0; EPiServer.MarketingAutomationIntegration.Pardot 3.2.0;
Jan 21, 2018
  Performance improvements for MAI
  • Improve the performance of the connectors by fetching and caching databases and lists (wherever applicable) upon site startup.
  • Add a scheduled job that fetches data at a configured interval and refreshes cached items.
  • In the Global Settings area, add a field to set cache duration.
EPiServer.ConnectForMarketingAutomation 4.2.0; Episerver.Marketing.Automation.Forms 1.3.0; EPiServer.MarketingAutomationIntegration.Eloqua 3.2.0; EPiServer.MarketingAutomationIntegration.ExactTarget 3.2.0; EPiServer.MarketingAutomationIntegration.HubSpot 3.1.0; EPiServer.MarketingAutomationIntegration.Marketo 3.1.0; EPiServer.MarketingAutomationIntegration.MSDynamics 3.1.0; EPiServer.MarketingAutomationIntegration.Pardot 3.1.0; EPiServer.MarketingAutomationIntegration.Salesforce 3.1.0; EPiServer.MarketingAutomationIntegration.Silverpop 3.1.0;
Dec 10, 2017
1 2 Next