CSConjoint Survey

How to Prepare Clean Analysis Files

Move from raw responses to analysis CSVs, respondent files, codebooks, and scripts.

The Short Version

Move from raw responses to analysis CSVs, respondent files, codebooks, and scripts. A practical way to begin is to open Results after final fielding, then set final exclusion rules. Finish by making sure you store all files in one replication folder. The full walkthrough below explains each part in order.

Is This Guide for You?

Researchers preparing files for R, Stata, Python, SPSS, coauthors, or replication archives.

Follow These Steps

Work through these 7 steps at your own pace. The wording is intentionally practical, and you can return to the checklist at the end when you are ready to review your work.

  1. Open Results after final fielding.
  2. Set final exclusion rules.
  3. Export raw responses for audit records.
  4. Export analysis CSV for profile-level conjoint analysis.
  5. Export respondent-level clean CSV for covariates.
  6. Export codebook and starter scripts.
  7. Store all files in one replication folder.

What This Helps You Accomplish

Clean analysis files keep the profile-level conjoint structure intact while preserving enough raw data to audit decisions. For studies without conjoint tasks, Analysis CSV exports one respondent-level row per completed response, including pre-treatment answers, randomized survey-experiment arm columns, and VADER/word-count metrics for open-ended text questions.

A Quick Confidence Check

  • Keep raw and clean files separate.
  • Use respondent IDs for clustering.
  • Save codebook and scripts.
  • Record the export date.

Common Questions

Can I use this guide if I am new to this?

Yes. Researchers preparing files for R, Stata, Python, SPSS, coauthors, or replication archives. Follow the steps in order, start with a small test, and use the final checklist before you field or report anything important.

What is the simplest way to get started?

Begin by open Results after final fielding. Next, set final exclusion rules. You do not need to perfect every setting before running a small preview or pilot.

How do I know when I am ready?

Use the confidence check above. In particular: Keep raw and clean files separate. Use respondent IDs for clustering. Save codebook and scripts. Record the export date. When the decision is consequential, keep your study documentation and ask a qualified colleague or methods reviewer to examine the design as well.

Related Guides

Research artifact: sample data, codebook, and scripts

Research Pathways

Product names and fielding platforms mentioned in this guide belong to their respective owners. Conjoint Survey is an independent academic research tool and is not affiliated with, sponsored by, or endorsed by those services.