CSV import
Bring your feedback history in with a guided column-mapping wizard.
Have years of feedback in a spreadsheet, an export from another tool, or survey results? Import it in one pass. Go to Sources → Import CSV, drop the file, and a wizard maps your columns. Rows are redacted and analysed exactly like live feedback, at lower priority so they never delay real-time traffic.
Column mapping
#The wizard guesses these from your headers; you can override any of them:
| Parameter | In | Description |
|---|---|---|
Feedback text | required | The column holding the actual feedback. |
User ID | optional | Your stable ID for the user, if the export has one. |
Email | optional | The user's email — joins the row to a user, or creates one that merges later. |
Date | optional | When the feedback was created, so trends and history are accurate. The wizard shows you how the first value reads before you import, and won't accept a column that isn't dates. |
Map the email column
If your export has emails, map them. Imported rows then join the same people your app and support tools know — see Identifying users.
Everything else becomes metadata
#Columns you don't map are kept alongside each row and become filterable in Reports— plan tier, region, channel, app version. The wizard lists them before you import so you can drop any you'd rather not store.
Metadata is kept as written
Feedback text is fully redacted before storage. Metadata is only pattern-redacted, because replacing its values with placeholders would leave nothing to filter on. Columns that look like personal data — names, phone numbers, addresses — are flagged in the wizard; drop the ones you don't need.
Limits
#Up to 10 MB and 5,000 rows per import — enough for most backfills while keeping processing time and cost bounded. For larger migrations, split the file or talk to us about the batch path.