Publish your tracking plan into Amplitude, Mixpanel, Segment or with a Webhook
Sölvi Logason

Sölvi Logason

November 24, 2020

Publish your tracking plan into Amplitude, Mixpanel, Segment or with a Webhook

We’re excited to announce the following Publishing destinations are now available in Avo:

What is Publishing? Auto-Publishing? 🤔

Publishing integrations are a special type of integration in Avo where we send your tracking plan and accompanying metadata (think event and property descriptions) to the other tools in your analytics workflow. This means that you only have to define your schema once, and that data can live on in any tool that is used by your team. All team members have the knowledge and context to do their best work with your analytics tracking data.

The feature we’re most excited about, however, is auto-publishing to all of these destinations. You can now configure these integrations so that each time a new branch is merged, your new and updated tracking plan is automatically sent to your downstream tools of choice! We’re taking the guesswork out of event metadata. 

With auto-publishing, you can rest assured that every team member has the insights needed for analysis and activation, right where they need them.

Use Cases

Tracking plans can't live in isolation. Once a tracking plan has been defined in Avo it needs to be utilized in multiple places, not only to generate type safe tracking code, but also to...

  • feed the rich context of the tracking plan (think event descriptions, property types etc) into analytics platforms. Example: I want to see the Avo description when hovering over an event in Amplitude.
  • sync with data from other product or feature teams. Example: a legacy product flow is tagged outside of Avo, but has relevant data for your new well-defined and -documented feature. 

Avo Webhooks unlock even more possibilities, allowing you to configure connections to virtually any tool in your existing analytics workflows.

  • update ingestion time validation tooling that blocks things that are not defined in the tracking plan from entering our datastore
  • build or update SQL tables based on the latest tracking plan, to receive and store the data

Basically, the limit does not exist. 🚀

Easy Implementation

Setting up a Publishing destination with Avo is an easy two-step process: configure and publish.


In the Avo UI, go to “Tracking Plan” > “Publish” in the left hand sidebar. Select your integration and enter your account credentials from your Publishing partner. Depending on the particular partner, this might be an API key or account credentials.

For more information, check out our docs


Next, simply click the “Publish” button to send your tracking plan out. 

On publish, Avo will merge your Avo tracking plan with any existing events in your partner tool. Any changes made to an event in your partner tool between Avo publishes will be overridden on next Avo publish. Avo will not impact any events or properties that are only defined in your partner tool, or events that have not been added to the partner integration in Avo.

Bonus: Automate it!

When Auto Publishing is enabled all changes made on a branch will be published to the integration when the branch is merged.

This is practically a super-power when working with cross-functional and distributed teams. It means your tracking plan taxonomy is always up to date, no matter what tool you or your colleagues are leveraging.

Publish Your Avo Tracking Plan 

Publishing helps you seamlessly create a single source of data truth and foster better collaboration across teams in your product organization. If you need help along the way, know Avo is ready to partner with you on your journey to good analytics governance.

Get Started Today >