Overview
Salesforce Marketing Cloud (SFMC) Journey Builder offers visibility into consumer interactions across various marketing channels, including email, mobile, social ads and more. By connecting these actions or conversations, you gain a deeper understanding of your customers, improve message building, design and automate campaigns, deliver a seamless customer experience, and secure customer loyalty. Integrating with Zeotap enhances these capabilities by enabling marketers to base campaigns on real-time data sent from Zeotap.Supported Identifiers/Attributes
This integration allows you to send any identifiers of your choice and custom attributes.Prerequisites
Ensure that you have addressed the following prerequisites before starting the integration:- You must create a data extension table in SFMC Journey Builder with the relevant fields. You can use this data extension as an entry source in Salesforce Marketing Cloud Journey Builder. Note that you have Admin access to SFMC Journey Builder. For more information about how to create a data extension table, refer here.
- You must create package in SFMC Journey Builder and provide certain API permissions. For more information about how to create a package, refer here.
- Obtain the event definition key associated with the journey created in Journey Builder to which you need to push data from Zeotap CDP.
- Ensure that you validate and save the journey in Journey Builder before testing it. Validation confirms that all elements of the journey design are complete and ready for testing. Note that Journey Testing is unavailable for Single Send journeys.
Components of Salesforce Marketing Cloud - Journey Builder
Ensure that you have the details about the below components of Salesforce Marketing Cloud account before starting this integration.Client ID, Client Secret and SFMC Subdomain
Perform the following steps to obtain the Client ID, Client Secret and Domain details from your Salesforce Marketing Cloud account:Under Summary of the installed package, you can find the following components that are essential for creating a Destination:a. Client Id - Marked as 1 in the below image
b. Client Secret - Marked as 2 in the below image
b. Client Secret - Marked as 2 in the below image
Sub Domain - Your subdomain is a 28-character string that starts with the letters “mc” in any of your base URIs. For example, in the base URI https://mc6x3p75x6j07021qz11gk9xg8cq.rest.marketingcloudapis.com the subdomain is . You can find it marked as 3 in the below image.
Account ID
This is the member ID (MID) of your Salesforce Marketing Cloud account. You can obtain this ID in the following two ways:Option 1
Option 2
Event Definition Key
This is a unique identifier assigned to a journey created in Journey Builder. This key helps determine which journey in Journey Builder to use when pushing data from Zeotap CDP. Perform the following steps to obtain the Event Definition Key:
Contact Key
This is a unique ID used to differentiate records in a data extension. This is typically the primary key of the data extension but is not always the case.Destination Setup
After you have applied filters or added conditions for your users in Journeys, you can activate them in SFMC Journey Builder under Send to Destinations. A new window appears, where you can set up your destination. You can use an already existing destination from the list of available Destinations or create a new one by clicking + Add New Destination.
Add New Destination
Perform the following steps to add a new destination:Enter the Client ID, Client Secret, Sub Domain details obtained from the Salesforce Marketing Cloud Summary Screen. Learn more
In the mapping screen that appears, under Choose your Action, select Stream Events to SFMC Journey Builder as the action for sending data from the workflow created in Journeys. Under Map the Fields, use + Add Mapping Field to add any number of identifiers and attributes you wish to send to SFMC Journey Builder.
Activate the Destination on Journeys
After creating a destination, next, you need to link it in the Send to Destination node within the workflow, as explained below.
Under the Destination Details tab, the Client ID, Client Secret, Sub Domain and Account ID fields are automatically populated based on the value that you had entered while creating the destination. However, you need to enter the following values:a. Event Definition Key, which is a unique identifier assigned to a journey created in Journey Builder. This key helps determine which journey in Journey Builder to use when pushing data from Zeotap. For information about how to obtain this, refer here.
b. Contact Key, which is a unique ID used to differentiate records in a data extension. This is typically the primary key of the data extension but not always the case.
b. Contact Key, which is a unique ID used to differentiate records in a data extension. This is typically the primary key of the data extension but not always the case.
