Products
Packages [expand] [collapse]
Services
Released in version
5.7.0
5.6.3
5.6.2
5.6.1
5.6.0
5.5.6
5.5.5
5.5.4
5.5.3
5.5.2
5.5.1
5.5.0
5.4.0
5.3.4
5.3.3
5.3.2
5.3.1
5.3.0
5.2.2
5.2.1
5.2.0
5.1.0
5.0.2
5.0.1
5.0.0
4.4.2
4.4.1
4.4.0
4.3.1
4.3.0
4.2.0
4.1.0
4.0.0
3.0.0
2.5.1
2.5.0
2.4.2.9000
2.4.1.9000
2.4.0.9000
2.3.0.9000
2.2.2.9000
2.2.1.9000
2.2.0.9000
2.1.0.9000
2.0.3.8000
2.0.2.8000
2.0.1.8000
2.0.0.8001
1.2.1.8000
1.2.0.8000
1.1.9.7192
1.1.7.7518
1.1.6.7514

Release notes for Optimizely updates

This overview lists changes included in Optimizely updates delivered as NuGet packages and services. Use the information to decide which updates to apply to your project, see Installing Optimizely updates. Select a product, package, or service in the left menu, and filter for dates, features, or bug fixes.

  • See only new features (all features) - filter on item type Feature.
  • See only end-user (user interface) features - filter on item type UI Feature.
  • See only critical bug fixes - filter on item type Critical Bug.

Note: New 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-1871
  MAI Connectors: Use absolute expiration when caching entity data.

The MAI connectors store entity data in a cache with a sliding expiration of 10 minutes.
This causes an issue where if the data is updated directly on the provider portal itself (as opposed to updating via form submission), it won't be reflected on personalized blocks and form auto-fill unless the cache is not accessed in the cache expiration interval of 10 minutes.

This behavior has been changed from version 5.6.3, by setting the cache to expire after a fixed interval of 10 minutes.

EPiServer.ConnectForMarketingAutomation 5.6.3;
Mar 23, 2021
MAI-1852
  Marketing connectors: Error occurred when duplicate fields were present on visitor group fields.

When you configured a visitor group, an error occurred if duplicate field names were present in the marketing provider.

EPiServer.ConnectForMarketingAutomation 5.6.2;
Nov 03, 2020
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-1819
  Delivra connector: Show the member fields by their display names in form mappings and visitor group UIs.

Delivra Connector: Form field mapping and visitor groups UIs should show display names of fields.

EPiServer.ConnectForMarketingAutomation 5.6.0; EPiServer.Marketing.Automation.Forms 2.3.0; EPiServer.Marketing.Connector.Delivra 1.1.0;
Jun 28, 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-1738
  Silverpop: Visitor group datasource dropdown does not display child contact lists

The datasources dropdown on the Visitor Group Profile Criteria configuration screen for Silverpop lists only parent level databases. The dropdown should also display child contact lists.

EPiServer.ConnectForMarketingAutomation 5.5.5;
Dec 15, 2019
MAI-1736
  Reduce number of calls to dynamic data store in marketing connector framework.

There are multiple calls to dynamic data store to fetch the connector credentials. Use caching to reduce the number of calls.

EPiServer.ConnectForMarketingAutomation 5.5.4;
Nov 24, 2019
MAI-1728
  Marketing connectors make repeated calls to dynamic data store

There are multiple calls to dynamic data store to fetch the list of active connectors. Use caching to reduce the number of calls.

EPiServer.ConnectForMarketingAutomation 5.5.3;
Oct 27, 2019
MAI-1715
  MAI: Odd behavior on connector settings UI

Steps to reproduce
1) Go to any connector's Admin settings screen, for example, Admin -> Config -> Microsoft Dynamics CRM.
2) Add settings and save.
3) Refresh the page.
4) Click Add Connector. An empty settings box appears.
5) Without saving anything, click the Microsoft Dynamics CRM link in the left navigation. The empty settings box remains on the screen.
6) Click the "Microsoft Dynamics CRM" link again. The empty settings box disappears.

Expected
The empty settings box disappears after the first click on the Microsoft Dynamics CRM link.
Also, after the first click, when the empty settings box remains on the screen, if valid values are entered and "save" button is clicked, the box disappears, leaving only the previously saved settings box on the screen. That is, the new instance is not saved.

Actual
See steps to reproduce

EPiServer.ConnectForMarketingAutomation 5.5.2;
Oct 20, 2019
1 2 3 4 5 6 Next