Overview

GIGYA was purchased by SAP and is now SAP Customer Data Cloud.

GIGYA offers a suite of social plugins including social login, sharing, identity management, mobile website integration, and subscriptions.

Integrating Lytics with GIGYA allows you to pull insights from your users' login patterns, subscriptions, and GIGYA ID which is often used as an identifier across platforms. You can also export Lytics audience membership containing behavioral scores and content affinities to personalize your brand experiences delivered to existing GIGYA users.

Authorization

If you haven't already done so, you will need to set up a GIGYA account before you begin the process described below. If you are new to creating authorizations in Lytics, see the Authorizations documentation for more information.

Select Gigya fraom the list of providers.
Select the Gigya method for authorization.
In the Label text box, enter a name for the authorization
(optional) In the Description text box, enter a description for this authorization
from the Datacenter input, select the GIGYA datacenter your account uses. See GIGYA's documentation for more information.
6.In the API Key text box, enter your Api Key from your GIGYA account dashboard.
In the User Key text box, enter User Key from your GIGYA account settings by navigating to Your name > Account.
In the Secret Key text box, enter your Secret Key from your GIGYA account settings
Click Save Authorization.

gigya-auth

Import Users

Import GIGYA contacts and email subscriptions into Lytics to build a more complete view of your customers. You can import from full accounts and lite GIGYA (SAP Customer Data Cloud) accounts.

Integration Details

Implementation Type: Server-side Integration.
Implementation Technique: REST API Integration
Frequency: Batch Integration with option for continuous, hourly updates.
Resulting data: User Profiles and User Fields.

This integration utilizes the GIGYA APIs to import user data. Once the import is started the job will:

Validate credentials by getting the user schema.
Search for users that have been updated since the last import.
1. Initial search request: SELECT * FROM accounts WHERE lastUpdatedTimestamp >= <last import date> ORDER BY lastUpdatedTimestamp LIMIT 10000, and openCursor = true.
2. Page through results.
Search for lite users that have been updated since the last import.
1. Initial search request: SELECT * FROM emailAccounts WHERE lastUpdatedTimestamp >= <last import date> AND hasLiteAccount=true AND hasFullAccount=false ORDER BY lastUpdatedTimestamp LIMIT 10000, and openCursor = true.
2. Page through results.
Search for subscriptions that have been updated since the last import.
1. Initial search request: SELECT * FROM emailAccounts WHERE subscriptions.<subscription name>.email.lastUpdatedSubscriptionState > <last import date>, and openCursor = true.
2. Page through results.
Ingest the data from the searches into the gigya_users stream.

Fields

The following fields are included in the default mapping of the gigya_users stream:

Source Field	Conditional	Lytics User Field	Description	Type
address		address	Address	string
birth_day		birth_day	Birth Day	string
birth_month		birth_month	Birth Month	string
birth_year		birth_year	Birth Year	string
city		city	City	string
country		country	Country	string
created		gy_user_created	GIGYA Profile Created	date
email(email)		email `unique id`	Email Address	string
emaildomain(email)		email_domain	Email Domain	string
facebook_id		fb_uid `unique id`	Facebook User ID	string
first_name		first_name	First Name	string
gender		gender	Gender	string
google_id		google_id `unique id`	Google ID	string
id		gy_profile_id `unique id`	GIGYA Distinct ID	string
instagram_id		instagram_id `unique id`	Instagram ID	string
is_registered		gy_is_registered	GIGYA Is Registered	string
last_login		gy_user_last_login	GIGYA Profile Last Login	date
last_name		last_name	Last Name	string
last_updated		gy_user_updated	GIGYA Profile Updated	date
login_provider		gy_login_provider	GIGYA Login Provider	string
map(subscription_name, double_optin-status)	IF exists(subscription_name)	gy_subscription_optin_status	GIGYA Subscription Optin Status	map[string]string
map(subscription_name, subscribed)	IF exists(subscription_name)	gy_subscriptions	GIGYA Subscriptions	map[string]bool
map(subscription_name, todate(modified))	IF exists(subscription_name)	gy_subscription_modified_date	GIGYA Subscription Modified Date	map[string]time
site_id		gy_site_id	GIGYA Site ID	string
state		state	State	string
tobool("true")	IF eq(lite_account, "false") OR eq(full_account, "true")	gy_lite_account	GIGYA Lite Account	bool
twitter_id		tw_uid `unique id`	Twitter User ID	string
twitter_name		tw_user_screenname `unique id`	Twitter Username	string
zip		zip	Zip	string

Configuration

Follow these steps to set up and configure an import job for Gigya in the Lytics platform. If you are new to creating jobs in Lytics, see the Data Sources documentation for more information.

Select Gigya from the list of providers.
Select the Import Audiences job type from the list.
Select the Authorization you would like to use or create a new one.
Enter a Label to identify this job you are creating in Lytics.
(Optional) Enter a Description for further context on your job.
Complete the configuration steps for your job.
(optional) In the Import Since text box, enter the date from which you want to import data using the YYYY-MM-DD format. If left blank, Lytics will import all available data.
(optional) From the Extended Data Fields input, select additional data fields to import to Lytics. Basic profile data will automatically be imported.
(Optional) Toggle Show Advanced Options. Select the Keep Updated checkbox to run this import hourly.
Click Start Import.

gigya integration import config

Export Users

Export Lytics audience membership to your existing GIGYA users to enrich your marketing efforts with cross-channel data, behavioral scores, and content affinities from Lytics.

Integration Details

Implementation Type: Server-side Integration.
Implementation Technique: REST API Integration.
Frequency: Batch Integration.
Resulting data: Array of audiences the user is a member of.

This integration utilizes GIGYA APIs to send user data. Once the export is started the job will:

Iterate through users in the selected audience.
Get the audience membership for each user.
Export the user's audience membership to either:
1. Data store.
2. User's account.

Fields

By default, Lytics exports the following fields to GIGYA:

Lytics User Field	Description	GIGYA Field	Type
GIGYA ID	GIGYA ID	UID	string
Audience Membership	Array of audiences the user is a part of.	lytics_segments	[]string

Configuration

Follow these steps to set up and configure an export job for Gigya in the Lytics platform. If you are new to creating jobs in Lytics, see the Destinations documentation for more information.

Select Gigya from the list of providers.
Select the Export Audiences job type from the list.
Select the Authorization you would like to use or create a new one.
Enter a Label to identify this job you are creating in Lytics.
(Optional) Enter a Description for further context on your job.
Select the audience to export.
Complete the configuration steps for your job.
(Optional) Toggle Show Advanced Options.
- (optional) From the Gigya ID Field input, select the field name that contains the Gigya unique id.
- (optional) From the Storage input, select where the user fields get stored in GIGYA.
- (optional) Select the Keep Updated checkbox, to continuously run this export.
- (optional) From the Time of Day input, select time of day to start export each day.
- (optional) From the Timezone input, select timezone for time of day.
Click Start Export.