Set up OpenX as a destination and send Audience Manager segment data to that platform.
For onsite ad server targeting only.
Standards for code placement, supported key-value formats, reports, and the type of segment data sent to OpenX.
Review the following before setting up OpenX as an Audience Manager destination:
get_aamCookieFunction: Code that captures the Audience Manager user ID and cookie data. Place this code on the top of the page or inside the
UUID. Audience Manager can pick up or receive these via FTP.
Audience Manager sends data in the form of key-value pairs. Create key-value pairs according to the following specifications:
c.color = red, green, blue).
c.color=red & c.price = 100 & c.condition = new).
The amount data passed in to OpenX depends on how many segments a particular user qualifies for. For example, say you set up 100 Audience Manager segments. If a site visitor qualifies for five of them, then only those five segments get sent to OpenX (not all 100).
Create a cookie destination for OpenX in Audience Manager.
In Audience Manager, a destination is any other system (ad server, DSP, ad network, etc.) that you want to share data with. Destination Builder provides the tools that let you create and manage these data delivery processes. Audience Manager destination features are located in Audience Data > Destinations. To get started, click Add New Destination and follow the steps below.
To complete the Basic Information section:
To complete the Configuration section:
To add a segment to a cookie destination:
Modify OpenX settings to work with Audience Manager segment data.
To set up OpenX:
Install DIL code across your site.
Create OpenX as a cookie destination in Audience Manager.
get_aamCookie function at the top of the page, ideally within the
<head> codeblock. The
get_aamCookie code is available here.
Modify your ad tag to call the
get_aamCookie function and include the cookie name you provided when setting up the OpenX destination. For example, if you named the cookie
test_cookie, then the ad tag should call
get_aamCookie and reference the cookie name.
Your ad tag could look similar to the example below.
<a href= "https://client.adserver.net/?" + get_aamCookie('test_cookie') + "&etc&xid=" + get_aamCookie('aam_uuid')
Remember to include
xid= . It holds the actual unique user ID (UUID) passed in during an ad call.
The fully formed ad call could look similar to this:
https://client.adserver.net/?c.key1=val1&c.key2=val2&etc& xid =3286487458745343