Virtual Happy Hour this month, Jun 28, we'll be getting a sneak preview at our soon to launch SaaS CMS!

Try our conversational search powered by Generative AI!

Packages [expand] [collapse]
Released in version
5.1.3
5.1.2
5.1.1
5.1.0
5.0.0
4.6.0
4.6.0-pre
4.5.0
4.4.0
4.4.0-pre
4.3.0
4.2.1
4.2.0
4.1.0
4.0.2
4.0.1
4.0.0
3.2.0
3.1.0
3.0.0
2.0.1
2.0.0
1.3.2
1.3.1
1.3.0
1.2.1.9000
1.2.0.9000
1.1.1.9000
1.1.0.9000
1.0.8.8000
1.0.7.8000
1.0.6.8000
1.0.5

Release notes for Optimizely CMS and Customized Commerce updates

Important

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
Items/Page
Area ID Type Description Released
MAI-2086
  Acoustic (Silverpop): Add ClientId and ClientSecret for authenticationfor CMS 12

Added client ID and client secret connector fields to support changes in API authentication.

EPiServer.MarketingAutomationIntegration.Silverpop 5.1.2; (Or a related package);
Jan 24, 2023
MAI-2040
  Silverpop: Provide ability to add ClientId and ClientSecret for authentication

Created editable text fields for clientId and clientSecretclientId. 

EPiServer.MarketingAutomationIntegration.Silverpop 4.6.0; (Or a related package);
Jun 29, 2022
MAI-1893
  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; (Or a related package);
Dec 21, 2021
MAI-1886
  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
MAI-1878
  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; (Or a related package);
May 25, 2021
MAI-1766
  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; (Or a related package);
Jan 19, 2021
MAI-1635
  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; (Or a related package);
Mar 08, 2020
MAI-1761
  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; (Or a related package);
Mar 08, 2020
MAI-1557
  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.

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

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

Test configuration

EPiServer.ConnectForMarketingAutomation.4.1.0-pre-000808
EPiServer.Marketing.Automation.Forms.4.1.0-pre-000808
Episerver.MarketingAutomationIntegration.Silverpop.4.1.0-pre-000808

EPiServer.MarketingAutomationIntegration.Silverpop 4.2.0; (Or a related package);
Mar 07, 2019
MAI-1512
  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; (Or a related package);
Dec 09, 2018
1 2 Next