---
updatedAt: 2026-06-15T09:30:12.000Z
agentTools:
  projectIndex: https://triplewhale.readme.io/llms.txt
---

# Email/SMS Settings Table

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 Guide
>
> **What You Can Answer With This Table**
>
> * What subject lines and message copy belong to each campaign or flow? — use `campaign_name` or `flow_name` with `message_subject`, `message_copy`, and `message_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`, `conversions`
>
> **Before You Query**
>
> * This table is not time-series. No `event_date` filter is needed.
>
> **Key Relationships**
>
> | Table                                                          | Join Key     | Use This Join To                                           |
> | :------------------------------------------------------------- | :----------- | :--------------------------------------------------------- |
> | [Email/SMS](https://triplewhale.readme.io/docs/emailsms-table) | `message_id` | Measure how each message configuration performed over time |
>
> <br />
>
> **When to Use a Different Table**
>
> * Use [Email/SMS table](https://triplewhale.readme.io/docs/emailsms-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.
>
> *[View the full Triple Whale Data Ontology →](https://triplewhale.readme.io/docs/triple-whale-data-ontology)*

***

# Dimensions

Dimensions are immutable properties that can be used for grouping data.

<Table align={["left","left","left","left"]}>
  <thead>
    <tr>
      <th>
        Title
      </th>

      <th>
        ID
      </th>

      <th>
        Type
      </th>

      <th>
        Description
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        Is Campaign Archived
      </td>

      <td>
        `campaign_archived`
      </td>

      <td>
        boolean
      </td>

      <td>
        True if the campaign has been archived.

        Possible values: `true`, `false`
      </td>
    </tr>

    <tr>
      <td>
        Campaign Created Date
      </td>

      <td>
        `campaign_created_at`
      </td>

      <td>
        timestamp
      </td>

      <td>
        The time the campaign was created. Formatted according to the [ISO 8601 international standard](https://www.iso.org/iso-8601-date-and-time-format.html).

        Example value: `2019-04-15 08:26:00`
      </td>
    </tr>

    <tr>
      <td>
        Campaign ID
      </td>

      <td>
        `campaign_id`
      </td>

      <td>
        string
      </td>

      <td>
        The unique ID of the email/SMS campaign, assigned by the email/SMS platform.

        Example value: `01G2MRY5AF2A4QFJMS5EF8X2MW`
      </td>
    </tr>

    <tr>
      <td>
        Campaign Name
      </td>

      <td>
        `campaign_name`
      </td>

      <td>
        string
      </td>

      <td>
        The name of the email/SMS campaign.

        Example values: `Fall Colors Launch`, `Father's Day Sale 50% Off`
      </td>
    </tr>

    <tr>
      <td>
        Campaign Scheduled Date
      </td>

      <td>
        `campaign_scheduled_at`
      </td>

      <td>
        timestamp
      </td>

      <td>
        The time the campaign was scheduled to be sent. Formatted according to the [ISO 8601 international standard](https://www.iso.org/iso-8601-date-and-time-format.html).

        Example value: `2019-04-15 08:26:00`
      </td>
    </tr>

    <tr>
      <td>
        Campaign Sent Date
      </td>

      <td>
        `campaign_send_date`
      </td>

      <td>
        date
      </td>

      <td>
        The date the campaign was sent to recipients.

        Example value: `2019-04-15`
      </td>
    </tr>

    <tr>
      <td>
        Campaign Sent Time
      </td>

      <td>
        `campaign_send_time`
      </td>

      <td>
        timestamp
      </td>

      <td>
        The time the campaign was sent to recipients. Formatted according to the [ISO 8601 international standard](https://www.iso.org/iso-8601-date-and-time-format.html).

        Example value: `2019-04-15 08:26:00`
      </td>
    </tr>

    <tr>
      <td>
        Campaign Status
      </td>

      <td>
        `campaign_status`
      </td>

      <td>
        string
      </td>

      <td>
        The status of the campaign associated with the email/SMS.

        Example values: `Sent`, `Cancelled`
      </td>
    </tr>

    <tr>
      <td>
        Campaign Updated Date
      </td>

      <td>
        `campaign_updated_at`
      </td>

      <td>
        timestamp
      </td>

      <td>
        The time the campaign was last updated. Formatted according to the [ISO 8601 international standard](https://www.iso.org/iso-8601-date-and-time-format.html).

        Example value: `2019-04-15 08:26:00`
      </td>
    </tr>

    <tr>
      <td>
        Channel
      </td>

      <td>
        `channel`
      </td>

      <td>
        string
      </td>

      <td>
        The platform used to send email/SMS.

        Example values: `klaviyo`, `smsbump`
      </td>
    </tr>

    <tr>
      <td>
        Messaging Channel Type
      </td>

      <td>
        `channel_type`
      </td>

      <td>
        string
      </td>

      <td>
        The messaging channel used to deliver the communication.

        Example values: `email`, `sms`, `push`
      </td>
    </tr>

    <tr>
      <td>
        Is Flow Action Archived
      </td>

      <td>
        `flow_action_archived`
      </td>

      <td>
        boolean
      </td>

      <td>
        True if the specific action within an automation flow has been archived.

        Possible values: `true`, `false`
      </td>
    </tr>

    <tr>
      <td>
        Flow Action ID
      </td>

      <td>
        `flow_action_id`
      </td>

      <td>
        string
      </td>

      <td>
        The unique ID for a specific action within an automation flow. Assigned by the email/SMS platform.

        Example value: `51670312`
      </td>
    </tr>

    <tr>
      <td>
        Flow Action Name
      </td>

      <td>
        `flow_action_name`
      </td>

      <td>
        string
      </td>

      <td>
        The name of the specific action within an automation flow.

        Example values: `SEND_EMAIL`, `SEND_SMS`, `AB_TEST`, `TIME_DELAY`, `WEBHOOK`
      </td>
    </tr>

    <tr>
      <td>
        Flow Action Status
      </td>

      <td>
        `flow_action_status`
      </td>

      <td>
        string
      </td>

      <td>
        The status of a specific action within an automation flow.

        Example values: `draft`, `live`, `manual`
      </td>
    </tr>

    <tr>
      <td>
        Flow Action Updated Date
      </td>

      <td>
        `flow_action_updated_at`
      </td>

      <td>
        timestamp
      </td>

      <td>
        The time the flow action was updated. Formatted according to the [ISO 8601 international standard](https://www.iso.org/iso-8601-date-and-time-format.html).

        Example value: `2019-04-15 08:26:00`
      </td>
    </tr>

    <tr>
      <td>
        Is Flow Archived
      </td>

      <td>
        `flow_archived`
      </td>

      <td>
        boolean
      </td>

      <td>
        True if the automation flow has been archived.

        Possible values: `true`, `false`
      </td>
    </tr>

    <tr>
      <td>
        Flow Created Date
      </td>

      <td>
        `flow_created_at`
      </td>

      <td>
        timestamp
      </td>

      <td>
        The time the automation flow was created. Formatted according to the [ISO 8601 international standard](https://www.iso.org/iso-8601-date-and-time-format.html).

        Example value: `2019-04-15 08:26:00`
      </td>
    </tr>

    <tr>
      <td>
        Flow ID
      </td>

      <td>
        `flow_id`
      </td>

      <td>
        string
      </td>

      <td>
        The unique ID for the automation flow. Assigned by the email/SMS platform.

        Example value: `YuNWdc`
      </td>
    </tr>

    <tr>
      <td>
        Flow Name
      </td>

      <td>
        `flow_name`
      </td>

      <td>
        string
      </td>

      <td>
        The name of the automation flow.

        Example value: `Abandoned cart reminder: 1-3 days`, `Joined Membership`
      </td>
    </tr>

    <tr>
      <td>
        Flow Status
      </td>

      <td>
        `flow_status`
      </td>

      <td>
        string
      </td>

      <td>
        The status of the automation flow.

        Example values: `draft`, `live`, `manual`
      </td>
    </tr>

    <tr>
      <td>
        Flow Updated Date
      </td>

      <td>
        `flow_updated_at`
      </td>

      <td>
        timestamp
      </td>

      <td>
        The time the automation flow was last updated. Formatted according to the [ISO 8601 international standard](https://www.iso.org/iso-8601-date-and-time-format.html).

        Example value: `2019-04-15 08:26:00`
      </td>
    </tr>

    <tr>
      <td>
        Message Copy
      </td>

      <td>
        `message_copy`
      </td>

      <td>
        string
      </td>

      <td>
        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: `'Can't view this email? {% web_view %} Shop our latest collection! [https://example.com/new-arrivals] Get 20% off your first order with code WELCOME20. {% unsubscribe %}'`
      </td>
    </tr>

    <tr>
      <td>
        Message ID
      </td>

      <td>
        `message_id`
      </td>

      <td>
        string
      </td>

      <td>
        The unique ID for the individual message sent as part of a campaign or flow. Assigned by the email/SMS platform.

        Example value: `SDiqmK`
      </td>
    </tr>

    <tr>
      <td>
        Message Name
      </td>

      <td>
        `message_name`
      </td>

      <td>
        string
      </td>

      <td>
        The name of the individual message sent.

        Example value: `Welcome Series: Email 2`
      </td>
    </tr>

    <tr>
      <td>
        Message Preview Text
      </td>

      <td>
        `message_preview_text`
      </td>

      <td>
        string
      </td>

      <td>
        The short snippet of text shown alongside the subject line in the recipient’s inbox, offering a preview of the message content.

        Example value: `Get 20% off your first order - limited time only!`
      </td>
    </tr>

    <tr>
      <td>
        Message Subject
      </td>

      <td>
        `message_subject`
      </td>

      <td>
        string
      </td>

      <td>
        The subject line of the email message, as displayed in the recipient's inbox.

        Example value: `New Fall Collection Just Dropped`
      </td>
    </tr>

    <tr>
      <td>
        Message Template HTML URL
      </td>

      <td>
        `message_template_html_url`
      </td>

      <td>
        string
      </td>

      <td>
        The URL of the hosted HTML template for the email message, fully formatted as rendered for recipients.

        Example value: `https://storage.googleapis.com/email-templates/klaviyo/12345/template.html`
      </td>
    </tr>

    <tr>
      <td>
        Report Type
      </td>

      <td>
        `report_type`
      </td>

      <td>
        string
      </td>

      <td>
        The type of report generated.

        Example values: `flow`, `campaign`
      </td>
    </tr>

    <tr>
      <td>
        Shop ID
      </td>

      <td>
        `shop_id`
      </td>

      <td>
        string
      </td>

      <td>
        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: `example-US.myshopify.com`, `example-EU.myshopify.com`
      </td>
    </tr>

    <tr>
      <td>
        Shop Name
      </td>

      <td>
        `shop_name`
      </td>

      <td>
        string
      </td>

      <td>
        The name of the shop. Can be used to group or filter data by shop in multi-store reports.

        Example values: `example-US`, `example-EU`
      </td>
    </tr>
  </tbody>
</Table>

# 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 campaign / flow.                                 |
| 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 for the email/SMS campaign / flow. |
| Opens              | `opens_unique`     | numeric | The total number of unique email opens for the email/SMS campaign / flow.                                        |
| Recipients         | `recipients`       | numeric | The total number of intended recipients for the email/SMS campaign / flow.                                       |