Beekeeper provides companies with frontline workers an integrated platform for communication, knowledge sharing and more, mainly through their mobile apps but also through web apps and micro-sites. With multiple front-ends and teams, Beekeeper needs an integrated analytics solution and process to succeed.
At Beekeeper there are multiple teams working across their iOS, Android and web apps and they are all responsible for designing and implementing tracking for their respective features and apps. Beekeeper was relying on a Confluence page with long tables listing events, their definitions and status.
There was no clear owner of event tracking and the Confluence page was never kept up to date. New features would go live regularly without tracking and if features included tracking, it was often inconsistent across platforms and never tested.
“In many cases we just didn't have tracking at all, or we kind of defined and added it, but inconsistently across platforms and then didn’t QA it. So a year later we’d realize, hey, this event has never been sent from the iOS app.”
Furthermore, there was a lot of confusion around the Confluence page and it was hard for product managers to tell what events were live in the product and what they meant. This resulted in unnecessary back and forth and engineers having to waste time manually weeding through the code, only for that information to get lost again.
As a result, product and BI teams did not trust their data and product managers spent very little time in Mixpanel exploring the performance of new features or understanding the core metrics they were responsible for. They simply had no confidence in what they were seeing, which greatly limited the use of their data at Beekeeper.
While exploring their options to improve data quality and the process around defining, implementing and evolving their event tracking, Beekeeper luckily found Iteratively. The team started by leveraging Iteratively for a new feature to understand the process and the impact of the tool. The feature quickly became the most tracked feature and its performance was easy to explore and understand in Mixpanel. It turned out to be a huge success and slowly Beekeeper rolled out Iteratively across the company.
“Now the product team is excited to explore new features in Mixpanel and we’ve seen a big increase in usage. It’s hard to rebuild trust once it’s been lost, but Iteratively has helped us so much.”
Head of BI
The product team now feels empowered to own analytics tracking and all new features go live with consistent and accurate tracking that is fully tested. While trust is hard to win back, product managers are rebuilding confidence in their data by taking ownership of the process and relying on Iteratively to ensure the accuracy and consistency of their tracking.
Iteratively has become the source of truth for all Beekeeper’s analytics tracking. The always up to date documentation has been a major driver of success and the old Confluence page now redirects to Iteratively. The process and collaboration around analytics tracking has been greatly improved too. The product teams are leveraging Iteratively’s branching feature so each team can work on changes and updates in privacy, without disrupting others.
Beekeeper has seen a big cultural shift within the company after adopting Iteratively. New features always go out with accurate tracking, product managers are leveraging analytics significantly more and confidence in the data is coming back. Product managers are excitedly exploring the performance of new features in Mixpanel, which they rarely did before.
“Iteratively was a big cultural push for us and empowered us to get our tracking in order and finally improve the quality of our data.”
Head of BI
For the BI and engineering teams it has meant a huge increase in productivity. With product managers taking ownership of tracking and having a user-friendly interface to do so, there’s little back and forth and no confusion around tracking or event definitions. It has resulted in many fewer Jira tickets for the technical teams and their resources are now more effectively used. Collaboration has improved too - now product managers ask for suggestions to improve their event tracking, not why, where or what it is.