Packages [expand] [collapse]
Released in version
7.1.0
6.0.0
6.0.0-pre
5.0.0
4.2.2
4.2.1
4.2.0
4.1.0
4.0.0
3.2.0
3.1.0
3.0.1
3.0.0
2.0.1
2.0.0
1.3.3
1.3.2
1.3.1
1.3.0
1.2.2.9000
1.2.1.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-1867
  Pardot: Update Authentication mechanism.

The newly supported authentication method lets customers leverage Salesforce OAuth flows using Salesforce users, no longer requiring a one-off Pardot only user.

EPiServer.MarketingAutomationIntegration.Pardot 6.0.0;
Jul 27, 2021
MAI-1731
  Pardot connector: Custom fields with multiple values (Checkbox, Multi-Select) not saved

Upon form submission, Checkbox or Multi-Select custom fields are not being saved in the prospect properties.

EPiServer.MarketingAutomationIntegration.Pardot 5.0.0;
Nov 03, 2019
MAI-1698
  Pardot: Only subset of custom fields displayed on field mapping UI

Pardot API returns a maximum of 200 records in one API call. If there are more than 200, multiple requests must be made to fetch the remaining custom fields.

EPiServer.MarketingAutomationIntegration.Pardot 4.2.2;
Sep 29, 2019
MAI-1667
  Pardot: Authentication method changes as per recent Pardot API changes

There was a recent change to the way authentication is done for a few API calls, like getting a prospect and getting custom fields. The user_key and api_key must be sent in an HTTP Authorization header or the body of a POST request, instead of query string parameters.

EPiServer.MarketingAutomationIntegration.Pardot 4.2.1;
Jul 14, 2019
MAI-1499
  Pardot: Wrong endpoint being used when making a call to check if email already exists.

Endpoint being used to check if the email exists was
https://pi.pardot.com/api/prospect/version/4/do/read/id/<email>
It should be
https://pi.pardot.com/api/prospect/version/4/do/read/email/<email>

EPiServer.MarketingAutomationIntegration.Pardot 4.1.0;
Dec 09, 2018
MAI-1510
  Pardot: 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.Pardot 4.1.0;
Dec 09, 2018
MAI-1000
  Pardot: Form data not submitted to Pardot due to expired API key

In Pardot, the API Key is valid for 60 minutes, after which a new key is generated. This procedure works fine for other API calls, like retrieving prospect fields and prospect data. But when saving a prospect, the outdated key was being used. This caused a failure in the API call with the error message: "Either the user and/or API keys are incorrect, or the API key has expired."

EPiServer.MarketingAutomationIntegration.Pardot 3.0.1;
Nov 05, 2017
MAI-971
  MAI Connectors: Crytographic error if site deployed to server with different machine key.

If credentials are saved and the site/database is deployed to a server whose machine key is different, the site throws cryptographic error and becomes unusable.

EPiServer.ConnectForMarketingAutomation 4.0.0; EPiServer.MarketingAutomationIntegration.Eloqua 3.0.0; EPiServer.MarketingAutomationIntegration.ExactTarget 3.0.0; EPiServer.MarketingAutomationIntegration.HubSpot 3.0.0; EPiServer.MarketingAutomationIntegration.Marketo 3.0.0; EPiServer.MarketingAutomationIntegration.MSDynamics 3.0.0; EPiServer.MarketingAutomationIntegration.Pardot 3.0.0; EPiServer.MarketingAutomationIntegration.Salesforce 3.0.0; EPiServer.MarketingAutomationIntegration.Silverpop 3.0.0; Episerver.Marketing.Automation.Forms 1.1.9;
Aug 13, 2017
MAI-970
  Pardot: Crytographic error if site deployed to server with different machine key

If the credentials are saved and the site/database is deployed to a server whose machine key is different, the site throws cryptographic error and becomes unusable.

EPiServer.MarketingAutomationIntegration.Pardot 2.0.1;
Jul 30, 2017
MAI-727
  Pardot: Prospects not created upon form submission if credentials are changed

If a browser has the cookie that contains a ProspectId (that is, a form has been submitted successfully), and the credentials of the Pardot account are changed (in the Admin config screen) to point to a different instance, upon subsequent form submission, the Prospect is not updated.

EPiServer.MarketingAutomationIntegration.Pardot 1.3.3;
May 11, 2017
1 2 Next