Contents x
    Relay Response Log
    • 07 Feb 2025
    • 2 Minutes to read
    • Print
    • Dark
      Light
    Contents

    Relay Response Log

    • Updated on 07 Feb 2025
    • 2 Minutes to read
    • Print
    • Dark
      Light
    Article summary

    Relay Response Log data extension stores response data from the Relay platform back into SFMC. This data extension is used to capture ALL transactional updates for messaging and connections delivered from the Relay platform. There is no need to build a rollup view of activity at the person (CCID) or person within a campaign. The Response log DE design allows SFMC users the ability to build their own queries for data extracts or segments to retarget.

    SFMC places limits on the number of annual requests made to its REST APIs. To reduce the number of calls, as a default, Relay groups events in batches of 50 and pushes all available events every 15 minutes.

    The various events that populate this data extension can be found here: Push Events

    Data Extension Name: relay_response_log

    Standard fields in this data extension are:

    Field Name

    Data Type

    Notes

    action_label

    string (255)

    The text on an action element within a Feed message. Examples: “Call Customer Service” and “Provide Feedback”

    action_value

    string (255)

    The destination of an action. Examples: “(800) 555 1234” and “[email protected]”

    channel_address

    string (100)

    The phone number associated with the Customer. Example: “12155551234”

    channel_type

    String (100)

    The type of channel the channel address represents. Example: “sms”

    client_message_tag

    string (255)

    A system passthrough value intended to link feed messages to other Client systems. Any experience triggered from the SFMC widget will include a GUID in this field. This enables adding SFMC Journey Name and SFMC Journey Version to Relay Response Log data.

    client_id

    string (100)

    A unique client identifier provided by Relay

    current_consent

    string (50)

    The current consent type for the channel address. Valid values:

    • express

    • written

    • stop

    client_source

    string(100)

    A second level of tracking the source of an update or message request. Example: phone number removals occurring as a part of monthly Neustar analysis will have a client_source of “Neustar.”

    customer_id

    string(255)

    [UUID] A unique Relay customer identifier.

    data_capture_id

    string(255)

    The unique identifier of the data capture field. This ID is specified in the Relay CX Builder.

    data_capture_label

    string(255)

    The data capture field label as presented to the end user

    data_capture_value

    string(4000)

    The current captured value of the field

    error_string

    string(255)

    The description of the error. Examples: Duplicate message suppression is active, missing input parameters: [fieldname], and Customer id [ccid] not found.

    error_type

    string(255)

    The error resulting in message.not_attempted or notification.not_attempted. Examples: duplicate-request, missing-fields, and ccid-not-found.

    event_id

    string(255)

    [UUID] A unique Relay event identifier.

    event_subtype

    string(255)

    Primary Key. The sub event type. See the Event Types section below for complete details.

    event_timestamp

    Date

    Primary Key [timestamp] Contains the date and time of when the event occurred. The data is in ISO 8601 format

    event_type

    string(255)

    Primary Key. The event type. See the Event Types section below for complete details.

    job_id

    string(255)

    [UUID] A unique Relay job identifier.

    journey_id

    string(255)

    [UUID] A unique Relay experience identifier.

    journey_ver

    string(50)

    In order for this field to be populated in the Response Log, the Journey Name Automation must be enabled.

    mc_journey_name

    string(200)

    In order for this field to be populated in the Response Log, the Journey Name Automation must be enabled.

    mc_journey_version

    string(50)

    In order for this field to be populated in the Response Log, the Journey Name Automation must be enabled.

    message_id

    string(255)

    A unique Relay feed message identifier.

    message_name

    string(255)

    The CX Builder entered name of the feed message.

    name

    string(255)

    The name of the event.

    notification_id

    string(255)

    A unique Relay notification identifier.

    previous_consent

    string(50)

    The consent type of the notification channel prior to the change. Valid values: “express”, “written”, “stop”, null

    product_group_id

    string(255)

    The product group Id assigned to the Customer. A Customer can only be assigned to a single product group.

    relay_ccid

    string(255)

    Primary Key. Uniquely identifies a Client’s Customer

    relay_tracking_id

    string(255)

    A unique Relay tracking identifier for the event.

    source_channel

    string(255)

    The source channel where the event originated from.

    trigger_id

    string(255)

    The trigger Id of the Relay experience the event is related to

    trigger_nickname

    string(255)

    The user friendly name associated with the Relay experience trigger

    Was this article helpful?
    What's Next