Remove event properties from specific events

In the Data interface I can remove event properties from our tracking plan. However, this removes the event property in it’s entirety, from all events. I’d like to be able to remove event properties only from specific events in our tracking plan.

Example: We have a submit hol search event that passes with park name and park region event properties, I’d like to be able to remove those properties in our tracking plan only for this event and not others.

Find more posts tagged with

Active

Status: Active

Comments

Esther Trapadoux

dangrainger Hi Dan! Hope you’re doing well! 😊 If the property is already ingested on the event, then we do not allow for the removal of the property from the event since data is historical and immutable. However, if you have the property as planned and it has not yet been ingested, then you can go to the event with the property, remove it, and save the changes. I would also be sure your code is not sending in that property for the event.

Has the property already been ingested? If so, there might be some things our team can suggest to mitigate the impact.

dangrainger

Thanks Esther Trapadoux - yes, it’s already ingested. So if we’re can’t “unattach” the property from the event in our schema, I’m guessing the best solution is to just hide it in the UI instead? I know that means it’ll be hidden for all historic data too, not just forward looking, but that shouldn’t be a problem.

Esther Trapadoux

Hey dangrainger sorry about the long wait 😓 You’re right, best option is to hide it.

Here’s a bit more background:

When an event comes in with an unexpected event property and you don't want that property, there's currently no way to get rid of it.
You can leave it as unexpected. It'll continue to show in Analytics.
You can also Add it to plan so that you can hide it in Analytics. Note that there's no way to make it unexpected again today.
The only current option to get rid of the property entirely is to delete it in the property library, which removes it from all events.

So there would be no way to delete the property at the event level when ingested and usually the easiest way is to add the property and hide it. We do plan to support event-level property deletion in the future. You might also want to be sure your code is not sending in that property for the event.

Johnny Andersen

I have a similar issue, and I assume that if I choose to make the event property“hidden”, then it will also be hidden on other events?

Esther Trapadoux

Johnny Andersen welcome! That’s right, changing the visibility to hidden will hide it from the charts. It will still show up in the raw data when you look at the user lookup and past events with that property.

Varun Goyal

Hey Esther Trapadoux thank you for the responses and this thread. it was quite helpful.

Are there any plans in the future to be able to remove old properties from the events?

Varun Goyal

Esther Trapadoux A quick solution could be to add a new filter to the Properties drop down in the Events data to `only show visible` properties?

Varun Goyal

Managing Properties within events are super hard without this.

Quick Links

Give your vote

Linking AI Feedback to Specific Surveys in Amplitude
It would be really helpful if Amplitude showed which survey a piece of feedback belongs to. Right now, it’s hard to tell where comments originate when multiple surveys are active. As a bonus, it would also be great if the feedback text matched the UI language (currently, mine shows in German).
playback video in 9:16 in guides on phones
It would be great to have the option of playing back video (and having the video preview) in a 9:16 (vertical) orientation so that an end user of a video in a guide didn't have to full-screen the video in order to have it play in the correct orientation. It would also be great to have support for Wistia as more and more…
Grouping reordering
Hi, I’d like to request a feature: it would be really helpful to have the ability to shuffle or reorder properties within an event, especially when grouping. Right now, adjusting the order of grouped outputs is quite cumbersome.
Fix the search when filtering
When changing a property value, because we often have complex and long values, we paste the exact value in the search bar. However the matching value will appear at the very top but all other values will remain, which makes the search complex and we lose a few seconds each time Here is a loom to show my point Thanks !!

View All