Customer Message

Step #	Description	Salesforce Marketing Cloud
1	Complete the SQL Mapping Worsksheet. Note: For details on each data field and the required format, please see the Data Fields section below this table.	Customer Messaging 30.50 KB
2	Open Journey Builder > Automation Studio.
3	Select the Activities tab and open the list of SQL Queries.
4	Select the Relay Customer Message SQL Query and select the edit icon (pencil).
5	Edit the SQL Activity shell. All tablename.fieldname entries must be updated (or removed) based on your entries in the mapping worksheet. The Test table name must be replaced with the actual table name where the data will be pulled from. (If more than one table is used to obtain data, a properly coded SQL 'join' statement can be used.) All input_ parameters required for the trigger_id must be mapped. Add additional mappings for each input_ parameter to support the requirements of the experience.
6	Click through to save the updated query. Schedule the automation.

Step #

Description

Salesforce Marketing Cloud

Complete the SQL Mapping Worsksheet.
Note: For details on each data field and the required format, please see the Data Fields section below this table.

Customer Messaging

30.50 KB

Open Journey Builder > Automation Studio.

Select the Activities tab and open the list of SQL Queries.

Select the Relay Customer Message SQL Query and select the edit icon (pencil).

Edit the SQL Activity shell.
- All tablename.fieldname entries must be updated (or removed) based on your entries in the mapping worksheet.
- The Test table name must be replaced with the actual table name where the data will be pulled from. (If more than one table is used to obtain data, a properly coded SQL 'join' statement can be used.)
- All input_ parameters required for the trigger_id must be mapped. Add additional mappings for each input_ parameter to support the requirements of the experience.

Click through to save the updated query.
Schedule the automation.

Field Name	Data Type	Notes
CCID	Text (100)	Primary Key. Required. Uniquely identifies a Client’s Customer
TRIGGER_ID	Text (100)	Primary Key. Required. Experience trigger_id. The customer will be sent the experience associated with the specified trigger_id.
ASSET_ID	Text (100)	Optional. The asset_id can be used to override the default branding on the message.
CLIENT_MESSAGE_TAG	Text (100)	Optional. This is an arbitrary passthrough property specified by the Client for reporting and tracking by the Client.
LB_NAME	Text (255)	Optional. Client defined property to store the Launched_by Name record. Identifies the individual who launched a certain experience.
LB_SOURCE	Text (255)	Optional. Client defined property to store the Launched_by Source record. Identifies the system where an experience was launched.
INPUT_XXX	Text (100)	Optional input parameters to the message. Each input parameter is prefixed with INPUT_ followed by the input parameter name. Custom input parameters are provided by the Client Zero or more INPUT_ parameters can be specified Different INPUT_ parameters can be specified on each row in the file The maximum length of each INPUT_ parameter is 100 characters

Field Name

Data Type

Notes

CCID

Text (100)

Primary Key. Required. Uniquely identifies a Client’s Customer

TRIGGER_ID

Text (100)

Primary Key. Required. Experience trigger_id. The customer will be sent the experience associated with the specified trigger_id.

ASSET_ID

Text (100)

Optional. The asset_id can be used to override the default branding on the message.

CLIENT_MESSAGE_TAG

Text (100)

Optional. This is an arbitrary passthrough property specified by the Client for reporting and tracking by the Client.

LB_NAME

Text (255)

Optional. Client defined property to store the Launched_by Name record. Identifies the individual who launched a certain experience.

LB_SOURCE

Text (255)

Optional. Client defined property to store the Launched_by Source record. Identifies the system where an experience was launched.

INPUT_XXX

Text (100)

Optional input parameters to the message. Each input parameter is prefixed with INPUT_ followed by the input parameter name. Custom input parameters are provided by the Client Zero or more INPUT_ parameters can be specified Different INPUT_ parameters can be specified on each row in the file The maximum length of each INPUT_ parameter is 100 characters

Customer Message

Setting Up the Automation

Data Fields

What's Next