This article helps you:
Manage the events, event properties, and user properties of your tracking plan via .CSV import and export
Understand the data fields and values needed for importing and how they compare to exported files
In Amplitude Data, you can view and manage event types, event properties, and user properties piece by piece, but you may want to see a holistic view of your entire tracking plan's schema and make bulk changes to the schema instead.
Amplitude lets you import and export your schema with .CSV to plan new events and properties, edit categories and descriptions, and generate bulk changes.
This article covers the differences between using import and export for events and event properties versus user properties.
Follow the below steps to import or export events and event properties:
Navigate to Data, and click Events under your tracking plan in the left side pane.
If you wish to import, click 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 click Upload and choose the file from your desired location. If not, click template to download a template .CSV to update for importing.
The imported events and event properties appear in a branch named import.
Once you’re sure the imported tracking plan updates are correct, you can merge the changes back into the main branch.
If you want to export events and event properties from your tracking plan, click 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, click Download.
Downloaded .CSV files of your tracking plan contain additional fields not required for import. The next section 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, nor default Amplitude entities.
The events and event properties .CSV file requires a specific schema for a successful import. The table below highlights the required schema by entity type. There are some things to note:
Action
Ignore
: No changes made to the entity nor its subpropertiesRemove
: Event and property groups can be removed from the tracking plan. The remove value doesn't affect individual properties. Removing an event or property group disassociates related properties, and changes a live property’s status to unexpected. The remove value doesn't delete an entity, nor does it stop ingestion.<blank>
: Creates or updates an entity and it’s associated sub-entitiesArray min items
Array max items
Array unique items
TRUE
: Array has unique items<any>
: Assumes array doesn't have unique itemsConst value
Enum values
Event activity
Active
Inactive
. Marking an event as inactive applies retroactively and immediately, and excludes the event from the Any Active Event
metric.Event hidden from dropdowns
True
: Event is hidden in event dropdownsFalse
: Event is visible in event dropdowns<blank>
: Retains the current valueEvent hidden from persona results
True
: Event is hidden from persona resultsFalse
: Event is visible in persona results<blank>
: Retains the current valueEvent hidden from pathfinder
True
: Event is hidden from pathfinderFalse
: Event is visible in pathfinder<blank>
: Retains the current valueEvent hidden from timeline
True
: Event is hidden from timelinesFalse
: Event is visible in timelines<blank>
: Retains the current valueEvent category
Event display name
Event property name
Event source
Number property value min
Number property value max
Number is integer
True
: Property is an integerFalse
or <blank>
: Property isn't an integerObject type
Event
Property Group
Object name
Object owner
<blank>
removes the owner if one exists on the event or property groupObject description
Property type
Event Property
Event Property Group
Property group names
Property description
Property value type
string
number
boolean
any
enum
const
Property required
True
: Property is requiredFalse
or <blank>
: Property is optionalProperty visibility
VISIBLE
: Property is visible in chartsHIDDEN
: Property is hidden in charts<blank>
: Retains the current valueProperty is array
True
: Property is an arrayFalse
or <blank>
: Property isn't an arrayProperty regex
String property value min length
String property value max length
Tags
The following list includes additional fields found in the .CSV export of your tracking plan’s events and event properties.
Action
Ignore
: The user property is unexpected, blocked or deleted.<blank>
: The user property is planned or live.Event first seen
mm/dd/yyyy
Event last seen
mm/dd/yyyy
Property first seen
mm/dd/yyyy
Property last seen
mm/dd/yyyy
Follow the below steps to import or export user properties:
The imported events and event properties appear in a branch named import.
The next section defines the user properties .CSV import file structure and the additional columns seen in the user properties export.
The list below highlights the required schema for the user properties .CSV file import. There are some things to note:
Action
Ignore
: No changes will be made to the user property.Remove
: The user property is removed from the tracking plan. The removed value doesn't delete a user property, nor does it stop its ingestion.<blank>
: Creates the user property if it did not already exist; or updates the user property if it did exist.Array min items
Array max items
Array unique items
TRUE
: Array has unique items<any>
: Assumes array doesn't have unique itemsConst value
Enum values
Number property value min
Number property value max
Number is integer
True
: Property is an integerFalse
or <blank>
: Property isn't an integerProperty type
Property name
Property description
Property visibility
VISIBLE
: Property is visible in chartsHIDDEN
: Property is hidden in charts<blank>
: Retains the current valueProperty value type
string
number
boolean
any
enum
const
Property is array
True
: Property is an arrayFalse
or <blank>
: Property isn't an arrayProperty regex
String property value min length
String property value max length
The following list includes additional fields found in the .CSV export of your tracking plan’s user properties.
Action
Ignore
: The user property is unexpected, blocked or deleted.<blank>
: The user property is planned or live.Property first seen
mm/dd/yyyy
Property last seen
mm/dd/yyyy
June 19th, 2024
Need help? Contact Support
Visit Amplitude.com
Have a look at the Amplitude Blog
Learn more at Amplitude Academy
© 2025 Amplitude, Inc. All rights reserved. Amplitude is a registered trademark of Amplitude, Inc.