Episerver MA Connector Developer Guide

The Episerver Connect for Marketing Automation (MA) integration suite lets marketers automate activities such as web form interaction with Episerver Forms, and sending out emails based on visitor behavior, using popular MA products. There are a number of pre-built connectors available for integrating Episerver with common MA tools. This section describes how to install and configure components needed to set up an MA integration.

Getting started

Requirements

You need an account and live connection for the desired MA product (see list below), and an Episerver CMS site with Episerver Forms installed.

Installation

The MA components are installed through NuGet packages and Visual Studio.

Install the following for the MA integration:

The Forms connector (EPiServer.Marketing.Automation.Forms) to get the integration between Episerver Forms and the MA connector. See Configuring MAI connector.
The MA connector to connect with the desired marketing automation product (see list below).

See Platform integration compatibility for the specific NuGet packages to install and supported Episerver versions.

web.config

From EPiServer.ConnectForMarketingAutomation 5.5.1 onwards, configure the following section web.config.

<configSections>
  ...
  <section name="episerver.dataStore" 
           type="EPiServer.Data.Configuration.EPiServerDataStoreSection, EPiServer.Framework.AspNet"/>
</configSections>

  <episerver.dataStore>
     <dataStore autoRemapStores="true">
     </dataStore>
  </episerver.dataStore>

Connectors

Select the MA product to continue with the installation and configuration.

Digital Experience Hub (DXH)

The Episerver Digital Experience Hub (DXH) is part of the the Episerver Customer-Centric Digital Experience Platform (DXP), and provides a set of the pre-built MA connectors. See Digital Experience Hub.

Custom connectors

See the Custom connector developer guide for examples how to build connectors implementing necessary components for integration with the Episerver DXH marketing connector framework.This integration requires installation of the Episerver.ConnectForMarketingAutomation package.

Cookie usage

The cookie described below is used with these Episerver Marketing Automation connectors:

Cookie Name	Purpose
mai_trk_{connectorId}_{instanceID}	Functionality-related. Identifies current visitor for form auto-fill purposes. Connector-related personalization is through visitor groups. Persistent (1 year from creation).

See Cookies for more information about cookies used in other parts of the Episerver platform.