We find Combo Events very useful in managing our heap instance. For example, we have one Heap Event called “HVA” (High Value Action) that is a combo event of all the high value actions we track that users do in our product. It makes subsequent reporting and segment definition so much simpler.
However, many times we have other combo events we want to define that are SUPERSETS of another combo events. For example:
ComboEventA:
- Event1, OR
- Event2, OR
- Event3
Assume now I have EventB (another Combo event) that is EventA plus 2 other events. Logically the definition is:
ComboEventB:
- ComboEventA, OR
- Event4, OR
- Event5
Currently, Heap does not allow nested combo events. This forces us to define ComboEventB as this:
ComboEventB:
- Event1, OR
- Event2, OR
- Event3, OR
- Event4, OR
- Event5
This is really bad because now I have to maintain definition of ComboEventA in 2 places. Even worse if there are multiple instances of definitions like this.
In my proposal where combo events are nestable, then when you change ComboEventA, it applies everywhere it is referenced.
Best answer by Holly Goodliffe
View original