[writimov]

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 the case that the sales funnel changes and a new page is added, do I need to remember to update Avo with the change?

[cosmie]

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 (data structure, naming scheme, etc) and ensuring that everywhere "TrackFunnelStep" event ends up, it's used consistently. But Avo wouldn't stop you from forgetting to add the event to a step in the first place.

[1] https://www.observepoint.com/

[stefaniabje]

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.

[stefaniabje]

Thank you for surfacing the need for a better demo and examples.

> I'm currently managing a team using Google Analytics, Facebook Pixel and Hotjar.

Avo is optimized for event based analytics, such as when people send events with metadata into Amplitude, Mixpanel, Segment or into custom pipelines. Are you sending custom events into the platforms you mentioned, and sending metadata along with the events?

> 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.

You can use Avo to define the structure of the events that you want to send at each step in that flow. From those definitions, developers can generate code that validates that the event structures are correct.

What I mean by event structures is for example event names, which properties should be required on those events, what those properties should be named, and which type their values should be.

An example event could be:

event name: "Checkout Completed"

properties and their values: {"Number of Items": 2, "Amount": 100.00, "Currency": "USD"}

> In the case that the sales funnel changes and a new page is added, do I need to remember to update Avo with the change?

If your data should change along with the sales funnel change, then you should update Avo and then your code.