Avo Destination

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 product analytics. 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 a 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.

Destination Settings

Available Presets

Avo has the following presets:

Available Actions

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

• Track Schema From Event

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

Getting 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”)
4. Click the Inspector Setup tab in the Avo source
5. Copy the API Key

Destination settings

1. Copy the API Key from Avo into the field API Key in settings.
2. Select an environment you’d like the data to go to within Avo. It should reflect from what environment the source is receiving data from. (Production / Development / Staging)
3. (Optional): If you have an event property describing the app release version of your source you can provide it under App Version. By default the destination attempts to extract your app release version from {context.app.version} which defaults to unversioned if that does not exist. Having accurate app release versions in Avo Inspector will help you identify which releases an issue is impacting, and monitor for regressions in future releases after you’ve resolved the issue.

Engage

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.

Settings

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