Update Existing Mobile App Event Schemas

Use care when updating events that are being used in running journeys. Changing the names or data types of app events can cause errors if newly defined event doesn't match the inbound data coming from the MobilePush SDK.

Note
Note To edit existing events, upload an updated .csv file, and then select the option Add and update events for your selected apps. To delete existing events, upload an updated .csv file with the removed event, and then select the option Overwrite and Replace existing schema for your selected apps.

Constructive Schema Changes

Extending an event: If you add attributes to an existing event, this action doesn't change your active running journeys that are using that event.

Example
Example A Purchase event exists with a Price attribute. You later upload a new schema with the same Price definition, but add a Currency attribute. Since the Price attribute hasn't changed, journeys using that event aren't disrupted.

Destructive Schema Changes

Deleting an Event or Attribute: If you Overwrite and Replace your existing event schema with a new schema that doesn't include the same event names or attributes, the event definitions and attributes are deleted from your account. As a result, all journeys using those definitions and attributes are affected.

Example
Example You have a Purchase event that's referenced by many journeys. You later upload a new schema file that doesn't contain any information about this Purchase event. You select Overwrite and Replace the existing schema for your selected apps. As a result, Journey Builder is unable to listen for Purchase events because the Purchase event schema is deleted from your account.