Solution Overview

Please create a test site in the Gigya admin console for integration tes=
ting (don't use your production site) and use a test list on the target int=
egration platform. We are able to put integrations in "sample mode" for tes=
ting, which will restrict audiences to 10 sample accounts.

User Data

Access to user information requires that users login to the site t=
hrough Gigya.

If you are implementing Social Logi=
n, then after the user logs-in the data available in the User object may be pushed to Lotame. This object, whi=
ch is returned by the so=
cialize.getUserInfo method contains social information pulled from soci=
al networks.

To find out whether RaaS/IS package is part of your site package, or to =
activate RaaS/IS package, please contact your Gigya Account Manager or=
contact us by filling in a support form on our=
site.

Adding Gigya to a Web=
Page that Uses Lotame

This section demonstrates how to integrate Gigya with Lotame.

We take a simple web page that uses Lotame and add Gigya code to it, thu=
s pushing the logged in user's data to Lotame.

Gigya's User object can contain=
data from a number of different providers and does not record the source o=
f each field's user data. It does, however, store the original data receive=
d from providers in Identity object=
s which are held within the User object=
. Gigya recommends that data passed to Lotame be taken directly =
from the Identity objects (rather t=
han from the User object) because the data source is clearly identifiable. =
This makes it possible to securely prevent data from specific social networ=
ks from being passed to DMP sites, or from being used to target ads ou=
tside the customer's own server. Identity objects hold data for a part=
icular provider and make it possible to ignore data that originates from sp=
ecific social networks and avoid non-targetable social network da=
ta. Our code example below demonstrates retrieval of Identity objects =
from a User object.

A Simple Pa=
ge that Uses Lotame (Without Gigya)

The following code inserts static data into Lotame:

To use the code enter your Lotame ID in the "src" line and in the l=
otame-id variable. Enter a valid Lotame behavior type in th=
e lotameBehavior variable.

When the user signs-in the onLogin event returns the User objectto the web page. User objects can also b=
e retrieved using socialize.getUserInfo (not demonstrated in this code). T=
he user object contains an array of providers and an Identity object for each provider, with =
the provider's data for this user.

Note that some social networks do not allow their user data to be t=
ransferred to direct marketing providers, while others do not allow ce=
rtain fields to be used in targeted advertising outside the customer's site=
. It is the customer's responsibility to comply with any such restrictions =
placed by each individual social network. The code below shows how this is =
done, for example, if you do not want to transfer LinkedIn data, or w=
ant to mark Facebook "age" data as non-targetable (i.e. you might use =
the age data for reporting purposes only). To achieve this, the onLogi=
n event in the example calls the web-page's cbUserInfo f=
unction which extracts the identity object for each provider.&nbs=
p;LinkedIn data is ignored, and Facebook "age" data is marked as =
non-targetable. Other fields (or providers) can be added as required.=