- 08 Aug 2025
- 5 Minutes to read
- Print
- DarkLight
Installation and Configuration
- Updated on 08 Aug 2025
- 5 Minutes to read
- Print
- DarkLight
Salesforce Marketing Cloud Package Installation
STOP
In order to continue, you should have received a .zip file from Relay that will be used for the installation process.
SFTP File Location Setup
Prior to Installing the Package, you will need to setup File Locations.
Step # | Description | Salesforce Marketing Cloud |
---|---|---|
1 |
| |
2 |
| |
3 |
|
These File locations will match the FTP location in the File Transfer Activities within the Relay – Batch File Automation |
FILE LOCATIONS FOR BATCH INTEGRATION VIA SFTP:
Name & External Key & Description | File Path |
---|---|
Relay_Customer_Consent_Management | [environment]/dropoff/consent_update |
Relay_Customer_Onboarding | [environment]/dropoff/onboarding |
Relay_Customer_Phone_Management | [environment]/dropoff/phone_management |
Relay_Customer_Deactivation | [environment]/dropoff/deactivation |
Relay_Customer_Data | [environment]/dropoff/cca |
Relay_Customer_Message | [environment]/dropoff/messaging |
Configuration - Package Installation
Step # | Description | Salesforce Marketing Cloud |
---|---|---|
1 |
| |
2 |
| |
3 |
| |
4 |
| |
5 |
|
Configuration - Creating the Application Package
Step # | Description | Salesforce Marketing Cloud |
---|---|---|
1 |
| |
2 |
| |
3 |
|
Configuration - Adding API Component
Step # | Description | Salesforce Marketing Cloud |
---|---|---|
1 |
| |
2 |
| |
3 |
| |
4 |
|
Configuration - Relay Custom Journey Activity
Clients can create two custom journey activities as part of the package if they wish to have two components displayed in the journey builder palette – one for production and one for staging. The difference being the URL, which is explained in the steps below.
Step # | Description | Salesforce Marketing Cloud | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
1 |
| |||||||||||
2 |
|
Setup Access to Receive Relay Push Events
In order to subscribe to Relay Push Events/Web Hooks which flow into the relay_response_log data extension in your Salesforce Marketing Cloud instance, certain Salesforce Marketing Cloud keys must be obtained and configured for setup in Relay CX Builder.
Checklist of Salesforce Marketing Cloud Keys to be configured in CX Builder are:
Client Id
Client Secret
REST Based URI
Authentication Base URI
JSON Web Token (JWT) Signing Secret
Account ID
Step # | Description | Salesforce Marketing Cloud |
---|---|---|
1 |
| ![]() |
2 |
| |
3 | Login to CX Builder to Enter the Details and Establish Connectivity Once you are signed in, click on the API Management in the left menu column. Click on the Push API Integration tab. This is the “home page” of the Push API Integration UI, where you will see a list of existing integrations for the selected client (if any exist). Note: If you do not see the API Management module on the left menu, please check that you have either Client Admin or Client User with Integration Permissions in the system | |
4 | To add an integration, click the “ADD INTEGRATION” button. A modal will pop up with a dropdown, where you will select Salesforce Marketing Cloud | |
5 | Enter the details obtained from SFMC on this screen: Name: This is the name of the integration you are creating, and can be named whatever you wish to refer to it as. Version: Select the version of this integration form with which you wish to integrate your client. The latest version is selected by default. Client ID: This is the client id acquired from Salesforce, not the client’s Relay client id, and can be obtained from the client’s Salesforce Marketing Cloud instance. Client Secret: This value can be obtained from the client’s Salesforce Marketing Cloud instance. REST Base URI: This value can be obtained from the client’s Salesforce Marketing Cloud instance. Should resemble a URL and begin with: JWT Signing Secret: This value can be obtained from the client’s Salesforce Marketing Cloud instance. Authentication Base URI: This value can be obtained from the client’s Salesforce Marketing Cloud instance. Should resemble a URL and begin with: Account ID: This value can be obtained from the client’s Salesforce Marketing Cloud instance. | |
7 | Obtain the Auth Hash from CX Builder At the bottom of this screen, you will see an Auth Hash, use the copy icon to the right to copy this value and save it for the next step where you will add it to SFMC |
Setup Access to Call the Relay API to Trigger Experiences
In order to call the Relay APIs to trigger experiences from your Salesforce Marketing Cloud instance you need to store certain keys in Salesforce Marketing Cloud that have been provided by your Relay Client Success representative.
Checklist of Salesforce Marketing Cloud Keys to be sent to Relay are:
Auth Hash
Data Extension Mapping:
Field | Staging Connection | Production Connection |
---|---|---|
Metadata Id | 1 | 2 |
Metadata Name | relayauthhash_staging | relayauthhash_production |
Metadata Value | Auth Hash Value from CX Builder Staging | Auth Hash Value from CX Builder Production |
Step # | Description | Salesforce Marketing Cloud |
---|---|---|
1 | Store the Auth Hash in Salesforce Marketing Cloud:
|
Update External Keys
Step # | Description | Salesforce Marketing Cloud |
---|---|---|
1 |
| |
2 |
| |
3 |
| |
4 |
|