Gigya Job Openings


Skip to end of metadata
Go to start of metadata



Integrate Gigya's rich, permission-based other profile info with Selligent's data-driven, multi-channel marketing services.

The integration synchronizes user data between Gigya and Selligent on a recurring basis, including:

  • Creating and updating users in Selligent based on information from Gigya.
  • Updating user data in Gigya based on information from Selligent.

The integration uses IdentitySync, Gigya's ETL platform. Each direction of data transfer (from Gigya into Selligent, or from Selligent into Gigya) requires extracting data from the source platform, saving it as a file in a middle platform (such as SFTP, S3 or Azure Blob), and extracting the file from there into the target platform. This means that on Gigya's side, you should set up an outbound job that reads Gigya data and saves it to SFTP, and an inbound job that extracts a file from SFTP and writes the data to Gigya. In addition, you should set up the parallel data extract and file import  jobs on Selligent. 


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.

Setting up the Gigya- Selligent integration requires the following configuration information:



The following diagram shows the information flow. The flows with dotted lines mean that this is configured outside of Gigya. 

The transfers from Gigya to SFTP and from SFTP to Gigya are done using IdentitySync, Gigya's ETL platform. When creating a dataflow on Gigya's Console, you should choose the relevant "SFTP" integration as a template, and customize as needed. You can read more about those templates here: 

Additional points to consider: 

  • On the ESP, you should create a custom "Gigya UID" field, and sync Gigya's UID to that field. Gigya's UID should be used as the identifier to support the use case of a user changing their email address. When the UID is used rather than the email, that user will remain identified by the system after the change. 
  • Whether you are using a simple Gigya data field for describing the user's subscription status, or Communication Preferences, you should update the relevant subscription status (opt in or out) on the target platform. 

Compression Support

Gigya supports transmitting files in compressed format. By default files are not compressed, but you can set up gzip or LZO compression.