Recommendations to others considering Avo:
If you do any event tracking (i.e. you have Segment, Rudderstack, Mixpanel, Amplitude etc) you should be using Avo. If you want to build a data culture at your business, you need to remove the friction in tracking high quality and consistent events from that growth loop. Avo does exactly that. Review collected by and hosted on G2.com.
What problems is Avo solving and how is that benefiting you?
Avo solves a whole ball of fuzzy data quality problems in one.
- It's allowed us to scale governance of event taxonomy from single gatekeepers to a more decentralised model. Prior to Avo only 1-2 analysts could make changes to the taxonomy and without branching, we could only manage a single change at a time. With Avo we have all our teams creating branches of changes that can be QA'd by the team.
- It also solves problems on the engineering side. The Avo developer tools have meant a drastic reduction in how long it takes our engineers to implement tracking and a huge increase in data quality.
Because of Avo we now have a culture of tracking consistent events everywhere that we can rely on. Review collected by and hosted on G2.com.