Relay Power-Ups Response Log
- 13 Nov 2024
- 1 Minute to read
- Print
- DarkLight
Relay Power-Ups Response Log
- Updated on 13 Nov 2024
- 1 Minute to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
The Relay Power-Ups Response Log data extension stores response data from customers who have answered Power-Ups prompts. 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.
Data Extension Name: relay_powerups_response_log
Standard fields in this data extension are:
Field Name | Data Type | Notes |
|---|---|---|
event_type | Text (255) | The event type. |
event_subtype | Text (255) | The event subtype. |
event_timestamp | Date/Time | Primary Key. Required. Contains the date and time of when the event occurred. The data is in ISO 8601 format |
relay_ccid | Text (255) | Primary Key. Required. Uniquely identifies a Client’s Customer |
product_group_id | Text (255) | The product group Id that will be assigned to the Customer. A Customer can only be assigned to a single product group. |
trigger_nickname | Text (255) | The user friendly name associated with the Relay experience trigger. |
client_message_tag | Text (4000) | 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. |
journey_id | Text (255) | [UUID] A unique Relay experience identifier. |
trigger_id | Text (255) | The trigger Id of the Relay experience the event is related to |
message_id | Text (255) | [UUID] A unique Relay feed message identifier. |
relay_tracking_id | Text (255) | [UUID] A unique Relay tracking identifier for the event. |
event_id | Text (255) | [UUID] A unique Relay event identifier. |
Text (255) | [UUID] A unique Relay customer identifier. | |
client_id | Text (100) | [UUID] A unique client identifier. |
form_id | Text (255) | Primary Key. Required. [UUID] A unique Relay identifier for the form (Power-Up) filled out by the customer. |
date_submitted_at | Text (255) | Timestamp of when the customer submitted their answers to a form in unix ms format. |
name | Text (80) | [UUID] The name of the event. |
submission_id | Text (255) | Primary Key. Required. [UUID] The unique identifier of the full Power-Up submission. |
submission_answer_id | Text (255) | Primary Key. Required. The Power-Up submission answer identifier. |
submission_type | Text (255) | The Power-Up submission answer type. |
submission_value | Text (4000) | The Power-Up submission answer. |
Was this article helpful?