Subscribe
Sign in
Avo has been a game changer for us, alerting us when we have data issues in dev or staging and virtually eliminating data quality issues from making it into production. Data quality has gone from a problem that keeps me up at night to something I barely have to think about!
Avo has chosen their niche and they do it really, really well. We've been using Avo for the better part of a year: it's easy, intuitive, and above all, effective. It has saved our Data team hours of work in developing and maintaining a tracking plan. And it has saved our Engineering team hours of work, thanks to Avo's codegen feature.
Such an amazing team and product - 10/10 would recommend!
An inspector like this is exactly what I've been looking for and a miracle for any marketing teams looking to step up their data game but already putting a lot of pressure on at-capacity engineering teams.
Avo is the best way to manage your analytics and make sure they are right. I love that there's only a single line of code for all of our analytics tools and that we can robustly test the data we're sending to these tools in our development environments. It's great to know that we're always shipping good analytics code. This means we can make less mistakes, measure faster and improve our product faster.
I know the team personally, they are super smart and hard working and make everything work for you in terms of analytics! Go AVO!
I don't have a ton of experience with Avo yet, but I'm intimately familiar with the problem it is solving, and I've seen enough (through a demo and through my own exploratory use) to know that this is the solution I always wanted but never knew I wanted. Instead I was stuck with spreadsheets describing the analytics setup that were well intentioned but quickly got stale and were lacking the ability to communicate with the rest of the team, let alone verify that everything is OK between the code and the analytics design.
The main thing I worry is that e.g. the android team and iOS team may interpret an even as happening at different times, so it's unclear if the events *mean* the same thing across implementations. If Avo could figure that part out, it'd be a killer weapon :D
Avo