Kermit is an open-source Javascript framework to solve your web analytics implementation on single-page applications, and all other types of websites, help you catch the developers modifying your analytics code before it goes live and even simplify tagging the consent for cookies.
Imagine having a constellation of websites and microsites some using a traditional architecture where each web page requires full page loads and others built like a single page application where you only have one full-page load followed by partial screen updates. Sometimes the URL will change but not always. You have many single page applications, built using a variety of frameworks such as AngularJS or EmberJS or even just CSS hide and show tricks. You have no consistency to help you track page views.
Last week one of your stakeholders informed you that the top pages report has gone blank. Your developers have released a code change on the same day, and you realise that they have removed some of your analytics code. Just how much they removed you do not know yet. This has happened before, and nobody seems to hold the developers accountable but you instead. Why, oh why can't they include additional checks in their test suites to ensure that they stop removing analytics code by accident?
You have one-time banners on your websites to require consent for your cookies. Several links and page elements are more important than others. When your visitors interact with the former, the interaction is interpreted as an implicit form of consent. Explicit or implicit consent, the banner goes away until your visitor clears their cookies in both cases. Could there be an easier way to identify these important page elements and all their analytics properties by simply inspecting the element in the browser?
