Adobe® AudienceManager (AAM) is a data management platform that consolidates audience information from all available sources. It identifies, quantifies, and optimizes high-value target audiences, which can then be offered to advertisers across all advertising distribution platforms. Gigya provides functionality for integrating AAM with user data such as age, gender, relationship status, country, likes and more.
This document provides a guide on how to integrate Gigya with AAM.
The solution has three parts:
- Taxonomy - Setting up a field mapping.
- User-ID Sync - Real time alignment of user IDs.
- Get Identity Data - Transfer of user data.
Please create a test site in the Gigya admin console for integration testing (don't use your production site) and use a test list on the target integration platform. We are able to put integrations in "sample mode" for testing, which will restrict audiences to 10 sample accounts.
The purpose of this process is to align the translation of data between Adobe and Gigya. This process must precede the first sync (see below: Get Identity Data from Gigya ) and then be updated when necessary.
Example of file content:
|age||[Value]||Age 18 - 120|
A boolean field needs to be created in the customer's Profile Management - IDS, using the API accounts.setSchema. The field should be called "data.internalAamIdSyncResponseCode" and should have a write access of "clientModify". The field is used by the code which performs the data sync.
Adobe-Gigya User ID Sync
Handles User ID reconciliation between Adobe and Gigya in real-time. To be implemented by the customer in the onLogin event. This event returns the user's ID in Gigya, which in the example below is used to populate ().
Implementation of this code requires that the customer has an Adobe ID (ADOBE_ID in the following example). This must be obtained from your Adobe representative.
After a user logs in or a new user is created, the customer must implement code calling URL http://dpm.demdex.net/ibs:dpid=&dpuuid=
- Data is passed in the next stage.
Users who switch browser\device\clean cookies will be resynced.
- Return codes: 200, OK, Action completed successfully. Any other value indicates that an error has occurred.
Get Identity Data from Gigya
Gigya's User object can contain data from a number of different providers and does not record the source of each field's user data. It does, however, store the original data received from providers in Identity objects which are held within the User object. Gigya recommends that data passed to AAM be taken directly from the Identity objects (rather than from the User object) because the data source is clearly identifiable. This makes it possible to securely prevent data from specific social networks from being passed to DMP sites, or from being used to target ads outside the customer's own server. Identity objects hold data for a particular provider and make it possible to ignore data that originates from specific social networks and avoid non-targetable social network data.
The main sync process between Adobe & Gigya runs every day at a predefined hour. In this process, Gigya's service will send identity data for users that have been synced or changed since the last run.
The newly developed service will:
- Collect the delta set of users that should be reported [query below],
Store them in a tab-delimited file [see below],
Compress [using ZIP format],
FTP to Adobe,
Get FTP Status and email if not successful.
The sync will run daily, matching AAM digesting times.
If no matching users are found, no file will be created or sent.
File Name & Format
Where DPID: Gigya ID in AAM & TIMESTAMP: A UTC timestamp in seconds.
Exclude Social Network
In the event that you do not want to pass data from particular social networks, the query offers an exclude clause that is taken from the configuration file.
The key can be either commented, empty or a comma delimited list.
The integration is based on Adobe’s documentation here.
Adding Gigya to a Web Page
In this section we use an example to demonstrate integration of Gigya with AAM.
The code both syncs users to AAM and indicates to Gigya that the user was synced, so that user data remains offline.