Historical Q&A Feed
This optional feed is used to import pre-existing Q&A data into Emplifi Ratings & Reviews Community Q&A.
To import pre-existing Q&A data, you must provide data files to your Emplifi Customer Success Manager for questions, answers (if any), and replies (if any). Accepted file formats are comma-separated (.csv), tab-separated (.tsv), and Excel (.xlsx).
Questions Data File
A question is always associated with a product.
Header | Required? | Description |
---|---|---|
Question ID | Yes | Unique identifier for the question. |
SKU | Yes | Product SKU. |
Text | Yes | Question text. |
Submission Date | Yes | Date the question was submitted. You can include the time, but we will truncate to date only. |
User name | Yes | Name of the question asker. We prefer first name and last name, but display name is acceptable. If necessary, we can use generic data such as "[company name] shopper". |
Status | No | Display status of the question. Can be anything that indicates a two-part division between displayed questions and hidden questions. Examples:
If you have more than two statuses, you must explain which statuses should map to displayed and which should map to hidden. |
Answers Data File
An answer is always associated with a question and a product.
Header | Required? | Description |
---|---|---|
Answer ID | Yes | Unique identifier for the answer. |
Question ID | Yes | Unique identifier for the question. |
SKU | Yes | Product SKU. |
Text | Yes | Answer text. |
Submission Date | Yes | Date the answer was submitted. You can include the time, but we will truncate to date only. |
User name | Yes | Name of the answerer. We prefer first name and last name, but display name is acceptable. If necessary, we can use generic data such as "[company name] shopper". |
Status | No | Display status of the answer. Can be anything that indicates a two-part division between displayed answers and hidden answers. Examples:
If you have more than two statuses, you must explain which statuses should map to displayed and which should map to hidden. |
Staff | No | Boolean. Indicates whether this is a staff answer. |
Replies Data File
A reply is always associated with an answer, and is indirectly associated with a question through that answer. Users can submit replies to answers or replies to other replies.
Header | Required? | Description |
---|---|---|
Reply ID | Yes | Unique identifier for the reply. |
Answer ID | Yes | Unique identifier for the answer. |
Parent Reply ID | No | Unique identifier for the reply this reply is responding to. Enables conversation threads. Leave empty when replying to an answer. |
User name | Yes | Name of the replier. We prefer first name and last name, but display name is acceptable. If necessary, we can use generic data such as "[company name] shopper". |
Status | No | Display status of the reply. Can be anything that indicates a two-part division between displayed replies and hidden replies. Examples:
If you have more than two statuses, you must explain which statuses should map to displayed and which should map to hidden. |