Packages [expand] [collapse]
Released in version
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; see Installing Optimizely updates.

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-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-1664
  Marketo: Add an option to specify workspaces from where to fetch lists from.

On the Admin Configuration screen, provide an optional text field to specify workspace names. If any workspace is specified, lists are fetched from that workspace only.
Multiple workspaces can also be given, separated by commas.

EPiServer.MarketingAutomationIntegration.Marketo 4.4.0;
Jun 16, 2019
MAI-1622
  Marketo: Choose behavior of multiple form submissions in same session

Currently, multiple form submissions in the same session update the lead created on the first submission. Provide an option to create a new lead on every submission, similar to the Salesforce connector.

EPiServer.MarketingAutomationIntegration.Marketo 4.3.0;
Apr 07, 2019
MAI-1595
  Marketo: Add API method to determine membership of a lead in a list

Add API methods in the service and connector to determine the membership of a lead in a list.

bool IsMemberOfList(long leadId, long listId)

EPiServer.MarketingAutomationIntegration.Marketo 4.2.0;
Mar 03, 2019
MAI-1371
  Marketo: Update settings UI to allow creation of multiple instances.
EPiServer.MarketingAutomationIntegration.Marketo 4.1.0; EPiServer.ConnectForMarketingAutomation 5.3.0;
Dec 09, 2018
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
1 2 3 Next