Has anyone combined structured and unstructured events in product analytics use cases in the same project?
These 2 event types are quite different.
- easy to add new events
- simple structure
easy to consume by analysts (event category and name already in
se_property, se_label, se_valuewill mean different things in different events
- can’t provide complex structure (only via custom contexts)
- any complex event structure is possible
- harder to add new events by developers (new event --> new schema)
needs additional data modeling to unwrap
unstruct_eventinto a fat table
I see at least 2 obvious solutions, but wanted to know if anyone was in the same situation?
Option 1. Use structured events with custom contexts.
Option 2. Use both types, and do additional data modeling on top of
atomic table to prepare events for downstream consumption (e.g. populate columns
final_event_category based on the types of events, as unstructured use schema URLs for event_name, and structured always have