Gigya Job Openings

Page History

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Overview

IdentitySync is Gigya's robust ETL solution (Extract, Transform, Load) that offers an easy way to transfer data in bulk between platforms. Use it to transfer user data from Gigya to a third-party platform or vice versa, or even from one Gigya database to another. 

With IdentitySync, you can:

  • Take all the permission-based social and profile identity information stored at Gigya and channel it into another platform, such as an ESP, CRM, or marketing automation system.
  • Get up-to-date data from a 3rd party platform, such as a user newsletter subscription status, survey responses or account balance, and import it into Gigya.sync existing Gigya user profiles or create new ones ad-hoc.
  • Import from one Gigya site to another

IdentitySync is the engine that runs Gigya integrations with:

IdentitySync jobs can be carried out on a one-time basis, for example if migrating data, or they can be scheduled to run on a regular basis in order to keep your platforms synchronized.

IdentitySync APIs use the idx namespace. See Using the IDX API below for details.

Include Page
IdentitySync Activation Template - Premium
IdentitySync Activation Template - Premium

Use Cases

IdentitySync gives you the flexibility to use your data in any way you need. For example, with IdentitySync, the following scenarios are supported: 

Admin Activities

  • Retrieve all accounts that have remained unverified or unregistered for over a week (isVerified==false or isRegistered==false and created>'one week ago'), export the relevant email addresses to an ESP, from which to send follow-up emails.
  • As a sports club, regularly import accounts from an external ticketing system, thus fortifying your fanbase. 
  • Query the audit log to retrieve deleted users, and use a batch job to other external systems so that they can be deleted from there, too.

User Segmentation and Progressive Profiling

  • Set up data fields for segmenting users according to certain types of behavior in your site - such as Loyalty interactions, purchases or page visits (people who like and share content related to tabi socks, or have purchased said socks) then use an IdentitySync job to send only users that match these criteria to a marketing system for a targeted campaign (50% off in our summer sock sale). 
  • Use a Gigya-toGigya IdentitySync job to query users by Facebook likes stored in their profiles - for example, people who like vampire and zombie related content - and to plant a value (e.g. "horrorFic") in a Gigya data field. Then launch a gruesome Halloween marketing campaign targeting these users. 
  • Use an IdentitySync job to initialize default data to a Boolean field (e.g. set to null), and using a custom component that is activated according to this value, trigger a progressive profiling screen that requests more information from site visitors. 

Main Features 

For full, up-to-date details of the service's capabilities, see the Component Repository.

Main Supported Data Sources/TargetsSample TransformationsMain File Formats
  • Gigya accounts and email accounts
  • Gigya Data Store
  • FTP
  • SFTP
  • Amazon S3 cloud
  • Azure
  • ESP, DMP, CRM Platforms
  • Reordering, renaming, and removing fields
  • Replacing strings within field values using regex
  • Using JEXL expressions to create new fields based on the values of existing fields
  • Flattening objects (with some limitations)
  • Flattening an array field into a string field
  • PGP encryption and decryption (note that GPG is not supported)

Main file formats supported:

  • DSV
  • JSON
  • Salesforce, Mailchimp, Krux and other formats
  • GZIP, LZO

Building Blocks

Each IdentitySync job runs a dataflow. The building blocks of the dataflow are dedicated components. A component is a pre-configured unit that is used to perform a specific data integration operation. The components include readers, writers, transformers and lookups. Each component is responsible for performing a single task, such as:

...

Code Block
languagejs
linenumberstrue
{  
  "name":"NextDigital Krux",

  "description":"enter your dataflow description here...",

  "steps":[  

     {  
        "id":"account",
        "type":"datasource.read.gigya.account",
        "params":{  
           "select":"UID,profile.gender,profile.age",
           "where":"data.internalKruxIdSyncResponseCode=true"
        },
        "next":["rename"]
     },

     {  
        "id":"rename",
        "type":"field.rename",
        "params":{  
           "fields":[  
              {  
                 "sourceField":"UID",
                 "targetField":"id"
              },
              {  
                 "sourceField":"profile.gender",
                 "targetField":"gender"
              },
              {  
                 "sourceField":"profile.age",
                 "targetField":"age"
              }
           ]
        },
        "next":["gender"]
     },

     {  
        "id":"gender",
        "type":"field.evaluate",
        "params":{  
           "fields":[  
              {  
                 "field":"gender",
                 "expression":"gender eq 'm' ? 'male' : (gender eq 'f' ? 'female' : null)"
              }
           ], 
			"language": "jexl",
        },
        "next":[  
           "csv",
           "krux"
        ]
     },

     {  
        "id":"csv",
        "type":"file.format.dsv",
        "params":{  
           "fileName":"Gigya_Krux_NextMedia_hk-apple",
           "fileExtension":"csv",
           "columnSeparator":","
        },
        "next":["sftp"]
     },

     {  
        "id":"sftp",
        "type":"datasource.write.sftp",
        "params":{  
           "host":"...",
           "username":"...",
           "password":"...",
           "remotePath":"nextdigital-krux"
        }
     },

     {  
        "id":"krux",
        "type":"file.format.krux",
        "params":{  
           "filePrefix":"Gigya_Krux_NextMedia_hk-apple",
           "fileDateFormat":"yyyyMMdd_HHmm"
        },
        "next":["lzo"]
     },
     {  
        "id":"lzo",
        "type":"file.compress.lzo",
        "params":{  
           "createIndexFile":true
        },
        "next":["s3"]
     },

     {  
        "id":"s3",
        "type":"datasource.write.amazon.s3",
        "source":"internal",
        "params":{  
           "bucketName":"...",
           "accessKey":"...",
           "secretKey":"...",
           "objectKeyPrefix":"nextdigital/"
        }
     }

  ]

}
HTML
</div></div></div>

Use Cases

IdentitySync gives you the flexibility to use your data in any way you need. For example, with IdentitySync, the following scenarios are supported: 

Admin Activities

  • Retrieve all accounts that have remained unverified or unregistered for over a week (isVerified==false or isRegistered==false and created>'one week ago'), export the relevant email addresses to an ESP, from which to send follow-up emails.
  • As a sports club, regularly import accounts from an external ticketing system, thus fortifying your fanbase. 
  • Query the audit log to retrieve deleted users, and use a batch job to other external systems so that they can be deleted from there, too.

User Segmentation and Progressive Profiling

  • Set up data fields for segmenting users according to certain types of behavior in your site - such as Loyalty interactions, purchases or page visits (people who like and share content related to tabi socks, or have purchased said socks) then use an IdentitySync job to send only users that match these criteria to a marketing system for a targeted campaign (50% off in our summer sock sale). 
  • Use a Gigya-toGigya IdentitySync job to query users by Facebook likes stored in their profiles - for example, people who like vampire and zombie related content - and to plant a value (e.g. "horrorFic") in a Gigya data field. Then launch a gruesome Halloween marketing campaign targeting these users. 
  • Use an IdentitySync job to initialize default data to a Boolean field (e.g. set to null), and using a custom component that is activated according to this value, trigger a progressive profiling screen that requests more information from site visitors. 

Main Features 

For full, up-to-date details of the service's capabilities, see the Component Repository.

Main Supported Data Sources/TargetsSample TransformationsMain File Formats
  • Gigya Accounts
  • Gigya Data Store
  • FTP
  • SFTP
  • Amazon S3 cloud
  • Reordering, renaming, and removing fields
  • Replacing strings within field values using regex
  • Using JEXL expressions to create new fields based on the values of existing fields
  • Flattening objects (with some limitations)
  • Flattening an array field into a string field
  • PGP encryption and decryption (note that GPG is not supported)

Main file formats supported:

  • DSV
  • JSON
  • Salesforce, Mailchimp, Krux and other formats
  • GZIP, LZO


Anchor
api
api
Using IdentitySync

...