Avo Inspector Connector Setup Guide | Server-Side Connectors |Preview of Tealium Docs

API Information

This connector uses the following vendor API:

API Name: Avo Inspector
API Version: v1.0.2
API Endpoint: https://api.avo.app/inspector/tealium/v1/track
Documentation: Avo Inspector API

Batch Limits

This connector uses batched requests to support high-volume data transfers to the vendor. For more information, see Batched Actions. Requests are queued until one of the following thresholds is met or the profile is published:

Max number of requests: 30
Max time since oldest request: 5 minutes
Max size of requests: 1 MB

Connector Actions

Action Name	AudienceStream	EventStream
Send Event Data (Real-Time)	✗	✓
Send Event Data (Batched)	✗	✓

Configure Settings

Navigate to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see About Connectors.

After adding the connector, configure the following settings:

API Key
Required. This API Key is created when activating an inspector source in Avo. Each inspector source requires a separate Avo destination in Tealium, which allows Avo to determine the source of the events.
Environment
Required. The current environment: Prod, Dev, or Staging.
Origin (String)
Optional. Origin of the call.

Actions

Enter a name for the action and select the action type from the drop-down menu.

The following section describes how to set up parameters and options for each action.

Send Event Data (Real-Time)

Parameters

Parameter	Description
Event Type	Type of event. Either `event` or `sessionStarted`.
Template Variables	Provide template variables as data input for Templates. See Template Variables Guide documentation for usage examples. Name nested template variables with the dot notation. Example: `items.name.` Nested template variables are typically built from data layer list attributes.
Templates	Provide templates to be referenced in Event Parameters. For more information, see Templates Guide. Templates are injected by name with double curly braces into supported fields, for example: `{{SomeTemplateName}}`.

Send Event Data (Batched)

Parameters

Parameter	Description
Event Type	Type of event. Either `event` or `sessionStarted`.
Template Variables	Provide template variables as data input for Templates. See Template Variables Guide documentation for usage examples. Name nested template variables with the dot notation. Example: `items.name.` Nested template variables are typically built from data layer list attributes.
Templates	Provide templates to be referenced in Event Parameters. For more information, see Templates Guide. Templates are injected by name with double curly braces into supported fields, for example: `{{SomeTemplateName}}`.