Data Integration Methods

A high-level overview of how Audience Manager exchanges information with other data providers and systems.

Supported Data Integration Methods: Real-Time and Server-to-Server

Choosing the right integration method depends on a combination of business requirements and the technical capabilities of your data partner. Audience Manager exchanges visitor information with other data providers by either of the following methods:

• Real-Time: Transfers data immediately as a user visits your site. This method is also known as a synchronous integration.
• Batch (Server-to-Server): Transfers data between servers on a set schedule after a visitor has left the page. This method is also known as an out-of-band or asynchronous integration.

Prerequisites: Create a Trait Taxonomy

Before the integration process begins, remember to create traits and a folder structure in the Audience Manager UI. The taxonomy will contain all your traits organized in a logical hierarchy.

Integration Use Cases

A use-case summary of Audience Manager data integration methods along with the advantages and disadvantages of each.

Real-Time Server-to-Server Integrations

A real-time server-to-server data integration rapidly synchronizes user data between Audience Manager servers and another targeting system. In most cases, data exchange takes place within seconds or minutes, depending on the refresh rate of the targeting system. Note, however, the targeted system determines this refresh interval, not Audience Manager. Furthermore, the refresh rate can vary between different systems. A real-time, server-to-server integration is the preferred integration type for data exchanges. Audience Manager uses this method whenever targeting partners can support it.

Advantages:	Lets you qualify users for segments without seeing them again on the page, in a video player, etc. Reduces the number of HTTP calls from the page. Fewer calls helps preserve the user experience. Helps with time sensitive targeting so you can take action on a qualified user quickly. Useful when moving to a DSP for offsite targeting.
Disadvantages:	Less useful for onsite targeting when you need to target the user on the same page, or the next page, based on qualifying a user for that segment.

Server-to-Server Batch Integrations

A server-to-server batch integration bundles data and sends it to other systems at set intervals rather than in near real time. Data transfer intervals start from 24 hours. Some data providers support this integration type only. However, we’ve seen a general trend away from batch integrations towards real-time integration methodologies.

Advantages:	Lets you qualify users for segments without seeing them again on the page, in a video player, etc. Useful for targeting that is not time sensitive.
Disadvantages:	The synchronization interval can delay targeting against the most current data.

Real-time Calls

Real-time calls exchange data with Audience Manager immediately, as a user visits your site or takes action on the page. With this method, targeting systems get the most updated segment qualification data and can take that information into account during a content or ad delivery decision. Also, this process works with publisher ad servers where we update qualified segments to a first-party cookie that is read into an ad call as key-value pairs. Currently, Audience Manager uses real-time calls to integrate with Adobe Target and other content management systems.

Advantages:	Lets you target the next page, content area, or ad impression based the most recent segment qualification.
Disadvantages:	Adds a call to Audience Manager from the page.

Pixels Syncs to Targeting Systems

Pixel synchronization maps segments to pixels on the page. The pixel fires and transmits data when a user qualifies for a particular segment. Pixel synchronization is a rudimentary and unreliable data transfer mechanism. Top tier data providers and systems rarely use it.

Advantages:	Real-time data transfers.
Disadvantages:	Can add a lot of client-side calls from the page. Unreliable for data transmission. 5% to 20% loss is normal.

How to Choose a Data Delivery Method

Describes technical and business reasons for sending data via synchronous (real-time) or asynchronous (server-to-server) methodologies.

Selecting a Data Delivery Type

• Technical Considerations: Data delivery depends on the technical capabilities of the data partner. Audience Manager can send/receive data in real-time from the browser or by batch updates through offline, server-to-server communication processes.
• Business Considerations: The business reasons for selecting one delivery method or another depend on the technical capabilities of your destination partner and how you want to use this data. Typically, synchronous data transfers are useful when you need to take action on user data immediately. Asynchronous data transfers may be useful when immediate action is not required and when you have time to build deeper user profiles for later use.

Real-Time Data Transfer Process

A general overview of how Audience Manager performs a synchronous data exchange with a third-party vendor.

Real-Time Data Transfer

Real-time data transfers send and receive segment IDs as a user visits or takes action on your site. Typically, synchronous data transfers are useful when you need to qualify or segment users right away, as they navigate through your inventory.

Real-Time Data Integration Steps

The real-time data integration process works as follows:

1. A user visits a customer’s site that contains Audience Manager code.
2. Audience Manager loads an Iframe and makes a call to the Data Collection Server (DCS).
3. The DCS calls the third-party server (in real time) to check if the vendor has any segment information about the user.
4. The third party returns segment information about that user to Audience Manager.
5. Audience Manager ingests segment information and makes it available for targeting.

Batch Data Transfer Process

A general overview of how Audience Manager exchanges data synchronously (in real time) with a third-party vendor.

Batch Data Integration

The batch (server-to-server) data integration process follows most of the steps outlined in the real-time data transfer process. However, instead of returning segment IDs immediately, user information is saved to our servers and synchronized with a third-party data provider at regular intervals. The asynchronous data transfer process is useful when:

• Immediate data transfers are not required.
• Collecting data to build a large pool of segmented users.
• You want to reduce data discrepancies and HTTP calls from the browser.

Batch Data Integration Steps

1. A user visits a customer site.
2. Audience Manager and the third-party data provider assign the visitor a unique ID (usually with a cookie).
3. Audience Manager calls the third-party data provider to match visitor IDs.
4. A scheduled request, usually on a daily interval, exchanges visitor segment data between Audience Manager and your third-party data provider.

For information describing the time frames when Audience Manager processes inbound and outbound Server-to-Server (S2S) file transfers, see Reporting and File Transfer Time-Frame Guidelines.