---
schema_version: "1"
id: f8ef17a72047afbb68630e6576dc10c7b49ea19c947350007d1332f031846b26
title: Create a Chat Messaging Data Extract in Marketing Cloud Engagement
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_jb_whatsapp_data_extract.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_jb_whatsapp_data_extract.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: e29cec6a5ffffb54a901a7109eeed52645e99c8f2a00880d0539452c8ba60c92
description: Use Automation Studio and Contact Builder to create Chat Messaging Data Extracts and learn more about your message metrics.
products:
  - Marketing
  - Marketing Cloud Engagement
release: "264"
---
# Create a Chat Messaging Data Extract in Marketing Cloud Engagement

Use Automation Studio and Contact Builder to create Chat Messaging Data Extracts and learn more about your message metrics.

1. In Automation Studio, click **New Automation**.
2. Drag the Data Extract activity to the Automation canvas.
3. Click **Choose**.
4. Click **Create New Data Extract** and create a data extract file.
    1. Select **ChatMessagingDetailExtract**.
        
        If you’re using wildcards in your file name, only use trailing ones. For example, test\_mo\_log\_%%Year%%%%Month%%%%Day%%.zip.
    2. Channel ID: The phone number for your WhatsApp channel. Use the country code and phone number with no symbols.
    3. Channel Type: WHATSAPP.
    4. Include MOLog: Provides a raw data file with inbound messages from customers.
    5. Include Tracking Detail: Provides detail disposition for Sends and the corresponding Inbound Tracking. If you choose to not include tracking details, some delivery receipts aren’t included if they’re near the end of the set sending time period. If you use a rolling range, you get a complete dataset.
    6. Include Potential Bounces: WhatsApp doesn’t provide unsubscribe information. If a user hasn’t received a message three times in the last 30 days, they’re counted as bounced users. It’s possible bounced users opted out and blocked the brand’s WhatsApp channel.
5. Create a File Transfer activity. Use the same file-naming pattern as the Data Extract activity.
    
    When you run the data extract, the file is stored in a Salesforce Safehouse. The file transfer activity moves the file to a configure file location.
6. [Retrieve your files from the SFTP server](https://help.salesforce.com/s/articleView?id=mktg.mc_overview_ftp_accounts.htm&language=en_US).
    
    ![FTP file name examples](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_journeys_and_automations-264-0-0-production-enus/e08cdd71-c1c1-4ae5-a5e9-8a6dad583ad4/mc_journeys_and_automations/images/mc_jb_whatsapp_ftp.png)
    
    - Tracking file name: chat\_{filename}\_tracking.csv
    - Inbound messages file name: chat\_{filename}\_inboundmessagelogs.csv
    - Potential unsubscribes file name: chat\_{filename}\_potentialunsubs.csv
    - Example log file name with date: chat\_test\_mo\_log%%Year%%%%Month%%%%Day%%\_tracking.csv
7. Import your information into a data extract.
    1. In Contact Builder, [create a data extension](https://help.salesforce.com/s/articleView?id=mktg.mc_cab_create_a_new_data_extension.htm&language=en_US).
    2. In Contact Builder, [create an import definition](https://help.salesforce.com/s/articleView?id=mktg.mc_cab_create_a_new_import_definition.htm&language=en_US).

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small " summary="
          Track File Details
        ">
        <caption>
          Track File Details
        </caption>
        <colgroup>
          <col style="width:47.06927175843694%">
          <col style="width:36.9449378330373%">
          <col style="width:15.985790408525755%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d52422e208"> Name </th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d52422e211"> Description </th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d52422e214"> Data Type </th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e208 ">TrackingType</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e211 ">Send disposition in Marketing Cloud Engagement. Is either DeliveryReport or
              SEND</td>

            <td data-label="Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e214 ">string</td>

          </tr>
          <tr class="">
            <td data-label="Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e208 ">SendType</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e211 ">How the send was initiated: through Journey Builder or Transactional API or as a
              default response.</td>

            <td data-label="Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e214 ">string</td>

          </tr>
          <tr class="">
            <td data-label="Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e208 ">MID</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e211 ">Member ID for the sender</td>

            <td data-label="Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e214 "> bigint</td>

          </tr>
          <tr class="">
            <td data-label="Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e208 ">EID</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e211 ">Enterprise ID number for the sender</td>

            <td data-label="Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e214 ">bigint</td>

          </tr>
          <tr class="">
            <td data-label="Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e208 ">ContactKey</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e211 ">Contact key of the receiver</td>

            <td data-label="Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e214 ">string</td>

          </tr>
          <tr class="">
            <td data-label="Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e208 ">MobileNumber</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e211 ">Phone number of receiver</td>

            <td data-label="Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e214 ">string</td>

          </tr>
          <tr class="">
            <td data-label="Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e208 ">EventDateUTC</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e211 ">UTC date and time of the event</td>

            <td data-label="Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e214 ">datetime</td>

          </tr>
          <tr class="">
            <td data-label="Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e208 ">AppID</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e211 ">Application ID of the provider</td>

            <td data-label="Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e214 ">string</td>

          </tr>
          <tr class="">
            <td data-label="Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e208 ">ChannelID</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e211 ">Phone number of the registered channel</td>

            <td data-label="Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e214 ">string</td>

          </tr>
          <tr class="">
            <td data-label="Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e208 ">ChannelType</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e211 ">Channel platform (WhatsApp)</td>

            <td data-label="Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e214 ">string</td>

          </tr>
          <tr class="">
            <td data-label="Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e208 ">ConversationType</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e211 ">Meta-defined conversation category with one of these values: Marketing, Utility,
              Authentication, Service, Referral. ConversationType is assigned only for sent or delivered
              messages that have a TrackingType value of DeliveryReport.</td>

            <td data-label="Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e214 ">string</td>

          </tr>
          <tr class="">
            <td data-label="Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e208 ">ActivityName</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e211 ">Name of message activity related to the send for the journey (WhatsApp)</td>

            <td data-label="Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e214 ">string</td>

          </tr>
          <tr class="">
            <td data-label="Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e208 ">ChannelName</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e211 ">Name of channel used</td>

            <td data-label="Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e214 ">string</td>

          </tr>
          <tr class="">
            <td data-label="Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e208 ">Status</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e211 ">Send status provided by sender or Marketing Cloud Engagement</td>

            <td data-label="Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e214 ">string</td>

          </tr>
          <tr class="">
            <td data-label="Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e208 ">Reason</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e211 ">If Status is negative, this field provides further details</td>

            <td data-label="Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e214 ">string</td>

          </tr>
          <tr class="">
            <td data-label="Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e208 ">JBDefinitionID</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e211 ">Unique identifier for the journey a message was deployed from</td>

            <td data-label="Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e214 ">unique identifier</td>

          </tr>
          <tr class="">
            <td data-label="Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e208 ">SendIdentifier</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e211 ">
              <p>Internal Engagement identifier for a send. </p>
              <p style="margin-bottom:0;">This identifier associates a unique
                SEND”with the corresponding “DeliveryReport” information. Order or date can’t be verified
                when sending to the same contact many times. This field is your source of truth for data
                association of send and delivery reports.</p>
            </td>

            <td data-label="Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e214 ">unique identifier</td>

          </tr>
          <tr class="">
            <td data-label="Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e208 ">AssetID</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e211 ">Asset ID associated with the Send. Available on Send type only.</td>

            <td data-label="Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e214 ">bigint</td>

          </tr>
          <tr class="">
            <td data-label="Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e208 ">MessageTypeID</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e211 ">Internal send type ID</td>

            <td data-label="Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e214 ">int</td>

          </tr>
          <tr class="">
            <td data-label="Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e208 ">JBActivityID</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e211 ">Unique identifier for the message within the journey </td>

            <td data-label="Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d52422e214 ">unique identifier</td>

          </tr>
        </tbody>
      </table>

Inbound Message Details   
| Name | Description | Data Type |
| --- | --- | --- |
| ChatMessagingMOLogID | Unique database identifier in sequential order | bigint |
| ChannelID | Phone number of the registered channel | string |
| ChannelType | Channel platform (WhatsApp) | string |
| MobileNumber | Phone number of contact who responded to the channel | string |
| MessageData | JSON-formatted data from our partner. The Text field displays inbound text. | string |
| DateCreatedUTC | UTC date and time the inbound message was received in Engagement | datetime |

Potential Unsubscribe Details   
| Name | Description | Data Type |
| --- | --- | --- |
| MID | Member ID for the sender | bigint |
| EID | Enterprise ID number for the sender | bigint |
| ContactKey | Contact key of the receiver | string |
| MobileNumber | Phone number of receiver | string |
| ChannelID | Phone number of the registered channel | string |
| ChannelType | Channel platform (WhatsApp) | string |
| ChannelName | Name of channel provided by customer | string |
| FirstDateUTC | UTC date and time of first send without delivery tracking | datetime |
| LastDateUTC | UTC date and time of last send without delivery tracking | datetime |

A user is marked as a potential unsubscribe if:

- At least three messages have failed to send to the user
- There are no successful sends to the user during the report’s selected time window

A message is defined as failed to send if it has a Failed status or a Not Sent status with Reason 100.