Avo Inspector SDK reference

2 minute read

Avo Inspector analyzes the analytics events sent from your app, without collecting the actual data (not yet another tool to add to your privacy policy). Based on that analysis Avo automatically builds a single source of truth tracking plan, covering all your products and platforms, giving you a complete overview of which is tracking what, and which is not.

The Avo Inspector SDK is designed to be small and easy to include in any project.

Table of Contents

Platform documentation

Usage overview

Find the overview in the Inspector section in the Avo 101 for Developers guide.


In order to ensure our SDK doesn't have a large impact on performance or battery life it supports event schemas batching. Default values are 30 schemas per batch and smaller batches are sent if more than 30 seconds pass between uploads. You can change the values using AvoInspector.setBatchSize(newBatchSize: Int) and AvoInspector.setBatchFlustSeconds(newBatchFlushSeconds: Int) class methods to fine tune the library performance.

When integrating the Avo Inspector for the first time and sending the first event it might not appear right away because of batching. Be sure to trigger a few events within a few seconds to make the batch go out to Avo servers. It will be reflected in the logs.

Easy setup with Segment SDK on Android and iOS

If you are using Segment Analytics for tracking integrating Avo Inspector SDK is even easier.

We provide a code snippet to be used as middleware component that you supply to Segment during initialization. That will allow Avo to analyze schemas of all event tracked by Segment.

Check platform docs for more information and actual code snippets.