Getting started with Avo
Your Avo Workspace
Data Design
Implementation
Explore the Tracking Plan
HelpGetting started with Avo
The Avo workflows are layered. The 3 steps to adopt Avo can be adopted as a whole or in part – depending on your use case. Each layer of the workflow provides value and each of them requires different amount of engineering contribution.
For example, if you already have a framework for analytics implementation and implementation data bugs are not a problem for you, you can stay at the second adoption step.
Step 1. Tracking plan management – no engineering required
Use Avo instead of your spreadsheet to manage and discuss your tracking plan changes. Avo is designed for analytics, so it's way better than the spreadsheet for managing your tracking plan.
This adoption step does not require any developer input, so you can adopt it in the data design team without getting a developer buy-in.
Creating tracking plan in Avo
If you already have a tracking plan you can import it to Avo, or you can create your plan in Avo from scratch. In any case you'll be able to fine tune it and add new events for every feature release in Avo.
Branched workflows
One of the core features for effective data design in Avo is branched workflow. It allows you to see the changes for a single feature and provides implementation instructions that you can share with the developers working on the analytics implementation
Publish tracking plan from Avo to other analytics tools
You can set up your tracking plan to be automatically published to Segment Protocols, Amplitude and Mixpanel every time a branch is merged. We also provide a webhook for advanced automation.
Step 2. Tracking plan validation – one time SDK install
Add a lightweight SDK to your code to learn how actual implementation compares with the defined tracking plan. Get instant feedback on what tracking is implemented when working on new features with the Implementation status in your Avo workspace soon. Observe your tracking calls on device in real time with the Avo Debuggers.
This stage requires one time setup in each of your applications. The setup is simple and shouldn't take more than 30 minutes. It is not necessary to set up all platforms at once, you can start with a single platform. Once it's done the data design team will get the full power of Avo.
Adoption step 1 is required, but steps 2 and 3 are interchangable, i.e. you can go directly to step 3 without going through step 2 if your platform does not yet have the Inspector SDK and start using the Inspector once it's available.
Step 3. Tracking plan implementation workflow for your team
Avo generates human readable, type-safe, tracking code called Avo Functions, that sends the data exactly as planned. No more data bugs or cross-platform discrepancies in your analytics tracking!
This step requires developers to adopt Avo into their tracking implementation workflow.
It's not necessary to swap all your tracking with Avo functions, in fact we recommend starting by only using Avo functions for new events.
It's not necessary to adopt Avo functions on all platforms at It's not necessary to adopt Avo functions on all platforms at once, you can start with a single platform.
Avo functions reference
Explore your Avo workspace
Comprehensive data design and implementation guides
