Avo provides a number of tools that help you verify that the events you’ve implemented are correct according to how you’ve defined them in your Avo Tracking Plan.

Avo’s validation functionalities are built on top of two product offerings, Avo Inspector and Avo Functions.

🔒 While Avo offers powerful tools for data quality monitoring and observability, Avo never receives or processes any PII data about the customers of Avo customers. Avo never receives or processes your actual analytics events, only the schemas.

Validate implementation with Avo Inspector

For every source that has the Inspector installed, you can validate if the implementation is according to the tracking plan using the Inspector dashboard and/or the Inspector implementation in your tracking plan.

If you don’t have the Inspector installed yet, you can learn more about how to get started with the Inspector here:

Avo Inspector

Use Inspector to improve your tracking plan health

Read

Validate with the Inspector dashboard

The Inspector dashboard compares your tracking calls to the Tracking Plan on your current branch. If the Inspector finds any discrepancies between the tracking calls and the Tracking Plan, an issue is shown on the dashboard.

Here’s how you can validate tracking implementation for a particular branch using the Inspector dashboard:

Head to the Inspector dashboard in your workspace and switch to the branch you’d like to verify implementation for.
In the Inspector dashboard header, pick the environment you’d like to validate (Development, Staging, or Production). When validating tracking changes that haven’t been released to production yet, you pick development or staging.

Example: Inspector dashboard

In the Inspector dashboard you can see the health of all events that were sent from the selected environment during the select time period, and whether they fit the tracking plan or not. If any discrepancies were found, you can click into the event to learn more about the issue. Worth repeating here: Avo never receives or processes any of your actual analytics events, only the schemas. In other words, Avo never receives or process any PII data about the customers of Avo’s customers.

Example: Discrepancies in the event tracking

Validate with the Inspector implementation status

For every source the Inspector is installed on, you’ll find an implementation status in the Avo Tracking Plan. When looking at from which sources an event is sent from in your Tracking Plan you will notice green, yellow or red status indicator lights next to each source name. This is the implementation status.

You can hover over the source pill in the events table, or click into the event, to learn more about the implementation status.

Learn more about how to read the Inspector implementation status:

Inspector implementation status

Read

Validate implementation with Avo Functions

For all tracking implemented with Avo Functions, you can validate if the implementation is according to the tracking plan using four methods, each with its own purpose.

If you’re not using Avo Functions already, you can learn more about how to get started here:

Quickstart: Avo Functions

Start using Avo Functions

Read

Validate with type-safety and runtime validation

All tracking code implemented with Avo Functions is type-safe and has built in runtime validation. This gives the developer instant feedback on whether the tracking implementation is according to the tracking plan or not. Any type issues are surfaced by the code compiler, and runtime validations are surfaced via console logs and the Avo debugger.

Learn more about how validations in Avo Functions work here:

What's happening inside the Avo Functions

Learn about how validation in Avo Functions work

Read

Validate with the Avo In-app Debugger

The Avo In-app Debugger is an addition on top of Avo Functions that gives you better visibility into which events are being sent, which properties are attached, and whether any issues were detected or not.

Example: Web debugger example

The Avo debugger is available on Web, iOS, Android and React Native. Learn more about the Avo debugger here:

Visual debuggers

Learn about how Avo debugger works

Read

Validate with the Avo CLI

The Avo CLI has a command, ´avo status´, that will report on where the Avo Functions are being called from, and which events have not been implemented yet.

We recommend adding the ´avo status´ check to your CI pipeline, and configure it to throw an error if an event that is supposed to be sent with Avo Functions, is not found in the codebase.


Terminal
Copy
> avo status
info Currently on branch 'main'
└─ java android (musicplayerexample/src/main/java/sh/avo/Avo.java)
   ├─ appOpened
   │  └─ used in musicplayerexample/src/main/java/app/avo/musicplayerexample/MusicPlayerExampleApplication.kt: 1 time
   ├─ login
   │  └─ ✖ no usage found
   ├─ logout
   │  └─ ✖ no usage found
   ├─ pause
   │  └─ used in musicplayerexample/src/main/java/app/avo/musicplayerexample/ExampleMusicPlayerActivity.kt: 1 time
   ├─ play
   │  └─ used in musicplayerexample/src/main/java/app/avo/musicplayerexample/ExampleMusicPlayerActivity.kt: 3 times
   ├─ playNextTrack
   │  └─ used in musicplayerexample/src/main/java/app/avo/musicplayerexample/ExampleMusicPlayerActivity.kt: 1 time
   └─ playPreviousTrack
      └─ used in musicplayerexample/src/main/java/app/avo/musicplayerexample/ExampleMusicPlayerActivity.kt: 1 time
info 5 of 7 events seen in code
error 2 missing events
└─ java android (musicplayerexample/src/main/java/sh/avo/Avo.java)
   ├─ login: no usage found
   └─ logout: no usage found

Example: The ´avo status´ command in Avo CLI

You can learn more about using the Avo CLI in CI/CD here:

Avo in CI/CD

How to use the Avo CLI in CI/CD

Read

Validate with implementation status in the tracking plan

For every source the Avo Functions are installed on, you’ll find an implementation status in the Avo Tracking Plan. When looking at from which sources an event is sent in your Tracking Plan you will notice green, yellow or red status indicator lights next to each source name. This is the implementation status.

You can hover over the source pill in the events table, or click into the event, to learn more about the implementation status.