Avo Destination

Destination Info
Partner Owned
  • This integration is partner owned. Please reach out to the partner's support for any issues.

Avo lets you find, fix, and prevent data quality issues upstream. World class data and product teams at companies like Fender, IKEA, and Wolt use Avo to guarantee event data quality upstream, so they can focus on building great user experiences. With Avo you get reliable data with less effort, by moving from reactive damage control to proactive data management and addressing your data quality issues at the source, where the data is created.

With Avo Inspector, data quality is no longer a dream, it’s a workflow. Inspector lets you find, triage, fix, and prevent data quality issues in your event based data. Launch Inspector to discover all your data quality issues and systematically work towards better data, one resolved issue at a time.

The Avo Inspector destination automatically extracts event schemas from your product events, sending only the signatures from the connected Segment sources to the Inspector API. Avo Inspector receives no PII data from your source.

Supported methods

Track events

The Avo destination supports Track events.

Example of Track call:

analytics.track("Login", {
  userName: "John",
  city: "San Fransisco"
  age: 32

This Track call is translated into an event signature that is sent to Avo’s Inspector API.

  "eventName": "Login",
  "properties": [
    {"userName": "string"},
    {"city": "string"}
    {"age": "integer"}

Getting started

  1. From the Segment web app, click Catalog, then click Destinations.
  2. Find the Destinations Actions item in the left navigation, and click it.
  3. Select Avo from the list of destinations, then click Add destination.
  4. Select a source to connect to Avo (Actions) and click Next.
  5. Enter a name for your Avo (Actions) destination and click Create destination.

Configure Avo

Get the Avo API key

Before connecting the Segment source to Avo, you will need an API key for your source.

  1. Create your Avo workspace at avo.app (If you don’t have one already).
  2. From the Avo workspace sidebar, select Sources.
  3. Select an existing source or create a new one. (Avo recommends naming your Avo sources the same as your Segment sources, for example “Web”, “iOS”, “Android”) Select a source
  4. Click the Inspector Setup tab in the Avo source
  5. Copy the API Key Copy API key

Configure Destination

Avo Inspector API key

You can copy the API key from your source in Avo. The API key allows Avo to map the events from your Segment source to the Avo source, to accurately compare your source’s event schemas to your Tracking Plan in Avo.


Environment describes which app environment the source is sent from, Development | Staging | Production. Avo only generates issues for events in your Production environment, but you can see the event shapes for staging and development environments to make sure they are implemented correctly.

App Version Property

App Version Property is an optional (but recommended) field. Having accurate app release versions in Avo Inspector allows you to see how events change across releases. This helps you identify which releases an issue is impacting, and monitor for regressions in future releases after an issue has been resolved.

Without app versions, the inspector has no way of differentiating between old and new releases, and might surface irrelevant issues based on old releases. Learn more about how Inspector uses releases in Avo’s documentation.

For most mobile sources, Avo automatically fetches the app version from Segment Context. If you have an event property describing the app release version of your source (for example, “app_version”) you can provide it under App Version.

If you are unsure of whether this applies to your source, or if you don’t know which event property to use, you can proceed with setting up the source and add this information later.

Select a source

Destination Settings

Setting Description
Avo Inspector API Key Required.

Avo Inspector API Key can be found in the Inspector setup page on your source in Avo.

App Version Property

If you send a custom event property on all events that contains the app version, please enter the name of that property here (e.g. “app_version”). If you do not have a custom event property for the app version, please leave this field empty.

Environment Required.

Avo Inspector Environment

Available Presets

Avo has the following presets:

Preset Name Trigger Default Action
Track Schema From Event Event type = "track"
Track Schema From Event

Available Actions

Build your own Mappings. Combine supported triggers with the following Avo-supported actions:

Mapping limits per destination

Individual destination instances have support a maximum of 50 mappings.

Track Schema From Event

Sends event schema to the Avo Inspector API

Track Schema From Event is a Cloud action. The default Trigger is: type = "track"

Click to show / hide fields

Field Description
Event Name* Type: STRING

Name of the event being sent

Properties* Type: OBJECT

Properties of the event being sent

Message ID* Type: STRING

Message ID of the event being sent

Created At* Type: STRING

Timestamp of when the event was sent

App Version Type: STRING

Version of the app that sent the event

App Name Type: STRING

Name of the app that sent the event


URL of the page that sent the event

Enable Batching? Type: BOOLEAN

When enabled, Segment will send events in batches.


You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Real-time to batch destination sync frequency

Real-time audience syncs to Avo may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.


Segment lets you change these destination settings from the Segment app without having to touch any code.

Setting Description
Avo Inspector API Key
string. Avo Inspector API Key can be found in the Inspector setup page on your source in Avo.
App Version Property string. If you send a custom event property on all events that contains the app version, please enter the name of that property here (e.g. “app_version”). If you do not have a custom event property for the app version, please leave this field empty.
select, defaults to prod.

Avo Inspector Environment

This page was last modified: 22 Feb 2024

Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
Create free account