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.
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-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
|