Products
Packages [expand] [collapse]
Services
Released in version
All versions
5.1.0
5.0.0
4.2.0
4.1.2
4.1.1
4.1.0
4.0.0
3.3.0
3.2.0
3.1.0
3.0.0
2.0.0
1.4.2
1.4.1
1.4.0
1.3.2.9000
1.3.1.9000
1.3.0.9000
1.2.1.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 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
Items/Page
Clear filters
Area ID Type Description Released
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;
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;
Jul 20, 2021
MAI-1851
  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
MAI-1758
  Eloqua: Unable to set visitor group criteria with fields that have no value

In the Eloqua connector, for a contact, only fields with a value are being returned. As a result, visitor groups with a criterion based on a field not having a value (for example, Null or Empty) are not matched correctly.

EPiServer.MarketingAutomationIntegration.Eloqua 4.1.1; EPiServer.ConnectForMarketingAutomation 5.5.6;
Mar 08, 2020
MAI-1194
  Eloqua: Provide option to authenticate using clientId and clientSecret (OAuth 2.0).
EPiServer.MarketingAutomationIntegration.Eloqua 4.1.0;
Dec 09, 2018
MAI-1374
  Eloqua: Update settings UI to allow creation of multiple instances.
EPiServer.MarketingAutomationIntegration.Eloqua 4.1.0; EPiServer.ConnectForMarketingAutomation 5.3.0;
Dec 09, 2018
MAI-1506
  Eloqua: 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.Eloqua 4.1.0;
Dec 09, 2018
MAI-1125
  Create Eloqua Connector
EPiServer.MarketingAutomationIntegration.Eloqua 4.0.0;
Jul 29, 2018
MAI-1034
  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
MAI-1027
  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