Email/SMS Settings Table
The Email/SMS Settings table contains email and SMS campaign and flow message setup, including message content, status, send timing, and message-level counters. One row per campaign or flow message setup.
Table GuideWhat You Can Answer With This Table
- What subject lines and message copy belong to each campaign or flow? — use
campaign_nameorflow_namewithmessage_subject,message_copy, andmessage_name- Which campaigns and flows are active, archived, or draft? — use
campaign_status,flow_status,campaign_archived,flow_archived- How many recipients, deliveries, opens, clicks, and conversions are tied to each message setup? — use
delivered,opens_unique,clicks_unique,recipients,conversionsBefore You Query
- This table is not time-series. No
event_datefilter is needed.Key Relationships
Table Join Key Use This Join To Email/SMS message_idMeasure how each message configuration performed over time When to Use a Different Table
- Use Email/SMS table when you need daily performance trends for email/SMS campaigns or flows. The Email/SMS Settings table is for message configuration, content, and setup details.
Dimensions
Dimensions are immutable properties that can be used for grouping data.
| Title | ID | Type | Description |
|---|---|---|---|
| Is Campaign Archived | campaign_archived | boolean | True if the campaign has been archived. Possible values: |
| Campaign Creation Date | campaign_created_at | date | The time the campaign was created. Formatted according to the ISO 8601 international standard. Example value: |
| Campaign ID | campaign_id | string | The unique ID of the email/SMS campaign, assigned by the email/SMS platform. Example value: |
| Campaign Name | campaign_name | string | The name of the email/SMS campaign. Example values: |
| Campaign Scheduled Date | campaign_scheduled_at | date | The time the campaign was scheduled to be sent. Formatted according to the ISO 8601 international standard. Example value: |
campaign_send_date | |||
| Campaign Sent Date | campaign_send_time | date | The time the campaign was sent to recipients. Formatted according to the ISO 8601 international standard. Example value: |
| Campaign Status | campaign_status | string | The status of the campaign associated with the email/SMS. Example values: |
| Campaign Updated Date | campaign_updated_at | date | The time the campaign was last updated. Formatted according to the ISO 8601 international standard. Example value: |
| Channel | channel | string | The platform used to send email/SMS. Example values: |
| Messaging Channel Type | channel_type | string | The messaging channel used to deliver the communication. Example values: |
| Is Flow Action Archived | flow_action_archived | boolean | True if the specific action within an automation flow has been archived. Possible values: |
| Flow Action ID | flow_action_id | string | The unique ID for a specific action within an automation flow. Assigned by the email/SMS platform. Example value: |
| Flow Action Name | flow_action_name | string | The name of the specific action within an automation flow. Example values: |
| Flow Action Status | flow_action_status | string | The status of a specific action within an automation flow. Example values: |
| Flow Action Updated Date | flow_action_updated_at | date | The time the flow action was updated. Formatted according to the ISO 8601 international standard. Example value: |
| Is Flow Archived | flow_archived | boolean | True if the automation flow has been archived. Possible values: |
| Flow Created Date | flow_created_at | date | The time the automation flow was created. Formatted according to the ISO 8601 international standard. Example value: |
| Flow ID | flow_id | string | The unique ID for the automation flow. Assigned by the email/SMS platform. Example value: |
| Flow Name | flow_name | string | The name of the automation flow. Example value: |
| Flow Status | flow_status | string | The status of the automation flow. Example values: |
| Flow Trigger Is Triple Whale | flow_trigger_is_tw | boolean | True if the flow was triggered by a Triple Whale (Sonar) metric or event. Possible values: |
| Flow Trigger Metric ID | flow_trigger_metric_id | string | The ID of the metric or event that triggered the flow. Example value: |
| Flow Trigger Metric Name | flow_trigger_metric_name | string | The name of the metric or event that triggered the flow. Example values: |
| Flow Trigger Organization | flow_trigger_organization | string | The platform where the flow trigger originated. Example values: |
| Flow Trigger Sonar Enabled | flow_trigger_sonar_enabled | boolean | True if Sonar is enabled for this flow trigger. Possible values: |
| Flow Updated Date | flow_updated_at | date | The time the automation flow was last updated. Formatted according to the ISO 8601 international standard. Example value: |
| Message Copy | message_copy | string | The full text content of the email message body, including dynamic variables and template tags used for personalization, embedded links, images, and call-to-action buttons. Example value: |
| Message ID | message_id | string | The unique ID for the individual message sent as part of a campaign or flow. Assigned by the email/SMS platform. Example value: |
| Message Name | message_name | string | The name of the individual message sent. Example value: |
| Message Preview Text | message_preview_text | string | The short snippet of text shown alongside the subject line in the recipient’s inbox, offering a preview of the message content. Example value: |
| Message Subject | message_subject | string | The subject line of the email message, as displayed in the recipient's inbox. Example value: |
| Message Template HTML URL | message_template_html_url | string | The URL of the hosted HTML template for the email message, fully formatted as rendered for recipients. Example value: |
| Report Type | report_type | string | The type of report generated. Example values: |
| Shop ID | shop_id | string | The unique ID of the shop (often corresponds to the shop domain). Can be used to group or filter data by shop in multi-store reports. Example values: |
| Shop Name | shop_name | string | The name of the shop. Can be used to group or filter data by shop in multi-store reports. Example values: |
Measures
Measures are numeric fields that can be aggregated and/or combined to calculate new metrics.
| Title | ID | Type | Description |
|---|---|---|---|
| Clicks | clicks_unique | numeric | The total number of unique clicks on links within the email/SMS. |
| Conversion Value | conversion_value | numeric | The total value of conversions for the email/SMS campaign / flow. |
| Conversions | conversions | numeric | The total number of conversions for the email/SMS campaign / flow. |
| Delivered Messages | delivered | numeric | The total number of messages successfully delivered to the targeted recipient. |
| Opens | opens_unique | numeric | The total number of unique email opens. |
| Recipients | recipients | numeric | The total number of intended recipients for the email/SMS campaign. |
Updated 7 days ago