Ship and test features faster 🚀 Trusted by cross platform consumer products – where 1% conversion change matters.
⚙️Code generated tracking snippets.
👆Single source of truth tracking plan.
🌈No more outdated spreadsheets or broken analytics.
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.Pros:
10x better workflow than anything else for designing and managing analyticsCons:
I'm not seeing any downside so far
My company was one of the first Avo users. Avo helps product people like me define what to measure with analytics. Our workflow: - We start by hosting “purpose meetings” where we map out each feature on our roadmap. - We discuss the problem we are trying to solve, outline the reason for building this feature and clear metrics to see if we accomplish those things. - After this meeting, I jump in Avo, set up our goals, write up an all the relevant events on a new branch in Avo and post it as a task in Asana. - From there our Engineers grab the branch, have Avo automatically generate all the code they need, and then add these snippets to the relevant places in our codebase. Now I know that we are consistently tracking the right things. When we have these solid foundations, I can build dashboards that show metrics towards our objectives, and I'm confident that the data is correct. Avo has proven to be immensely valuable for us and created a very data-centric culture. 🚀 Would definitely recommend to a friend! 😄Pros:
Helps PMs define analytics Helps Eng implement analytics Helps everyone become data-drivenCons:
I would love a "global search" feature
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.Pros:
Avo does exactly what it says it will. If you run analytics, you should use this.Cons:
Looking forward to an easier onboarding process, but even yet, it's great
I'm the CTO and Co-founder of Teatime Games, one of the earliest customers of Avo. Their tool has helped us iterate on a robust event schema so that our data is reliable and we can make good product decisions based on our numbers. The Avo team is super responsive and has fixed issues and implemented new features within hours from us reporting them. I can't think of an alternative to Avo that isn't more expensive with fewer features.Pros:
Type safety removes a whole category of analytics bugs It's suddenly easy to refactor analytics Easier to QA that events have been sentCons:
Could add more features to detect if events are sent at the wrong time
I am a data scientist at Gangverk Software. Avo has made my life of implementing event tracking through Segment so much easier. By using Avo, we have have made our turnaround time of implementing new events a lot shorter while eliminating errors caused by typos and minor inconsistencies in naming of events and properties.Pros:
Overview of all events from all sources Seamless process from brainstorming to implementation Naming suggestions Type safety Great supportCons:
Documentation around the CLI and branching could be a bit deeper
Having been both a developer and a product manager using Avo it has made implementing and maintaining event schemas a lot easier. As a developer I can focus on finishing features instead of creating boilerplate code to integrate analytics into the project. It has also helped me to catch which events I'm not sending much earlier in the development cycle. As a product manager having one place with an up to date overview of all events for the product has been a game changer. It has also helped to eliminated any guessing about what each event does and when it should be sent. For both roles it has given me confidence that the team is shipping correct events at the correct time so we don't end up with a broken dataset.Pros:
Easy to setup in code Overview of all events and KPIS for a product in one place Takes away boring and error prone boilerplate codeCons:
Would be great to have an integration with github or a similar workflow to review changes to the schema.
I highly recommend. On our Android team, this has put everyone on the same page and we have been able to go from having a new analytics idea, planning it in Avo, and implementing it in production-ready code in only one hour several times this past month. For the past year I've been running a start-up with an Android app as the main product. I've been using Avo for about a month now and it's been a big success for us. Even with a small team, getting everyone on the same page with our events and tracked properties has been a mess, and whenever our CEO wanted to know which events we were tracking, the ad hoc spreadsheet we used was inevitably out of date and I had to check the code. That's okay, but I was certainly a bottleneck. Avo acts as a shared contract between the team in terms of the analytics roadmap, current implementation, and suggestions. On top of that, I love it as an engineer because I no longer have to manage a bunch of analytics libraries with my own solutions. Literally several times over the past month I have decided to track a new flow through the app, I write down the events in Avo with the team, and within an hour I use Avo's generated code to have a production-ready solution. It's not 100% fully-featured yet, but the Avo team is responsive and quickly building the tool around the new needs of the customers. 👍Pros:
Gets team on the same page Greatly speeds up analytics planning and implementation Simplifies engineer's lives The Avo team is responsiveCons:
not support for every analytics library yet, but it's coming and don't let this deter you
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 :DPros:
1. Unified view of all events that matter 2. No chance to mess up event data 3. *Less* work for all the correctness than the alternative!Cons:
Finding a way to unify semantics across implementations
I think it will really come in handy as we scale!Pros:
- iOS setup process not as straightforward - It took me a minute to understand the environments, i.e. there is only Dev and Production
I am a developer at Teatime Games and we are one of the first customers of Avo. In our previous company, we built tooling to help us send events correctly to our analytics providers, which took significant amount of time to get right, and we really wanted to be able to skip that work this time. As soon as Avo showed us what they could do for us, with code generation and type safety in events, we jumped on the opportunity. We had all of our features sending analytics events within a week. The speed they allowed us to move on with analytics was intense. Individuals in our team have worked with number of analytics providers in the past, and we all agreed we have never felt as productive while implementing analytics for our apps.Pros:
Type safe code generation. Supports multiple Analytics providers. Abstraction of what Analytics provider is being used in code.Cons:
We sometimes forget to merge Avo branches into master once implemented. Would love more tight integration with Github for this.
Before I started working at Teatime, one of Avo's first customers, I did not have a lot of experience implementing analytics but the experience I'd had as a developer was not good. I did not have a good vision of the data and I basically had no idea if the tracking that I implemented was consistent or if it was being sent at all.. I've been using Avo for almost a year now and I can fairly say that I can't imagine going back to not knowing my data. Avo gives me such confident as a developer and the feeling of knowing pretty surely that your implementation is correct is very satisfying ❤️Pros:
Typesafety 🙏 Simple and pretty UI. Makes developer + PM relationship easier. Avo team is very responsive.Cons:
Avo is still a fairly young company so it's still in development but I gotta give them, they're moving relatively fast 💨