A tracking plan made for collaboration

Graduate your tracking plan from spreadsheets to source-controlled schema management. Collaborate on designing quality data, faster, with real-time feedback based on your team’s standards.

Team up on data design

Data design has never been easier, faster, or more collaborative.

No need to start from scratch

Auto populate your tracking plan from live data, or get started by importing a CSV file.

Safely evolve your data design

Collaborate on data design within the safety of branched workflows with peer reviews.

A single source of truth for your event data

Sync your single source of truth across codebases and schema registries.

Consistent events, faster

Design complete and consistent data structures faster by re-using events across platforms and properties across events. Bundle related properties to add them all to your events with one click.

Get real-time feedback when creating new events and properties to prevent duplicates or inconsistent casing.

Global Namespace docs

Collaboration made easy

Branched workflows and automatic consistency audits make it possible for anyone to contribute to data design.

Align with your team before implementation, with in-context comments and approval workflows.

Branched Workflow docs

Sync with your downstream tools

Your tracking plan doesn’t just live in Avo. It integrates with your downstream tools, so you can ensure high quality, highly expected data in your data warehouse and analytics solutions.

Make changes to your event structures once and see them reflected across products, platforms, codepaths and schema registries.

Publishing docs

Common questions

Is Avo a Customer Data Platform (CDP)?

Avo does not collect and route your data to other destinations so, no, Avo is not a CDP. Avo makes sure that the tracking calls you make to your CDP or analytics tool are according to spec so that you can make product decisions based on quality data.

What is a tracking plan?

A tracking plan is a central document that everyone in your organisation can refer to for data management best practices. It standardises the events and properties you track, determines where within the code your analytics should be placed, and outlines the reason why each event is being tracked in the first place. I the past, teams have most often managed their tracking plans in Spreadsheets. However, spreadsheets don’t scale and that’s where Avo helps.

Read more in our What is a tracking plan and why do you need one blogpost.

How do branches work?

In Avo there is the main tracking plan that acts as a source of truth for your production data structures. You can branch out from the tracking plan, creating a draft state of the main one, to make changes without affecting others. Once the suggested changes have been reviewed, approved and implemented, you merge the branch, updating the main tracking plan to include your changes. Read more about branches in our docs.

If you have an uncommon question, feel free to get in touch with our team.

Contact us