Marketing Cloud Administration Console

The Marketing Cloud Administration Console home page contains three sections enabling admin and integration users to manage the connection between Salesforce Marketing cloud and Veeva CRM:

Veeva CRM Connection Management – Allows admin users to create, edit, and validate the CRM instance used to integrate with Marketing Cloud

Marketing Cloud Connection Management - Allows admin users to create, edit, remove, and validate multiple Marketing Cloud instances. Selecting View Map displays the Marketing Cloud Integration Management page where admin users can set up object and field mappings

Marketing Cloud Job Status – Allows admin users to view and schedule Marketing Cloud jobs

The Veeva Salesforce Marketing Cloud Connector consists of three components:

Configuration

Data Extraction

Monitoring

The Connector allows Veeva CRM to connect to multiple Salesforce Marketing Cloud instances, extract data from them, and reconcile that data with existing CRM data. For example, one Marketing Cloud instance tracks customer activity in France and another tracks data from the UK. Data from both is captured in a single Veeva CRM org.

Configuring the Marketing Cloud Administration Console

  1. Grant admin users tab visibility to the Marketing Cloud Administrator Console tab.
  2. Grant users FLS Edit permission to the following fields on the Multichannel_Activity_vod object:

    1. MCD_Primary_Key_vod
    2. Start_Datetime_vod

      VExternal_Id_vod

  3. Grant users FLS Edit permission to any custom fields created in the Multichannel_Activity_vod object. This step is optional.
  4. These fields must be mapped in the Optional Field Mapping section.

  5. To leverage the DeveloperName of the Record Type instead of the SFDC ID when data loading, grant users FLS Edit permission to the Record_Type_Name_vod field on the Multichannel_Activity_vod object. See Simplifying the Multi-channel Activity Data-Load Process for more information. This step is optional.

Using the Marketing Cloud Administration Console

To enable the inbound integration with Salesforce Marketing Cloud, users must:

Provisioning Salesforce Marketing Cloud API Integration

Salesforce Marketing Cloud API Integration must be provisioned to enable the Marketing Cloud integration. The API Integration allows users to leverage Marketing Cloud APIs to automate tasks or integrate business systems. The API Integration utilizes an OAuth client credential flow to acquire access tokens from an API authentication service.

Users must create a Salesforce Marketing Cloud App Center account to receive an API Key. See the Salesforce documentation for instructions.

Creating a New Marketing Cloud Instance

To create a new Marketing Cloud instance to integrate with Veeva CRM, select New from the Marketing Cloud Connection Management section. Users must provide the following information in the pop-up window:

Field

Description

Connection Name The unique name of the Marketing Cloud instance
Client ID Obtained through the API Key.

Client Secret

Obtained through the API Key.

Status Drop-down menu the user can set to Active or Inactive. If set to Inactive, any Marketing Cloud jobs associated to the instance do not run. Only Active connections run.

After creating a Marketing Cloud instance, select View Map to create object and field mappings on the Marketing Cloud Integration Management page.

As of August 1, 2019, all new packages will be created as enhanced packages. See Creating Enhanced Package Connections for more information.

Creating a New Marketing Cloud Object

To create a new Marketing Cloud object, select New on the Marketing Cloud Integration Management page. A pop-up window displays with the following fields:

Field

Description

CRM Object API Name Automatically populates as Multichannel_Activity_vod and is read-only.
Data Extension Key Drop-down menu listing all available Marketing Cloud Data Extension objects.

Filter Property

Allows users to define a filter to retrieve a subset of Data Extension data. The format is [PropertyName];;[Operator];;[PropertyValue]. The available operators are:

  • equals
  • notEquals

    greaterThan

    lessThan

Status Drop-down menu the user can set to Active or Inactive. If set to Inactive, any Marketing Cloud jobs associated to the instance do not run. Only Active connections run.

Mapping Marketing Cloud Data Extensions to CRM Objects

A Marketing Cloud object displays on the Marketing Cloud Integration Management page after it is created. This page enables users to map Marketing Cloud Data Extensions to CRM Multi-channel Activity objects. Data Extensions are custom objects containing the information captured by Marketing Cloud. In the example below, there are two data extensions: Mass Email Marketing Message and Portal Visit.

Users can select Show Details or Hide Details next to a Marketing Cloud object to display information about the object including Status, Last Modified Date, and Validation Status. In the Contact to Account Mapping section, admins must set-up a field to uniquely identify an Account in CRM, either by external ID or email address. This mapping is used to associate a contact in Marketing Cloud to the corresponding Account record in CRM.

Users can add up to three field mappings in the Contact-Account section by selecting Add New (+). The Marketing Cloud record is matched to the existing Account record in order of precedence.

Required Field Mapping stores the field mapping for the Primary Key, and the timestamp of a Marketing Cloud activity. A Primary Key uniquely identifies a Marketing Cloud record. Admin users must map the Data Extension fields to the Multi-channel Activity Fields. The following table details the required field mappings:

Data Extension Field Name

Description

Multichannel Activity Field Name
<Data Extension>.Activity_Time Drop-down menu displaying the timestamp of the Marketing Cloud activity.

Automatically populates as Start_DateTime_vod and is Read only.

<Data Extension>.Primary_Key Drop-down menu displaying available Data Extension fields to mark as a Primary Key field. It also includes the system default _CustomObjectKey. Automatically populates as MCD_Primary_Key_vod and is Read only.

The integration uses a combination of the Marketing Cloud connection name, data extension key, and primary key as the basis for the data upload. This combination key is stored as a ‘::’ delimited list in the VExternal_Id_vod field on the Multichannel_Activity_vod object.

Validating Mappings

Users can validate field mapping by selecting Validate in the header section. Any validation errors display at the field level. The validation checks for the following:

Does the field exist?

Does the user have FLS to the field?

Do the source/target field types match?

Is the selected default record type active and available to the CRM integration user?

A yellow exclamation point icon displays next to the connection name of an object mapping with validation errors.

The Locale field type in Marketing Cloud is not supported in the field mappings.

Scheduling Marketing Cloud Jobs

After object mappings are created and validated, schedule the integration job. The integration job retrieves connections and mappings validated and marked as Active. The connector validates Marketing Cloud connection and mappings, then extracts Marketing Cloud data modified since the last time the job ran. The data is then uploaded to CRM.

The Marketing Cloud Job Status section allows admin users to view and schedule Marketing Cloud jobs. It displays recent jobs by instance, the number of successful rows processed, and the number of failed rows.

Users can schedule a Marketing Cloud job in two ways:

  • Selecting Schedule on the Marketing Cloud Administration page displays the standard Multi-channel Scheduler page where users can schedule a Marketing Cloud job. The job retrieves Active object mappings and data from Marketing Cloud, while respecting the Filter Property query
  • Selecting Run Now next to an individual object mapping in a Marketing Cloud instance initiates an ad hoc job run for only that particular mapping.
  • A pop-up window displays with the last successful job run date. Users can change the date to specify a custom date range. All data created between that date and the current date is extracted.

Marketing Cloud jobs cannot run more than once a day. The first time the job runs after the initial setup, the data is extracted from Marketing Cloud for the previous 14 days. When a new data extension is added to the job, the data is extracted for activities which occurred since the previous run of the job.

Each object mapping contains an icon to indicate the status of the last run. Icons include:

  • Green check mark -  Successful run
  • Red exclamation point -  Failed run
  • Grey pause mark - Inactive object mapping
  • Yellow triangle -  Successful run with row failures

Selecting Activity Log on the Marketing Cloud Administration Console home page displays the Marketing Cloud Activity Log page, displaying information about jobs from the last 14 days. A yellow triangle icon in a job row indicates an error. Users can hover their cursor over the icon to view the error message.

Resolving Errors

Users can download error logs enabling them to fix the data manually and upload it with the Salesforce data loader. Users access the error logs by selecting the number in the Failed Rows column, either in the Marketing Cloud Job Status section or the Marketing Cloud Activity Log.

Error files are stored on the Veeva server for up to 14 days.

In the Marketing Cloud Processes section of the Multi-channel Scheduler page, admin users can set recipients for an email alert when there are failed rows. The email contains a link to the Error log in CSV format.