amp event-properties

amp event-properties manages properties associated with an event. Read commands require taxonomy:read; create, update, and delete require taxonomy:write.

`amp event-properties list`

bash

amp event-properties list --project <project_id> --event <event_type> --limit 5

The result includes ingested-only properties that aren't in the tracking plan. Check is_in_schema before updating a property.

`amp event-properties create`

bash

amp event-properties create --project <project_id> --event <event_type> \
  --property <property_name> --data-type string

Creating an ingested-only property promotes it into the tracking plan. If the property already exists in the plan, the command returns it without changing it.

`amp event-properties get`

bash

amp event-properties get --project <project_id> --event <event_type> \
  --property <property_name>

`amp event-properties update`

bash

amp event-properties update --project <project_id> --event <event_type> \
  --property <property_name> --description "Updated description"

You can update properties in the tracking plan. Updating an ingested-only property returns 422 with error_code: "not_in_schema"; create it first to promote it. For array fields such as enum_values and classifications, an update replaces the entire array.

`amp event-properties delete`

bash

amp event-properties delete --project <project_id> --event <event_type> \
  --property <property_name> --dry-run
amp event-properties delete --project <project_id> --event <event_type> \
  --property <property_name> --yes

Preview the deletion with --dry-run. At a terminal, the delete command asks for confirmation; pass --yes to skip the prompt.

Run amp event-properties <command> --help for pagination, search, property metadata, and other command-specific flags.

Was this helpful?