# Data Export CSV

Schema: #/components/schemas/data_export_csv

Method: SCHEMA
Version: 2.7
Security: bearerAuth

## Schema fields:

  - `user_id` (string)
    The user_id of the user who was sent the message.

  - `user_external_id` (string)
    The external_user_id of the user who was sent the message

  - `company_id` (string)
    The company ID of the user in relation to the message that was sent. Will return -1 if no company is present.

  - `email` (string)
    The users email who was sent the message.

  - `name` (string)
    The full name of the user receiving the message

  - `ruleset_id` (string)
    The id of the message.

  - `content_id` (string)
    The specific content that was received. In an A/B test each version has its own Content ID.

  - `content_type` (string)
    Email, Chat, Post etc.

  - `content_title` (string)
    The title of the content you see in your Intercom workspace.

  - `ruleset_version_id` (string)
    As you edit content we record new versions. This ID can help you determine which version of a piece of content that was received.

  - `receipt_id` (string)
    ID for this receipt. Will be included with any related stats in other files to identify this specific delivery of a message.

  - `received_at` (integer)
    Timestamp for when the receipt was recorded.

  - `series_id` (string)
    The id of the series that this content is part of. Will return -1 if not part of a series.

  - `series_title` (string)
    The title of the series that this content is part of.

  - `node_id` (string)
    The id of the series node that this ruleset is associated with. Each block in a series has a corresponding node_id.

  - `first_reply` (integer)
    The first time a user replied to this message if the content was able to receive replies. Only events within the export job's requested date range are counted.

  - `first_completion` (integer)
    The first time a user completed this message if the content was able to be completed e.g. Tours, Surveys. Only events within the export job's requested date range are counted.

  - `first_series_completion` (integer)
    The first time the series this message was a part of was completed by the user. Only events within the export job's requested date range are counted.

  - `first_series_disengagement` (integer)
    The first time the series this message was a part of was disengaged by the user. Only events within the export job's requested date range are counted.

  - `first_series_exit` (integer)
    The first time the series this message was a part of was exited by the user. Only events within the export job's requested date range are counted.

  - `first_goal_success` (integer)
    The first time the user met this messages associated goal if one exists. Only events within the export job's requested date range are counted.

  - `first_open` (integer)
    The first time the user opened this message. Only events within the export job's requested date range are counted.

  - `first_click` (integer)
    The first time the series the user clicked on a link within this message. Only events within the export job's requested date range are counted.

  - `first_dismisall` (integer)
    The first time the series the user dismissed this message. Only events within the export job's requested date range are counted.

  - `first_unsubscribe` (integer)
    The first time the user unsubscribed from this message. Only events within the export job's requested date range are counted.

  - `first_hard_bounce` (integer)
    The first time this message hard bounced for this user. Only events within the export job's requested date range are counted.

