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
  Delivra connector: Show the member fields by their display names in form mappings and visitor group UIs.

Delivra Connector: Form field mapping and visitor groups UIs should show display names of fields.

EPiServer.ConnectForMarketingAutomation 5.6.0; EPiServer.Marketing.Automation.Forms 2.3.0; EPiServer.Marketing.Connector.Delivra 1.1.0;
Jun 28, 2020
  Option to prevent form submission; display message if submission of form data to connector fails

Currently, if the submission of form data to a marketing connector to create/update an entity is unsuccessful, it logs an error but still shows a success message in the UI. Also, the form submission is recorded in the Epi database.
Provide an option via the Admin settings to choose a different behavior, such that the error is displayed in the UI, and the form submission is not recorded in the database.

EPiServer.ConnectForMarketingAutomation 5.5.0; EPiServer.Marketing.Automation.Forms 2.2.0;
Sep 01, 2019
  MAI Core: Returning actor's result

The latest version EPiServer.Forms, 4.16, has a feature that allows submission actors to:

  • Return a signal to cancel the form submission if the actor running fails
  • Return an error message that can be displayed to a visitor

This story updates the MAI Core so that the Marketing Connector Actor can cancel the form submission and return an error message if it fails to run.

EPiServer.ConnectForMarketingAutomation 5.2.0; EPiServer.Marketing.Automation.Forms 2.1.0;
Sep 30, 2018
  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
  Support for EPiServer Tiny MCE 2.0

We need to eliminate the package dependency, as one of our customers has purchased Campaign but is using the new Tiny MCE editor package, so they can't use Campaigns.
This means

  1. Deleting the DynamicContent view and folder.
  2. Striking the reference from the nuspec.
  3. Validating that it can be installed with the new Tiny MCE without error.

We should increment the minor for this, so it would be 4.5.

EPiServer.Marketing.Automation.Forms 2.0.0;
Jun 21, 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
1 2 3 Next