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
  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;
Dec 21, 2021
  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
  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;
Oct 20, 2020
  Form's data cannot be submitted to external system if the first form element is not mapped to any remote field

Steps to reproduce:

1. Create a form and map it with a remote datasourse:

2. Add some fields to the form and map them to corresponding fields in the remote datasource, EXCEPT the first field:

3. Add the form to a page, then open the page and submit the form.

Actual result: Form's data is not submitted to the external datasource
Expected result: Form's data is submitted to the external datasource

EPiServer.Marketing.Automation.Forms 2.0.1;
Sep 02, 2018
  Form Mapping - The main datasource should be listed first in the dropdown.

Currently, the submission targets are listed first followed by the main datasource. It should be the other way around.

EPiServer.Marketing.Automation.Forms 2.0.1;
Sep 02, 2018
  MAI: Error if form fields not mapped to corresponding field(s) in installed connector

Steps to reproduce:

  1. Set up the automation connector (with "Enable Auto-fill on forms" turned on).
  2. Create an Episerver form that connects to the Contact table.
  3. Set up field mapping.
  4. Input sample data and submit.
  5. See data sent to Hubspot.
  6. Drag more form elements to the form, use settings by default, no field mapping setting.
  7. Open the page that contains the form in view mode.

Expected: The page opens as normal.

Actual: The page shows an exception.

Note: The form works normally if "Enable Auto-fill on forms" is turned off.

EPiServer.Marketing.Automation.Forms 1.4.3;
Apr 22, 2018
  MAI: Improve caching of forms-MAI integration package

Episerver made improvements to the performance and caching of MAI connectors.

EPiServer.Marketing.Automation.Forms 1.4.2;
Apr 15, 2018
  Null reference error if IElementCustomFormatValue elements submitted without entering values

If a form contained IElementCustomFormatValue elements (NumberElement, DateTimeRangeElement) and values were not entered for them, a Null Reference exception occurred. Null values are now checked so they no longer cause the exception.

EPiServer.Marketing.Automation.Forms 1.4.1; EPiServer.Marketing.Automation.Forms 1.3.1;
Mar 04, 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;
Aug 13, 2017
  The last value (and hidden fields) are populated with the last values even through the form is a different form

PreDefinedHiddenElement and VisitorDataHiddenElement were pre-filled on forms mapped to MAI connectors, which created issues. (They are no longer pre-filled.)

EPiServer.Marketing.Automation.Forms 1.1.5;
Feb 05, 2017
1 2 Next