Packages [expand] [collapse]
Released in version
5.1.0
5.0.0
4.6.0
4.5.0
4.4.0
4.3.0
4.2.0
4.1.0
4.0.4
4.0.3
4.0.2
4.0.1
4.0.0
3.2.5
3.2.4
3.2.3
3.2.2
3.2.1
3.2.0
3.1.1
3.1.0
3.0.1
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.0.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
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-1857
  Marketo: Add method to schedule campaigns in the REST Service API.

Add method to schedule campaigns in the REST Service API.

EPiServer.MarketingAutomationIntegration.Marketo 4.5.0;
Dec 29, 2020
MAI-1530
  Marketo: Form field mapping for custom fields lost when upgrading from 3.x to 4.x.

Form field mapping for custom fields lost when upgrading from 3.x to 4.x.

EPiServer.MarketingAutomationIntegration.Marketo 4.0.4;
Nov 06, 2018
MAI-1493
  Marketo: Error while fetching lead if large number of fields

While attempting to fetch a lead with a large number of fields, the Marketo connector results in an error.
"System.Net.WebException: The server committed a protocol violation. Section=ResponseStatusLine".

EPiServer.MarketingAutomationIntegration.Marketo 4.0.3;
Oct 21, 2018
MAI-1465
  Marketo: 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.Marketo 4.0.2;
Oct 07, 2018
MAI-1332
  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.

Expected:
Both custom scripts exist on the page.

Actual:
Only a single copy of the text shows up.

EPiServer.MarketingAutomationIntegration.Silverpop 4.0.2; EPiServer.MarketingAutomationIntegration.Marketo 4.0.1;
Sep 02, 2018
MAI-1223
  Marketo: New contact created when submitting form in same browser session

Steps to reproduce

1. Submit a Marketo form with valid values for FirstName and Email.
2. Re-submit the form on the same browser session (no clearing cache) with a different email address.

Expected:
After step 2, no new leads are created. Only the lead created in 1st step is updated.

Actual:
2 leads are created.

EPiServer.MarketingAutomationIntegration.Marketo 4.0.0;
Aug 19, 2018
MAI-1262
  Marketo: Empty row added in database before credentials provided

Before credentials are saved on the admin screen, a row with empty values is created in the database. The row should only be created after the credentials are saved by the admin.

EPiServer.MarketingAutomationIntegration.Marketo 3.2.5; EPiServer.MarketingAutomationIntegration.Marketo 3.1.1;
Jul 08, 2018
MAI-1295
  Marketo: Data format errors when multiple requests made to retrieve credentials

If multiple concurrent requests are made to pages that require the fetching of credentials, the following error results:

The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters.

Note: This error is logged in the log file, not on the web page.

EPiServer.MarketingAutomationIntegration.Marketo 3.2.5; EPiServer.MarketingAutomationIntegration.Marketo 3.1.1;
Jul 08, 2018
1 2 Next