Area: Episerver Add-ons
Applies to versions: MarketingAutomationIntegration.Marketo 1 and higher

Episerver Connect for Marketo

Recommended reading 

The Episerver Connect for Marketo add-on is part of Episerver Connect for Marketing Automation. The add-on connects Marketo with Episerver Forms, allowing marketers to collect visitor data, and pass that on to be used with Marketo.


An Episerver CMS installation with Episerver Forms, and the required Marketing Automation connector components. See Episerver Connect for Marketing Automation.


The Connect for Marketo MA connector is installed through the NuGet package EPiServer.MarketingAutomationIntegration.MarketoSee Platform integration compatibility for supported Episerver versions.


To configure your Episerver website to use Marketo, you need a Marketo license that provides REST authentication (Endpoint URL, Client ID, and Client secret) and SOAP authentication (Endpoint URL, User ID, and Encryption key), and Web tracking code.

You also need to configure the connection of form fields to Marketo, so that data from the specified fields can be sent to Marketo. These configurations are described in Marketo connector in the Episerver User Guide.

See Marketo connector API methods how to perform operations on email templates and folders.

Encrypting credentials

Credentials are encrypted and saved based on one of the following options:

  • MAICryptoKey (AES encryption with an SHA256-computer hash based on the value of the key)
  • machineKey of the server in web.config.

Note: For DXC instances, use MAICryptoKey.

If you choose to use machineKey configuration, you should specify a machineKey in the web.config of your site so that when you deploy it to a different server, the same machine key is used on the new server.

Note: If you neglect to specify a machineKey in the web.config, the credentials are removed when the site on the new server is accessed for the first time, in which case you need to save credentials again through the configuration screen. 

If the credentials are already encrypted using machineKey in an existing site, and the MAICryptoKey setting is added, then the credentials are deleted and must be re-entered.

Similarly, if the encryption uses MAICryptoKey first and then you decide to use machineKey encryption (by deleting the MAICryptoKey setting), then the credentials are deleted and must be re-entered.

Related topics

Do you find this information helpful? Please log in to provide feedback.

Last updated: Jun 07, 2019

Recommended reading