Gigya Job Openings


Skip to end of metadata
Go to start of metadata


Gigya’s integration with Eloqua is based on IdentitySync, our ETL service. The Eloqua integration allows you to integrate your Gigya user data with Oracle's Eloqua marketing service. Bulk data transfers are used to sync between the platforms. Synchronization is performed in two separate jobs - one transfers information from Gigya to Eloqua, creating and updating users as needed, and the other transfers information from Eloqua to Gigya, updating existing users (the integration cannot create new users in Gigya). The integration is based on passing a CSV file to an SFTP platform, and loading it into each platform with a dedicated job. For an example data flow that passes a CSV file, see Export from Gigya to SFTP

See examples:

Inbound flows update existing users on the Gigya database. If your implementation allows the creation of new users on the ESP regardless of whether they exist on Gigya, you should contact your Customer Engagement Executive to assist in supporting this.

Eloqua Configuration

 Work with your Eloqua account team to ensure that the Eloqua integration is defined correctlyYour customer support team can test that data transfers successfully from Gigya to Eloqua and vice versa. 

Adding the Gigya ID field to the contact fields  

Transfers of data from Eloqua to Gigya are faster and more effective if contact data stored by Eloqua includes the Gigya user ID.

  1. Click the "Settings" button at the top of the window and then select "Setup", this opens the "Application Setup" page.
  2. In the "Database" row, select "Fields and Views".

  3. Click the plus button at the bottom of the window and select "Add Contact Field".

  4. Add the "Gigya UID" field (see below) and click the "Save" button.  The "Save" action automatically generates a field in the Eloqua contacts database  and after the Save action the field's "Database name" will appear. Thus the database name for the Gigya UID will be (in the example shown below), "C_Gigya_UID1", although the Display Name shows Gigya UID.  You will need to know the field's database name for mapping with Gigya.

Gigya Configuration


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. 

Example of Eloqua data after integration