Xandr (formerly AppNexus) Connector Setup Guide for Customer Data Platform (CDP)

This article describes how to set up the Xandr (formerly AppNexus) connector.

Requirements

Action Name	Trigger on Audience	Trigger on Streams
Add User to or Remove from Segment	✓	✓

Go to the connector marketplace and add a new connector. For more information, see About connectors.

To configure your vendor, follow these steps:

Click Continue to configure the connector actions. Enter a name for the action and select the action type from the list.

General Mappings
- (Required) Map your Attribute(s) to the required event fields.
- Select the field of choice from the To drop-down list or enter a custom value.

Option	Description
`uuid2` (Required)	Use the Xandr Cookie Match tag in Tag Management to obtain the Xandr `uuid2` value from the visitor’s browser
`sess`	Automatically sets `sess=1` and sends to Xandr along with `uuid2` value in Cookie Header. Map `sess` to `0` to override the default.
`add`	Comma-separated segments to add for the user
`add_code`	Comma-separated list of segment codes to add for the user. The the `member` parameter is required when using codes.
`remove`	Comma-separated segments to remove for the user
`remove_code`	Comma-separated list of segment codes to remove for the user. Use the `member` parameter is required when using codes
`member`	ID of the member who owns the segment.
`other`	A user-defined field with an integer value that is stored for reporting. Some members use this as the source of the data used.
`redir`	A redirect URL used to piggyback another pixel
`external_uid`	A string that corresponds to an external user ID for this user

Was this page helpful?

This page was last updated: March 5, 2020