I want to set up some event properties that are used by many events, however I have noticed that I cannot have it set as required for some events, and optional for others.
When I change an event property to optional, it changes it to optional for all events.
Is it possible to have some properties be optional for some events, and required for others?
Did I hit a bug or a feature?
Best answer by eddie.gaona
View original
+9
Hello
This is where instances would come into play for Amplitude Data. You can go into the event properties tab and plan a new event property with the same name. The screenshot below is how it will appear after these steps are completed. You can then use one of them as required for the appropriate events and the other as optional for the other events.
You can see that the first instance has some events associated to it, we can make that property required and it will only affect those events. The other instance is still in the planned state which means data has not been ingested for it, but you will need to add the events that would have this optional instance of the property.
thanks, I also eventually figured this out by trial and error, however it was not obvious at all. I think the UX should be improved here.
If you don't have an Amplitude account, you can create an Amplitude Starter account for free and enjoy direct access to the Community via SSO. Create an Amplitude account. You can also create a Guest account below!
If you don't have an Amplitude account, you can create an Amplitude Starter account for free and enjoy direct access to the Community via SSO. Create an Amplitude account. Want to sign up as a guest? Create a Community account.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
