Our company is using Heap, and I’ve just got started sending some events from the product to heap. It’s a drawing app, so things like “element_add”, “element_delete”, “choose_tool”, etc.
But when I come into heap I cannot graph these without first “defining” the event? Is that right? That seems rather cumbersome.
Is there any way to graph things that are “tracked” via client-side heap analytics without having to go in and manually “define” everything? What is the thinking behind this model, when basically every other analytics platform doesn’t require this manual step?
Best answer by danielle
View original