Is not a bad idea for building the event list, but it doesn't solve the problem of documenting when or by what the event is triggered, something that a product owner or a data scientist that don't know the code might want to know to do some analysis (Sorry, I forgot to mention it needed to be for non developers)
well that is what the normal analytics functionality of the system was, basically on meaningful events you would make a call to analytics function and pass it an object with the properties you wanted to analyze, it would add some global properties and send it off.
There were of course various levels of abstraction, but sure I would know when an event happened because a user scrolled by a widget on an external site, on the main domain, when they clicked on the widget, liked it etc. all the normal things you would want to capture if you are measuring widget interactions across sites.
on edit:
So in your first scenario - if a non developer wanted to look over all events they might see that there were events named "hotspot seen", "hotspot hovered", "hotspot clicked" and so forth.
In those ones actually there was the widget id that hotspots where in and of course the original interaction id so you could draw a graph of how many users progressed from hotspot seen to product liked and so forth. But at some point a non developer is going to probably have to ask a developer or elasticsearch expert - I need this data out of the system and summed in this way.
ctrlio | Senior Backend JavaScript Engineer | Moorgate, London UK | £60-65k + bens
ctrlio: Join our small, close-knit start-up, building SaaS software for consumers and businesses. Our mission is to empower consumers to get better/tailored offers from responsive merchants. We enable people to publish their buying intentions that then allows merchants enriched with our smart analytics to compete and bid for business directly. We are growing rapidly and have the backing of a very impressive team.
Required: Senior Engineer with 6 years+ solid experience in client side JavaScript, server-side JavaScript (node.js) modern JS frameworks (React, Angular, and Express.js etc.). A strong communicator who can present ideas and get things done. Ideally from a relevant industry such as Ad tech, E commerce or Web Analytics. Web tech includes, (HTML, CSS, AJAX), HTTP, cookies, web security, cross-domain issues and databases, GIT.
ctrlio | Senior Backend JavaScript Engineer | Moorgate, London UK | £60-65k + bens
ctrlio: Join our small, close-knit start-up, building SaaS software for consumers and businesses. Our mission is to empower consumers to get better/tailored offers from responsive merchants. We enable people to publish their buying intentions that then allows merchants enriched with our smart analytics to compete and bid for business directly. We are growing rapidly and have the backing of a very impressive team.
Required: Senior Engineer with 6 years+ solid experience in client side JavaScript, server-side JavaScript (node.js) modern JS frameworks (React, Angular, and Express.js etc.). A strong communicator who can present ideas and get things done. Ideally from a relevant industry such as Ad tech, E commerce or Web Analytics. Web tech includes, (HTML, CSS, AJAX), HTTP, cookies, web security, cross-domain issues and databases, GIT.
