For Snowplow it often makes sense to have one single event that covers both a click and a view. Take an event "Internal Ad Engagement" as an example. A property e.g. "action" would then differentiate between "clicked" and "viewed". All other properties are shared between click and view. This makes data modeling a lot easier as there will be a single event schema added to the database.

The self-desc event schema would be called like so:

To make life easier for developers on the other hand and have more concise naming, in Avo it would be better to define two separate events: "Internal Ad Viewed" and "Internal Ad Clicked" where "action" is then pinned to either "clicked" or "viewed".

This would then generate two Snowplow self-describing event schemas:

It would be great to have a feature, that allows me to create the two events, but to define that both are part of the .

The properties are identical for both and I'm doing this manually already. However this is very error prone as I need to copy paste the existing schema from the "Publishing" tab for either internal_ad_viewed or internal_ad_clicked and replace it with my own internal_ad_engagement.