How Heap's 5-line MVP evolved into a 30,000 TPS beast
codeinsider.us
codeinsider.us
That said, I'd love to see Heap pull in the rest of the web analytics picture. Event data is interesting, and they seem to have a decent solution for the issue of setting up a massive amount of event tracking (and losing all the data you haven't set events for yet). However event data in a silo without the context of things like referral URLs, search query data, campaign metrics, etc. are critical for gaining the full picture.
Perhaps I didn't tinker with the demo enough, but I didn't see those pieces of the puzzle present. For any online marketer serious about analytics, you need the complete picture under one roof.
That said, this is a great step forward in a space where this pain point around setting up event tracking has been largely unsolved for some time. I wouldn't be sad at all to see them acquired by someone like MixPanel, KissMetrics, or Google.
Would love to know if there's other important context we're missing.
I'm playing around with the demo in our test environment right now and really love your Event Visualizer tool. I need to play a bit more, but I'm hoping that your ability to check/uncheck the components that define the event will let us work around issues of dynamic selectors generated by YUI which was our team's concern for why Heap might not work with our setup.
EDIT:
Looks like YUI is still a major issue. If you're curious, you can look up my HN username in your email list to find my account and see what I'm talking about.
> Oh god no.
Pretty damning condemnation of MongoDB, no?
It seems like Mongo's addressed some of these concerns since we started building Heap.
They also outgrew PostgreSQL, and gave up on Redshift, is that a condemnation of them as well?
var DOMEvents = ['click', 'submit', 'change'];
for (var i = 0; i < DOMEvents.length; i++) {
window.addEventListener(DOMEvents[i], function(e){
$.post('/collector', {type: e.type, target_id: e.target.id, target_class: e.target.className});
});
}