Best practice for creating event properties

Hey @Sachin 

Generally, PII such as email id of the user isn’t the best piece of data to capture in Amplitude Analytics due to GDPR concerns. But I do understand the need for that, especially if you are using Amplitude as your primary CDP.

Is there a specific use case here for email id to be an event property?

Ideally, email id can be captured as a custom user property instead of an event property. This enables you to set the email id only once per user and use this for querying events.

I haven’t used the Data feature that extensively yet, but here’s my interpretation on how to evaluate the Data UI for event properties on a different post

• Multiple instances of event properties

Afaik, after your tracking plan is approved/merged, the UI should show only one EmailId property under Event Properties Tab and the events sending this property should be listed under EVENTS column for the EmailId property.

From what I have observed, the multiple instances issue occurs when you are working on a test branch and have unsaved changes irrespective of how the property was created and assigned.

The most likely behavior here could be -  once the tracking plan gets approved, every common property name should be reflecting in the UI only once against the events that are sending them ( like the plain ol’ Govern UI )

Hope this helps.