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
  Acoustic (Silverpop) - Add fields to configure filters on how the databases and lists should be fetched.

Fields were added to the Silverpop Connector setting screen:

  • Include all lists. Enable to include all contact lists.
    Note: If enabled, Database Folder Id does not appear. If disabled, and no Database Folder Id is specified, lists are obtained from the top-level folders only, and not any subfolders.
  • Database folder Id. If specified, lists are obtained from this folder only.
EPiServer.MarketingAutomationIntegration.Silverpop 4.4.0;
May 25, 2021
  Silverpop: Update API endpoints to match platform changes

The Silverpop API endpoint Urls have changed. They have been updated in the connector accordingly.

EPiServer.MarketingAutomationIntegration.Silverpop 4.3.0;
Jan 19, 2021
  Change name of Silverpop settings page in admin mode to match others

Change the name of settings page for Silverpop from "Silverpop Engage" to "Silverpop Connector," so it matches the other connectors.

EPiServer.MarketingAutomationIntegration.Silverpop 4.2.1;
Mar 08, 2020
  SilverPop connector min framework requirement needs upgrade

The connector references a class in the newer version of the framework. This results in the following exception: Could not load type 'Episerver.Marketing.Common.Exceptions.EntityNotFoundException

EPiServer.MarketingAutomationIntegration.Silverpop 4.2.1;
Mar 08, 2020
  Silverpop: If settings saving fails, tracking script option always set to default
Steps to reproduce

1. Add an invalid value (for example, Engage Pod Number = Engage Pod 4) to an instance of the Silverpop connector.
2. Add valid values to the remaining fields (Connector name and Token).
3. Select the Custom tracking scripts option then enter a text value to the enabling textbox.
4. Click the Save button.

Once the settings fail in saving, all entering values and option should remain.

Failed for settings saving as expected. But the tracking option is set to the default: "No tracking scripts...."

Test configuration


EPiServer.MarketingAutomationIntegration.Silverpop 4.2.0;
Mar 07, 2019
  Silverpop: 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.Silverpop 4.1.0;
Dec 09, 2018
  Webtracking code only adds first connector script found

Since there can be multiple connectors of each type, we need to add the script for each connector of the same type to pages. Currently, the code only adds the first one it finds of each type.

Steps to reproduce
1) Create an Alloy sample site.
2) Install the Silverpop connector and configure it.
3) Select a custom script and enter the text "Connector 1". This text will show up on every page.
4) Programmatically create a new instance of the Silverpop connector. Set the script text to be "Connector 2".
5) View a page.

Both custom scripts exist on the page.

Only a single copy of the text shows up.

EPiServer.MarketingAutomationIntegration.Silverpop 4.0.2; EPiServer.MarketingAutomationIntegration.Marketo 4.0.1;
Sep 02, 2018
  Silverpop form mapping upgrade script may not always correctly remap contact list ids

The length of the contact list id is being calculated incorrectly in rare cases where the database id and contact list id are different lengths.

An update to the script needs to correctly determine the contact list id length. The package also needs to be updated to no longer run the old database upgrade script. This puts the form mapping into a state from which it cannot be recovered.

EPiServer.MarketingAutomationIntegration.Silverpop 4.0.1;
Jul 22, 2018
1 2 Next