Understanding Why Some Events Can Be Dropped and Others Cannot

Hi 鈴木宏昌, Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋

In Mixpanel, you can drop events and properties through the Lexicon feature, which allows you to intercept and prevent new data from being stored. When you drop an event or property, Mixpanel won't store any new data for that event or property going forward. However, it's important to note that any data that was already ingested before dropping will still remain in your project. Only project owners have the permission to drop events and properties, and it takes a few hours for Mixpanel to process the dropped event.There's no inherent difference between events that can or cannot be dropped - all events can technically be dropped through Lexicon. The process involves: 1. Selecting the event you want to drop 2. Clicking the Drop icon 3. Confirming the action (with awareness that you cannot recover the data)Some common reasons for dropping events include: - Removing sensitive data (like passwords or credit card information) - Cost efficiency (removing events that aren't useful to save on your event quota) - Better organization (reducing clutter in your Mixpanel project)If you later decide you need the event again, you can "undrop" it to resume collecting that data.Lexicon: Dropping DataNote that dropping events is different from hiding events. Hiding events doesn't affect data ingestion - hidden events will continue to be ingested and count toward your data allowance, they're just not visible in your interface by default.Is there a specific event you're having trouble dropping?

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.