Over time, we improve the way we utilize heap by improving our event definitions. Or alternatively, our product changes and we change our heap event definitions to match the changes.
one thing we constantly struggle with is tracking these changes.
example:
we track completion of a workflow without a custom event, and instead just look at visits to a page url. This works but is better with a custom event because we realize that workflow is going to be super important. So after 3 months, we then implement a custom event. There’s no easy way to make a simple continuous view of this because combo events work by recognizing both the pageview and the custom event so will double count.
what would be super powerful is two things:
- Combo events to not double count in the above example. Since the custom event is happening with the page view, it should be counted once.
- combo events should support some notion of configuring date ranges for events. Eg. Event A valid until date X, and after Date X event B is valid.
this in particular is complex I admit but super super powerful. We’d then have continuous data in one combo event without any complexity of juggling multiple events and knowing when to query separately.
Best answer by Holly Goodliffe
View original
