Today it’s not possible to define an event based on both a custom event and a click with a filter.
This is badly needed because many times we have growing event definitions that change over time. Usually it starts with us looking at a Click event with some filter based on an ID. Then as we decide to make this event more durable, we add a custom event for it.
To avoid losing history on the event, we want to then grow the original event definition to be:
- Custom Event1 with Filter X, OR
- Click on #someID with FilterY
You cannot do this today and have to create one event for the first custom event, then another event for the second, then a third event that is a combo of both. This bloats the number of events we must have defined in our heap project.
Best answer by Jonas-Heap
View original