Protect your schema from unexpected data

Sometimes, Amplitude might receive data from your app that it doesn't know how to handle. This is usually the result of a schema violation, which means the data Amplitude received isn't accounted for in your schema. If you see a schema violation, you probably didn't plan for that data type or value when you set up your schema.

You can tell Amplitude how to handle these situations by configuring your schema settings. You can configure responses for three types of schema violations. Find your schema settings by going to Amplitude Data and navigating to Settings > Schema Settings.

Unplanned event types

Sometimes, Amplitude may receive an event that isn't part of your schema, or that you didn't plan earlier. This is an unplanned event type. You can configure Amplitude to respond in these ways:

• Mark As Unexpected: Amplitude ingests the event, triggers a warning, and sends a notification to the designated subscribers. The event's category in drop-downs is "Unexpected" until you approve it.
• Reject: Amplitude rejects the event and sends a notification to the designated subscribers. Amplitude doesn't store the event or its properties.

Unplanned event or user properties

When Amplitude encounters an event or user property that isn't part of your schema, or that you didn't plan earlier, it considers the property to be an unplanned event or user property. You can configure Amplitude to respond in the following ways:

• Mark As Unexpected: Amplitude ingests the property, triggers a warning, and sends a notification to the designated subscribers.
• Reject: Amplitude rejects the property and sends a notification to the designated subscribers. Amplitude stores the event, but not the properties.

Unplanned event or user property values

When Amplitude receives an event property value that isn't part of your schema, or that you didn't plan earlier, it considers the value an unplanned property value. For example, an event property value arrives as a string, but your schema expected a number. You can configure Amplitude to respond to an unplanned property value in the following ways:

• Mark As Unexpected: Amplitude ingests the property, triggers a warning, and sends a notification to the designated subscribers.
• Reject: Amplitude rejects the property, triggers a warning, and sends a notification to the designated subscribers. Amplitude stores the event, but not the properties.

If Amplitude rejects your event data and you want to ingest it, add the events or properties to your schema by planning a new event or property.

View validation errors

After you initialize your schema and define your expected events and event properties, your schema can validate live data coming into Amplitude. If you configured your schema to trigger a warning for unexpected events or properties, Amplitude logs an error in the validation errors panel.

View validation errors by going to Amplitude Data and navigating to Settings > Schema Settings > Validation Errors. Any errors triggered in the last 24 hours appear on this page, whether or not the event or property has since been approved or rejected. If no errors appear on the validation page, there haven't been any violations in the past 24 hours. This doesn't mean that all violations are fixed; it only means Amplitude hasn't encountered them in that time.

Select Subscribe to set up email alerts for validation errors.

Manage subscribers

You can designate specific users to receive email notifications of any schema violations. Select Manage Subscribers at the top right of your schema options.