| Area |
ID |
Type |
Description |
Released |
|
MAI-2129
|
|
CMS 11 Salesforce: Excessive failed login attempts.
Fixed an issue in the Salesforce connector, which was making an excessive number of authentication calls when credentials became invalid.
EPiServer.MarketingAutomationIntegration.Salesforce 4.3.3; EPiServer.ConnectForMarketingAutomation 5.7.1; Episerver.Marketing.Automation.Forms 2.4.2;
|
Sep 01, 2023
|
|
|
MAI-2118
|
|
Marketing Connector Criteria disappeared after upgrading to CMS 12.15
Fixed an issue where Marketing Connector Criteria disappeared after you upgraded to CMS 12.15.
EPiServer.ConnectForMarketingAutomation 6.1.3;
|
Aug 31, 2023
|
|
|
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.
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-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-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
|
