InnovidXP Connector Setup Guide | Server-Side Connectors

Connector Actions

Action Name	AudienceStream	EventStream
Track Event	✓	✓

Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector.

After adding the connector, configure the following settings:

Client Host
- Client-specific collector hostname.
- A static value supplied by TVSquared.
- For example, collector-1233.tvsquared.com.
Site ID
- Client-specific collector site ID.
- A static value supplied by TVSquared.
- For example, TV1234-1.

Click Next or go to the Actions tab. This is where you configure connector actions.

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

The following table lists URL parameter to be encoded in the server-to-server request:

The servertrack and RAND parameters are automatically set by Tealium.

Parameter	Description
Visitor ID (`VISITORID`)	Required. Unique ID for the visitor. URL parameters to be encoded in the server-to-server request. For example, `0123456789ABCDEF`.
User Agent (`UA`)	User agent, if applicable. For example, `Mozilla/5.0`.
Browser Language (`LANG`)	Browser language, if applicable. For example, `en`.

The following table lists the fine-grained session-level tracking information:

Parameter	Description
`appid`	ID of the app. For example, `com.myapp.appster`.
`appname`	Name of the app. For example, My Application.
`country`	Country. For example, `US`.
`deviceid`	Device ID. For example, `e3f5536a141811db40efd6400f1d0a4e`.
`deviceidtype`	Device ID type. For example, `AAID` or `IDFA`.
`ip`	Required. The IP address of the mobile device. For example, `8.8.8.8`.
`lang`	User language. For example, `en`.
`medium`	Required. Set to `app` for mobile app. For example, `app`.
`os`	Operating system. For example, `ANDROID`.
`source`	Required. Identifies the name of the partner supplying the data. For example, `myApplication`
`ua`	User Agent. For example, `Mozilla/5.0`.
`user`	User ID. Client-supplied private unique user identifier, such as an internal ID from a billing system. For example, `U1234`.

The following table lists the fine-grained per-action tracking information:

Parameter	Description
Action Name	Required. Name of the action being performed. For example, `INSTALL`.
`adchannel`	Advertising channel name. For example, `Social`.
`campaign`	Campaign name. For example, `NY_Acquisition`.
`currency`	Currency of revenue. For example, `USD`.
`id`	Action ID of an individual user action, such as an order ID. For example, `42342`.
`preattributed`	Whether the event has already been attributed. For example, `1`.
`prod`	Product name. For example, `angry birds`.
`promo`	The promo code, if the user used one. For example, `ABCD`.
`rev`	Revenue amount. If not specified, is supplied by default. For example, `12`.
`ts`	Exact Unix timestamp of event, in UTC format. If not provided, will be provided by default. For example, `1538996046`.