Why are there multiple instances of same event property with same data type created?? This is making me confused. Am I missing something?
Solved
Multiple instances of event properties
Best answer by Saish Redkar
Hey
I haven’t used Data (Beta) yet that extensively. But from whatever I have explored so far, here’s my best understanding for the issue
- the first instance in the list for tax property could be the one that is coming along with your instrumented and approved events ( CheckOutPageViewed,etc) in your schema
- the second instance for the property might have been added via the “Add Event Property” action in the UI. That’s why there aren’t any events showing up against it under the EVENTS column unlike the first instance. If you click on this one, the right navbar will probably show Events(0)
- the third instance is the property which newly came in with your BookSalonPassClicked event, which isn’t approved and merged yet. Once this is done. I assume this event will show against the first instance.
Hope this helps.
Satya Reddy
1 person likes this
+10Hey
I haven’t used Data (Beta) yet that extensively. But from whatever I have explored so far, here’s my best understanding for the issue
- the first instance in the list for tax property could be the one that is coming along with your instrumented and approved events ( CheckOutPageViewed,etc) in your schema
- the second instance for the property might have been added via the “Add Event Property” action in the UI. That’s why there aren’t any events showing up against it under the EVENTS column unlike the first instance. If you click on this one, the right navbar will probably show Events(0)
- the third instance is the property which newly came in with your BookSalonPassClicked event, which isn’t approved and merged yet. Once this is done. I assume this event will show against the first instance.
Hope this helps.
Saish | Connect with me on topmate.io/saish_redkar for supercharging your Amplitude skills
+8Hi!
Thanks again Saish! I also wanted to mention this multiple instances of the same property could be seen since different people could be making edits to their branches. This notification is to show that there is more than one property with the same name so when you go to approve the properties only the right one is approved. See here for some details let me know if you have questions.
+8I wanted to mention one more thing! Instances can also be caused when the property is ingested with an event that has not been planned
Here is a workflow to avoid many instances:
- Create event property once
- Plan multiple events
- Add properties by clicking on Add Property within the event
- Chose one of the already created properties
Reply
Rich Text Editor, editor1
Editor toolbars
Press ALT 0 for help
Welcome to the Amplitude Community!
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're a current customer, select the domain you use to sign in with Amplitude.
analytics.amplitude.com analytics.eu.amplitude.comor
Welcome to the Amplitude Community!
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.
If you're a current customer, select the domain you use to sign in with Amplitude.
analytics.amplitude.com analytics.eu.amplitude.comor
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.