Building a New Salesforce Marketing Cloud Journey
  • 13 Nov 2024
  • 3 Minutes to read
  • Dark
    Light

Building a New Salesforce Marketing Cloud Journey

  • Dark
    Light

Article summary

Prerequisites

This chapter outlines the prerequisites necessary to use the Relay Widget when building a Salesforce Marketing Cloud Journey.

Step #

Summary

Description

Salesforce Marketing Cloud

1

Obtain Package Install

  • .zip Package Received from Relay

    • Steps completed in the Setup Access to Call the Relay API to Trigger Experiences section.

2

Create Relay Experience(s)

Experiences Exist in CX Builder

  • The installation process culminates in triggering a Relay message out of SFMC.

  • It is important for there to be an existing experience, in both the Relay staging and production environments, able to be used to confirm the integration is complete. This can be a simple message OR can model planned use cases.

  • When setting up an experience in CXB, remember to add a trigger nickname. The trigger nickname will populate in the custom journey activity when selecting a message.

    • NOTE: If you do not add a trigger nickname, the trigger id will populate in the custom journey activity.

cxb

3

CCID Available in SFMC

  • CCID is the unique identifier to message a customer in Relay.

  • A column containing CCID values must be included in the starting data extension and CCID must also be populated in the relay_network_data data extension (included with the installation package) for the custom journey activity to operate successfully.

    • NOTE: Every call to Relay from the custom journey activity requires CCID to complete successfully.

Custom Journey Builder Activity

Two custom activities are set up during configuration. One pointing to Relay’s staging environment, used for testing, and the other pointing to Relay’s production environment. When the user drags and drops the Relay Network custom activity on the SFMC Journey Builder canvas, all standard data fields that are required as part of onboarding or messaging are read from the standard Relay data extension (relay_network_data).The Relay Network custom activity can be pulled onto an existing Journey or into a new Journey. The Relay Network custom activity reads input_parameters and client message tag values from the starting DE.

Step #

Summary

Description

Salesforce Marketing Cloud

1

Starting Data Extension

  • When designing a journey in SFMC, add the starting DE as the entry source.

  • The Relay Network custom activity references the fields in the starting DE as Event.EventDefinitionKey and the starting DE needs to exist for the reference to succeed.

2

Locate the Custom Widgets

Experiences Exist in CX Builder

  • Under Custom on the right-hand side, choose the Relay widget associated with the environment you wish to utilize (Staging or Production).

  • After dragging the custom activity onto the Journey, select the custom activity to configure it.

3

Configure the Custom Widget

Select an Activity

  • Onboard: Requires ccid, product_group_id, phone_number, and consent_type populated in relay_network_data DE to complete call to Relay.  Note: It is possible to select Onboard and not select an Experience if you want to establish a connection in Relay, but do not want to send a message at the same time.

  • Message: Requires ccid in relay_network_data DE to complete call to Relay

4

Configure the Custom Widget

  • Select an Experience.

    Note: All experiences from CX Builder marked as Complete will be available in the list.

  • Select a Message Trigger

    Note: If the trigger nickname is populated in CX Builder it will display here, otherwise it will show the Relay generated trigger ID.

  • Client Message Tag. This is an optional field. This field can be used to map a pass through value with the messaging events that will return with the messaging results data into the relay_response_log DE. Client Message Tag must be available in the Starting data extension.

  • Input Parameters. If the selected experience has variable content, those fields will show up here for mapping. Enter the field name from the starting data source for each input field

    Note: If your field names are the same in CX Builder and in SFMC, the tool defaults to assume this and it will save time when configuring experiences in your Journey Builder journey.


Was this article helpful?

ESC

Eddy AI, facilitating knowledge discovery through conversational intelligence