Salesforce Marketing Cloud Journey Builder empowers you to guide customers on 1:1 journeys across channels and devices to deliver the right digital marketing solution, via the right channel. This article walks you through the process of setting up the Connector in your Customer Data Hub profile.

This connector is no longer available in the connector marketplace. For the latest version of this connector, which includes OAuth 2.0 support, see  Salesforce Journey Builder with OAuth Connector Setup Guide.

Table of Contents Placeholder

Requirements

  • Salesforce Marketing Cloud App Client Credentials
  • Salesforce Marketing Cloud Account
  • Journey
  • Event Entry Definition

Supported Actions

Action Name Trigger on Audience Trigger on Streams
Send Event to Initiate Journey

Configure Settings

Go to the Connector Marketplace and add a new Salesforce Marketing Cloud Connector. Read the Connector Overview article for general instructions on how to add a Connector.

To configure your vendor, follow these steps:

  • In the Configure tab, provide a title for the Connector instance.

  • Provide your Marketing Cloud App client ID and client secret.

  • Click Test Connection to verify API connectivity with the provided credentials.

For more information, see: Get App Client Credentials.

Action Settings - Parameters and Options

Click Next or go to the Actions tab. It's where you'll set up Actions to trigger.

This section describes how to set up Parameters and Options for each Action.

Action - Send Event to Initiate Journey

Parameters

  1. Event Entry Definition (REQUIRED): From this list, select an event entry definition that specifies the event data format to initiate journey.
  2. Contact Key (REQUIRED): Map an Attribute to uniquely identify the contact event data.
  3. Event Data (REQUIRED): Map Attribute(s) to contact event attributes. Attribute names must match Data Extension attributes for selected Event Definition (see: Entry Events and Data Definitions).
  4. Disable Auto Create Contact: By default, new contacts are created when sending event data with new contact keys. New contacts are then available to be injected into journeys. Check this option to disable automatic creation of contacts.

For more information, see: Admit Contacts via API

Vendor Documentation

Version history
Revision #:
4 of 4
Last update:
‎01-23-2020 02:27 PM
Updated by: