Skip to main content
Skip to article
  • Qualtrics Platform
    Qualtrics Platform
  • Customer Journey Optimizer
    Customer Journey Optimizer
  • XM Discover
    XM Discover
  • Qualtrics Social Connect
    Qualtrics Social Connect

XM Discover Data Formats Overview

Was this helpful?


This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

The feedback you submit here is used only to help improve this page.

That’s great! Thank you for your feedback!

Thank you for your feedback!

About XM Discover Data Formats

XM Discover supports three distinct data formats which you can upload using different file types.

The following connectors support loading data through files:

Individual Feedback

Individual feedback format is used for documents that present data as a single-row, or “flat” object. Each document may contain several verbatim fields, but usually these come from a single author (for example, when a survey contains more than one open-ended question).

You can upload individual feedback documents through:

Digital Interactions

Digital interactions format is used for documents that contain conversational data such as chats.

Digital interactions must follow Qualtrics conversational format that aids the system in understanding key details such as speakers, sequences, and conversational events. A similar conversational format is used for call transcripts.

You can upload digital interactions through:

Call Transcripts

Call transcripts format is used for documents that contain conversational data such as support calls.

Call transcripts must follow Qualtrics conversational format that aids the system in understanding key details such as speakers, sequences, and conversational events. A similar conversational format is used for digital interactions.

You can upload call transcripts through:

Sample File Errors

Various Connector jobs allow you to upload sample files (such as ad-hoc file uploads, files, or XM Discover link jobs). If your sample file is misconfigured, then you will see an error message prompting you to correct any issues. This section covers the different possible errors and how to fix them.

CSV and Excel Errors

The following errors are possible for CSV and Excel (XLS, XLSX) sample files:

  • File should have required property “REQUIRED_FIELD”: A required field is missing. See the documentation for that specific connector for more information about the fields required for that connection and make sure the listed field is included in your sample file.
  • Inconsistent participantType values for participantId ID: Each participant in a conversation can have only one participantType value defined. Review your sample file for any participants who have multiple participantTypes.
  • Number of columns does not match headers: Each column must have a header and the number of columns in every row must be equal.
  • Row ROW_NUMBER of column COLUMN_NAME should match date-time format ISO 8601 YYYY-MM-DDThh:mm:ss.sZ: For dates, use the ISO 8601 format with seconds precision.

JSON Errors

The following errors are possible for JSON files:

  • Error at JSON_DATA_PATH: should be a string of date-time format ISO 8601 YYYY-MM-DDThh:mm:ss.sZ: For dates, use the ISO 8601 format with seconds precision.
  • Error at JSON_DATA_PATH: should be a string of value AGENT, CLIENT, or TYPE_UNKNOWN: The participantType at the specified path is invalid. Only the following values should be used:
    • AGENT indicates a company representative or a chatbot.
    • CLIENT indicates a customer.
    • TYPE_UNKNOWN indicates an unidentified participant.
  • Error at JSON_DATA_PATH: should be DATA_TYPE: The field value is the wrong data type. Make sure the data type matches what’s in your connector’s data mapping.
  • Error at JSON_DATA_PATH: should have property REQUIRED_FIELD: A required field is missing. See the documentation for that specific connector for more information about the fields required for that connection and make sure the listed field is included in your sample file.
  • Error at JSON_DATA_PATH: Participant with participantId ID can’t be found in participants: Participant IDs must match one of the IDs provided in the list of participants. Make sure the listed ID is included in your sample file.