“The biggest thing we were looking for was flexibility—the ability to collect data from any interaction on any media property. We didn’t want to conform to what other analytics platforms thought was a good metric. We needed control over how we were collecting and analyzing our data.”

“Keen helps us define metrics and prioritize. It helps us see where our customers are not succeeding. When we build features with the goal of making a user’s life easier, Keen helps us understand if we’ve succeeded.”

"Our team writes one line of code, and it just works, and we can keep focused on what we want to work on."

"With Keen, we have the flexibility to query just the data we need, all in one place."

"Our goal from day one has been to build a community around open source and measure it, so we can better contribute to the sector. But what we discovered pretty quickly - and what many other community managers, developer evangelists, and advocates agreed with - is that measurement of a …

"Without Keen, we’d have to build our own analytics infrastructure to get the insights we need. Keen was super easy to implement and helped us boost views of our highest-impact content by 133%."

"I’d say customer behavior is our favorite use case, and we’re going to keep it around forever. I load our custom dashboard probably 100 times a day."

"Keen allows us to have analytics, but we don’t have to worry about it, and we didn’t have to reinvent the wheel to get it."

"With Keen IO, I don't even have to think about how it works – I just know that it does work, and it will work."

"Keen allows us to construct our data model in a way that privileges the metrics we care about. With other programs, we would have constant constraints that would greatly limit what we were hoping to achieve. For me I think that’s one of the biggest reasons we ended up going …

“The implementation was pretty straightforward. Keen’s Ruby gem library made accessing end points a lot easier, and we didn’t have to write them, just access. We ended up writing a wrapper around it to wrap the calls, because we make them in a few places. When we first started using …

"[Keen] sped up development time for a lot of “nice to have” features. [They] made building and conceptualizing new features super seamless."

“Initially, we just wanted to be able to shoot some events and log in and start slicing the data. On top of that, I needed something flexible enough that could evolve quickly alongside our product.”

"Keen has changed the way we manage our event data and create analytics. We now have a single platform to handle the entire data lifecycle from streaming millions of events to custom dashboard creation."

"Thanks to Keen, Content Science has been able to develop ContentWRX so that it meets the unique needs of end-users."