- 13 Nov 2024
- 3 Minutes to read
- Print
- DarkLight
Installation and Configuration
- Updated on 13 Nov 2024
- 3 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 provided to the Relay Client Success Team representative to be setup in Relay CX Builder.
Checklist of Salesforce Marketing Cloud Keys to be sent to Relay 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 |
|
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 | Value provided by Relay. | Value provided by Relay. |
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 |
|