Cool idea, seems like the next logical (or rather the first) step in the current analytics pipeline.
This being said, your doc could do with some fixing / editing :
> https://www.avo.app/docs/help/faq
Bad copy pasting of "Does Avo send my events to its servers?" instead of "Why does Avo want me to input my analytics tool API keys?"
Cool idea, seems like the next logical (or rather the first) step in the current analytics pipeline. This being said, your doc could do with some fixing / editing : > https://www.avo.app/docs/help/faq Bad copy pasting of "Does Avo send my events to its servers?" instead of "Why does Avo want me to input my analytics tool API keys?" > https://www.avo.app/docs/reference/languages Those are documented in detail in TBD.…
It's great that you think so.
Thank you for the Docs pointers! Good spots. We will make sure to fix these.
I'm having difficulty understanding how to use this. Is there a demo / example to view? I'm currently managing a team using Google Analytics, Facebook Pixel and Hotjar. How can I benefit from Avo? From what I understand, I can use Avo to setup flows that I want to watch (like a sales conversion funnel) and make sure that the analytics tags are properly implemented across all pages of the funnel. Is that correct? In t…
Something like ObservePoint[1] would be more appropriate for that use case. Avo seems like it's designed to deal with consistency issues, rather than coverage issues. For example, say you have three different multistep sales funnels. You send a custom event "TrackFunnelStep" to both GA and Facebook at each step of the funnel. Where Avo would come in would be with defining precisely what that custom event should be (d…
That's correct. Avo today is particularly designed for consistency issues. Coverage issues are top of our mind though, and we have some internal tools for that that we're excited to share soon.
Thanks for taking the time to clarify.