Behavior Tracking > DMP Sync - Adobe Audience Manager

DMP Sync - Adobe Audience Manager

How to send user data to OneSpot from your DMP

If you have a DMP and would like to send OneSpot data about your visitors you can configure your DMP to sync user data (such as segments) with OneSpot. Currently OneSpot only supports exchanging data with the Adobe Audience Manager (AAM) as a DMP. We expect to support other DMPs in the future, if you have a different DMP and would like to take advantage of syncing DMP data, please contact your account manager.

Example use cases for sending your user data to OneSpot from your DMP:

  • You would like OneSpot to add editorial rules around custom user data that you have in your DMP. For example, if you store user segment data (such as preferences) you may want OneSpot to use that data to create business rules around which users can/should see what content. Let’s say you have tagged some visitors as vegan then you may want to guarantee that these users only see content that is tagged as vegan. In order to do this we would need to set up a one-way data transfer from your DMP into OneSpot so we could identify which visitors should have the vegan filter applied.
  • You would like OneSpot to generate some custom reporting for you that takes custom user metadata into account. Lets say for instance you have segments of users that you’ve identified as high-value, medium-value or low-value visitors and wanted to understand these users content consumption behaviors. OneSpot’s Strategic Services team can generate custom reports and could join up your user metadata into the report. In order to do this we would need to set up a one-way data transfer from your DMP into OneSpot.
Adobe Audience Manager (AAM) supports two types of data delivery: batch and server2server. Batch delivery is required and server2server is optional. At this time, OneSpot supports batch sync with AAM as a destination but not server2server syncing.

Transferring and syncing visitor data from your DMP is a two-step process

1. ID Synchronization (cookie-sync)

Cookie-sync is the process where OneSpot and your DMP match IDs for the same site visitors. For example, a DMP customer may know a user by ID 123. However, OneSpot could identify this user with ID 456. The synchronization process allows the DMP and a OneSpot to reconcile these different IDs and identify users in their respective systems. Once complete, DMP and OneSpot should have corresponding IDs for each unique user seen on our networks.

Here is the documentation from Adobe Audience Manager on the ID sync process. However, OneSpot handles all of the cookie sync process in our tracking script so OneSpot will sync IDs with AAM automatically and starts building up a pool of matching user IDs in the two systems. There is no setup required on your end to start the cookie sync process.

2. Discuss requirements for using segment data with your account representative

If you have ideas/thoughts on how OneSpot can leverage your user segment data, you and your account manager should discuss the idea and validate the feasibility and discuss the types of data to be transferred from AAM to OneSpot.

3. Setup OneSpot as a Destination in Adobe Audience Manager

Adobe Audience Manager has a self service capability that enables their customers to set up OneSpot as a destination in your account and define which segments that you want to send to OneSpot. Here are the instructions from Adobe Audience Manager using Destination Builder to get this set up.

At this time, OneSpot only supports batch transfer with AAM and not server2server transfer, so you can ignore any AAM processes that are specific to setting up server2server derstinations.

Since OneSpot does not have access to your AAM account, this is a step you will need to handle. Any support requests on setting up destinations from AAM should be sent to your Adobe account team.

At this time, data exchange from OneSpot to AAM is not currently supported. However if you have a compelling need for this transfer please talk to your account manager.