.CSV import and export
Import and export your tracking plan as a .CSV to make bulk schema changes in Amplitude Data. The .CSV round-trip covers events, event properties, and user properties, and supports planning new events, editing categories and descriptions, and applying changes in one upload instead of editing entities one at a time.
Use .CSV import when you need to make bulk schema edits across many events or properties at once. For programmatic, automated, or scripted schema changes, use the Taxonomy API instead.
Events and event properties
Follow these steps to import or export events and event properties:
Navigate to Data, and select Events under your tracking plan in the left side pane.
To import, select the import icon to open the import modal.
If your import file is ready to upload and follows the expected schema for events and event properties, you can drop your .CSV file or select Upload and choose the file from your location. If not, select template to download a template .CSV to update for importing.
The imported events and event properties appear in a branch named import.
After you confirm the imported tracking plan updates are correct, you can merge the changes back into the main branch.
To export events and event properties from your tracking plan, select the export icon instead.
In the export modal that appears, choose whether to download your tracking plan's schema or a .CSV file template. Then, select Download.
Downloaded .CSV files of your tracking plan contain additional fields not required for import. The .CSV file schema reference defines the events and event properties .CSV import file structure and the additional columns seen in the exported file.
The import and export features don't support custom events, transformations, or default Amplitude entities.
User properties
Follow these steps to import or export user properties:
- Navigate to Data, and select Properties under Tracking Plan in the left side pane. Then select User Properties.
- Select the import icon to open the import modal.
- If your import file is ready to upload and follows the expected user properties schema, you can drop your .CSV file or select Upload and choose the file from your location. If not, select template to download a template .CSV to update for importing.
The imported events and event properties appear in a branch named import.
- After you confirm the imported tracking plan updates are correct, you can merge the changes back into the main branch.
- To export user properties from your tracking plan, select the export icon instead.
- In the export modal that appears, choose whether to download your tracking plan's schema or a .CSV file template. Then, select Download.
The .CSV file schema reference defines the user properties .CSV import file structure and the additional columns seen in the user properties export.
Common questions
Export options for raw chart or event data
These questions all have the same answer:
- How do I export raw data for a chart or event?
- Can I export the raw event data for the events included in this chart instead of the chart results?
- How do I export a .CSV of all occurrences of a specific event?
- How do I see the data that was pulled into this chart?
- Can I see event and user property values for every instance of this event in the last 30 days?
There's no way to export selected raw data for a chart or all data for selected events. Amplitude is built to perform large-scale, complex analyses inside the application, so isolating and exporting event data in a SQL-like manner isn't supported. A few alternatives:
- Export API: to export all values of an event and its event properties, use Amplitude's Export API. It exports all events across a specified time range and returns them in JSON format. From there, you can extract the specific events you want. If your data exceeds the Export API size limit, use Amazon S3 Export instead.
- Amazon S3 Export: integrate Amplitude with Amazon S3 to export your event data to an S3 bucket. This integration is available on all accounts, including the free plan. Refer to Amazon S3 Export.
How does Amplitude determine the structure of the .CSV file when exporting from an Event Segmentation chart?
Amplitude uses the breakdown data table as a guide when creating the .CSV. Amplitude mirrors the format and structure of the table in the .CSV.
Why isn't the .CSV file showing all the possible values of the user or event property?
There are limits on the number of values that appear in a .CSV. The limits differ from chart to chart. Refer to Limits and quotas.
Why is the value of a user property different between the chart and the .CSV export?
When you download users from the chart through Microscope, the .CSV contains the most recent property values for the user. The chart returns the property value at the time of the event.
The same applies when the .CSV has property values listed as "none" in the chart: the .CSV shows the most recent value, while the chart shows the value at the time of the event.
Why are there leading spaces (tabs) in my exported .CSV file?
By default, leading empty spaces can appear in the cells of an exported .CSV. To change the default:
- Go to Personal settings.
- Go to Profile.
- Enable Always Remove Leading Spaces from Export under Site Settings.
Refer to Manage your settings for more.
Was this helpful?
For AI agents: a documentation index is available at /docs/llms.txt. Append .md to any page URL for markdown, or send Accept: text/markdown.