This article helps you:
Understand the difference between drop and block filters
Learn how to block and delete events or properties
Learn how to remove corrupt data from analysis
Data on Amplitude is immutable once ingested. Amplitude Data provides you with several methods to prevent invalid or incorrect data from appearing in your Amplitude analyses. You can create a drop filter, create a block filter, block events and properties, or delete events and properties. This article describes each technique, as well as the differences between them.
To permanently delete data, use Amplitude's self-service data deletion feature.
You may find you've loaded incorrect data and want to filter it out from queries. Amplitude Data's drop filters feature allows you to remove specific event data from your charts at query time. These events aren't deleted, and they can be restored to your charts simply by editing or deleting the drop filter. Drop filters don't apply to data exports.
As query-side filters that aren't applied during data ingestion, drop filters don't affect your event volume limit.
To create a drop filter, follow these steps:
Make sure you’re on main
, as filters aren't accessible from any other branch
In the left-hand sidebar, click Filters, then select the Drop Filters tab.
Click + Create Drop Filter to open the Filter Configuration fly-out panel.
Click Select event ... to choose the event you want to filter on.
Optionally, click + where to include any relevant properties that will refine your filter. For example, perhaps you want to filter out all purchase events that come from a specific geographical location. Simply select that location from the list of properties and set the evaluation to is not equal
.
Specify the time range for the events you’d like Amplitude Data to drop-filter out.
When you’re ready, click Drop Data to initiate the drop filter.
If you want to edit or delete a drop filter, click on its name in the drop filter list. In the fly-out panel that appears on the right, make your edits and click Update Drop Filter.
There are some things about drop filters to keep in mind:
Block filters enable you to stop data ingestion for events and properties that you specify based on criteria you define. Blocking Amplitude from ingesting data can help you you need to act quickly before you update your code.
Block filters enable you to:
When you add or remove a block filter, allow up to 10 minutes for the change to take effect. As soon as the filter is active, it blocks Amplitude from ingesting matching data.
Amplitude doesn't collect data for blocked events or properties. As a result, you can't recover information about blocked data at a later time, because Amplitude never ingests it. If you think you may need data at some point in the future, consider hiding the event or property instead.
To create a block filter:
main
branch in Data.Block events based on the value of up to three event properties.
When you block events based on property values, Amplitude compares your filter against the raw stringified values sent to Amplitude. Knowing the data type is important in the following scenarios:
true
or false
, Amplitude displays the value as "True" or "False". To use this in a Block filter, you need to specify the exact value sent as a string. In this case, true
or false
.To find raw property values, use the Event Explorer to view an example of the event you want to block.
Create Block filters from your Events or Properties list.
main
branch.Custom events are a virtual grouping of your ingested events, aren't blockable. Instead, block the indivdual events that make up the custom event.
You can prevent Amplitude Data from ingesting data on a specific event, event property, or user property by blocking it. Amplitude Data immediately stops processing data for that event or property until you decide to unblock it.
Because Amplitude Data doesn't ingest any data for blocked events or properties, this means you can't recover any information about them at any future date. If you don't wish to display a specific event or property but think you may someday need this data, consider hiding the event or property instead.
To block an event or property, follow these steps:
main
branch. You can only block events and properties from there.You can't block custom events.
If you ingest events or properties that you no longer need, you can delete them from your plan.
When you delete an event or property, Amplitude blocks it from future ingestion and removes it from chart drop-downs to prevent future querying. The event or property doesn't count toward your monthly event volume or instrumentation limit.
Deleting an event or property doesn't remove historical data. Charts that reference a deleted event load with data from before you deleted the event and indicates the event is deleted.
Deleted user properties still appear on events that are already ingested, and you can still see them in historical user stream data.
To delete an event or property:
You can undelete a deleted event or property.
To delete a user entirely, use the User Privacy API. This API lets you delete a user, their events, and any associated data, and helps you keep compliant with data laws and regulations.
Thanks for your feedback!
October 8th, 2024
Need help? Contact Support
Visit Amplitude.com
Have a look at the Amplitude Blog
Learn more at Amplitude Academy
© 2024 Amplitude, Inc. All rights reserved. Amplitude is a registered trademark of Amplitude, Inc.