Avo Inspector v2 Destination

Avo Inspector v2 (Actions) provides the following benefits over the v1 destination:

• Batch processing: Events are processed in batches for improved performance and efficiency at scale.
• Property value validation: In Development and Staging environments, event property values can be validated against your Avo Tracking Plan constraints (allowed values, regex patterns, numeric ranges) using end-to-end encryption.

Avo Inspector v2 supports Track events. Segment translates each Track call into an event schema signature that is sent to Avo's Inspector API.

Example Track call:

1
analytics.track("Login", {
2
  userName: "John",
3
  city: "San Francisco",
4
  age: 32
5
});

This is translated into an event signature:

1
{
2
  "eventName": "Login",
3
  "properties": [
4
    {"userName": "string"},
5
    {"city": "string"},
6
    {"age": "integer"}
7
  ]
8
}

1. From your workspace's Destination catalog page search for "Avo Inspector".
2. Select Avo Inspector v2 and click Add Destination.
3. Select an existing Source to connect to Avo Inspector v2 (Actions).
4. Name your destination connection descriptively (for example, "Avo Web Prod").
5. In your Avo workspace, navigate to Inspector > Sources and either create a new source or select an existing one. Avo recommends naming your Avo sources the same as your Segment sources (for example, "Web", "iOS", "Android").
6. Go to the Inspector Setup tab and copy the API Key.
7. Enter the API Key in the Avo Inspector v2 destination settings in Segment.
8. Select the Environment that matches your source (Development, Staging, or Production). Avo only generates issues for events in your Production environment, but you can see event shapes for all environments.

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 impacts, and monitor for regressions after an issue has been resolved.

Set the App Version Property Name field to the name of a custom event property containing your app version (for example, app_version). If not provided, Inspector falls back to context.app.version.

Without app versions, 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 are unsure whether this applies to your source, you can proceed with setting up the source and add this information later.

In Development and Staging environments, Avo Inspector v2 can validate property values against constraints defined in your Avo Tracking Plan, such as allowed values, pinned values, regex patterns, and min/max ranges. This validation doesn't run in Production — in Production, only event schemas are sent.

Property values are encrypted end-to-end before transmission using elliptic curve cryptography. Avo only stores encrypted values and can't decrypt them. Only you can decrypt the values using your private key, which you can use in the Inspector Debugger to inspect the actual reported values.

To set this up:

1. Enable property value validation in your Avo workspace settings.
2. Generate an elliptic curve key pair:
   Copy code block

   node -e "const { createECDH } = require('crypto'); const ecdh = createECDH('prime256v1'); ecdh.generateKeys(); console.log('Private Key:', ecdh.getPrivateKey('hex')); console.log('Public Key:', ecdh.getPublicKey('hex', 'compressed'));"

3. Save your private key in a secure location like a password manager. Never share or expose your private key with a third party.
4. Add the Public Encryption Key (the compressed public key from step 2) to the Avo Inspector v2 destination settings in Segment.

See Property Value Validation in the Avo documentation for more information about Property Values.

Avo Inspector v2 has the following presets

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

• 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"

After connecting, navigate to Inspector > Events in your Avo workspace to monitor incoming data. Events typically appear within 2 minutes. Make sure to select the correct environment in Inspector to see your data.

To migrate from the Avo Inspector v1 destination to v2:

1. Add the Avo Inspector v2 destination to your Segment workspace alongside your existing v1 destination.
2. Configure it with the same API key and environment settings you used to configure your Avo v1 destination.
3. Verify that events from your Avo Inspector v2 destination appear correctly in your Avo workspace.
4. Once you've verified you're recieving events from the v2 destination, return to the Segment app and disable the v1 destination.

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.

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