Avo

Last updated:

|Edit this page

Avo is a data governance platform which helps teams plan, implement and verify analytics at any scale. The Avo Inspector sends event schema - but not events themselves - to Avo. This enables you to, for example, avoid losing data or events due to naming issues in your analytics.

You can read more about Avo in the official announcement.

Requirements

Using this requires either PostHog Cloud with the data pipeline add-on, or a self-hosted PostHog instance running version 1.30.0 or later.

Self-hosting and not running 1.30.0? Find out how to update your self-hosted PostHog deployment.

You'll also need to have an Avo account, obviously.

Installation

First, you need to set PostHog as a data source in Avo. We recommend checking Avo's documentation for setting PostHog as a source in Avo.

Once PostHog is set as a source in Avo, simply install and enable the destination in your PostHog instance by heading to the Data pipelines section. You'll need to enter your Avo API key to complete the setup.

FAQ

Where can I find out more?

Avo maintains robust documentation about integrating PostHog and Avo.

Who maintains this?

This is maintained by the community. If you have issues with it not functioning as intended, please let us know!

What if I have feedback on this destination?

We love feature requests and feedback. Please tell us what you think..

What if my question isn't answered above?

We love answering questions. Ask us anything via our community forum.

Questions?

Was this page useful?

Next article

Customer.io

Send event data from PostHog into Customer.io. User emails will also be sent if available and customers will be created in Customer.io. Note: We currently have an open issue with our customer.io plugin which is impacting some functionality. You'll also need access to the relevant Customer.io account. Installation In PostHog, click the " Data pipeline " tab in the left sidebar. Search for 'Customer.io' and select the destination, press Install. Add your Customer.io site ID and token at the…

Read next article