<style>.async-hide { opacity: 0 !important} </style>
<script>(function(a,s,y,n,c,h,i,d,e){s.className+=' '+y;h.start=1*new Date;
h.end=i=function(){s.className=s.className.replace(RegExp(' ?'+y),'')};
  (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
  ga('create', 'UA-8839817-1', 'auto');
  ga('require', 'GTM-MHMDDFM');
  ga('send', 'pageview');



IdentitySync is Gigya's robust ETL solution (Extract, Transform, Load) that offers an easy way to transfer data in bulk between platforms. 

With IdentitySync, you can:

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.

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

User Segmentation and Progressive Profiling

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
  • Other platforms, using the generic API writer
  • 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

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:

Components can be added to the dataflow, removed or changed as needed.

For detailed information, visit the Component Repository and see sample Dataflow Templates.

Dataflow Example

The following chart is a visualization of a dataflow in IdentitySync. This dataflow exports user accounts from Gigya to a partner platform (Krux).

Each step in the dataflow runs a separate component.


The above flow demonstrates a split dataflow. Dataflows are split using the next parameter. For more details, see Customize the Dataflow.

<a name="popup1-back"></a>
<p><a href="#popup1" rel="nofollow">

Click to view a sample JSON dataflow:

 		<div id="popup1" class="popup">
 		    <div class="popup-content-box">
 		        <a class="close" href="#popup1-back" rel="nofollow"></a>
 		        <div class="popup-content-box-inner">
  "name":"NextDigital Krux",

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




                 "expression":"gender eq 'm' ? 'male' : (gender eq 'f' ? 'female' : null)"
			"language": "jexl",







Using IdentitySync

Object Model


A dataflow is a complete definition for a transfer of information between Gigya and a third-party platform in a specific direction.

The dataflow includes all the necessary information about where the data is extracted from, which data is extracted, how the data is processed, and where the data is transmitted.

For details, see Dataflow Object. For samples, see Dataflow Templates


Steps are the building blocks of the dataflow. Each step is a call to a component that performs a specific task, such as extracting accounts from Gigya, or compressing a file in GZIP format. The step calls the component with specific parameters, and the output is passed on to the next step in the dataflow for further processing. For example, "datasource.read.gigya.account" is a component that searches the Gigya account database and returns all accounts that match specific parameters (an SQL-like search query). This component will typically be called in the first step in a dataflow that exports accounts from Gigya to a partner platform. Each step includes the following attributes: 

         "id":"dsv", // A name you assign to this step that serves as a unique identifier in this dataflow.
         "type":"file.parse.dsv", // The component run in this step.
         "params":{ // The parameters and values, expressions etc. used in this step.
         "next":[ // The next step to be run once this step completes.


For examples of end-to-end dataflows, see  Export from Gigya to SFTP and Import from SFTP to Gigya.

Data File Example

The following is an example of a data file in DSV format. The quotes around each field can be removed.


Handling Errors

IdentitySync includes a built-in capability for separating failed records and writing them to a file, so that they may be reviewed and handled, and fed back into the flow. 

Handling failed records is done by adding an additional step after a "writer" step, for writing to a separate file the records that did not complete the flow successfully. For detailed instructions, follow the implementation flow below (under Edit the Dataflow). For a code sample of a flow that writes failed records to SFTP, see the Component Repository


To create an integration based on IdentitySync, complete the following process:

<div class="flowdiagram">


Create Dataflow


Edit the Dataflow


Schedule the Dataflow


IdentitySync is a premium platform that requires separate activation. If it is not part of your site package please contact your Gigya or contact us by filling in a support form on our site. You can also access the support page by clicking "Support" on the upper menu of Gigya's site.



1. Create Data Flow

  1. Open IdentitySync Data Flows in Gigya's Console. Make sure your are signed in and have selected the relevant site. The IdentitySync dashboard may also be accessed by clicking Settings in the upper menu and then IdentitySync Data Flows in the left menu.

  2. In the dashboard, click Create Data Flow

  3. In the Create Data Flow window, select the data flow integration from the dropdown. If the flow you wish to create is not available in the dropdown, select any available flow: it is customized in the next steps. For more information, see Dataflow Templates.

  4. Select the data flow template: the direction of the flow, whether from or into Gigya. Note that at the bottom of this window, you can see an outline of the flow that will be created (e.g., Account > rename > dsv > gzip >sftp). 

  5. Click Continue. As a result, the IdentitySync Studio screen opens in the dashboard. 

2. Edit the Data Flow

The data flow you created is built of the required steps for data transfer between Gigya and the selected vendor. Use the Component Repository to understand the structure and parameters required in each step.

Using IdentitySync Studio, you can:

To do so: 

  1. If it's more convenient, you can work in full screen mode by clicking the full-screen toggle on the top rigt corner. 

  2. Double-click any of the steps to add or edit its parameters. Click OK when finished. 

  3. To add a new step, start typing its name in the Search component box. Drag the step from the list of components into the canvas.
  4. Drag arrows from/to the new step and from/to existing steps, to include it in the correct place in the flow. Make sure the "Success path" arrow is selected, under Connector Type
  5. To add a custom step, locate the record.evaluate step in the list of components and drag it to the canvas. 
  6. Double click the custom step to open a JavaScript editor. Click Test script to validate the code. For a full explanation of custom steps, see IdentitySync Custom Scripts

  7. To split the data flow (for example to write to two target platforms), add the relevant step (e.g. another "write" step) and draw arrows accordingly: 

  8. Handling failed records: You can add additional steps after a "writer" step, for writing to a separate file the records that did not complete the flow successfully. To do so: 
    1. Add the relevant components to the flow (for example, a file.format step to write the records to a file, and a writer to write the file to the relevant destination). 
    2. Under Connector Type, select the "Error path" connector. 
    3. Draw a connection from the original writer, to which successful records will be written, to the next step that handles failed records (e.g., the file.format step). 

    4. Under Connector Type, select the "Success path". 

    5. Connect the next steps that handle the failed records (e.g., the writer) using the "Successful path" connector. 

  9. Delete a step by selecting it and hitting the Delete button on your keyboard.
  10. If necessary, click Source to review the data flow code , and edit the code as needed. 
  11. Click Save

Your dashboard should now look something like this: 


The following actions are available: 

EditOpens the current data flow in IdentitySync Studio and change any of its attributes, steps and parameters.
Run TestRuns the data flow once on 10 records for test purposes. If the test was successful, after refreshing the dashboard, you will see the timestamp of the test run under Last Successful Run. Use the Status button to view the details of the run. See Job History  section on this page.

See Schedule the Dataflow.

DuplicateUseful for creating a new data flow based on a flow which has already been customized, if you wish to create a similar flow with slight variations.
StatusDisplays the status of the current jobs running in your IdentitySync configuration. See Job History section on this page.
DeleteDeletes this data flow.


3. Schedule the Dataflow

  1. Under Actions, click (schedule) to open the Scheduler. 
  2. Click Create Schedule
  3. Configure the schedule: 
  4. Click Create, and, once you are back in the Schedule dashboard, click the Refresh button. 
  5. The status of the scheduling is indicated in the Status column. 
  6. You can stop a job mid-run by clicking the Stop icon under Actions

  • The dashboard creates a Scheduling Object.
  • Last Successful Run corresponds with the lastRuntime parameter in the Dataflow Object
  • The Scheduled Next Run displays the newest date defined in the scheduler. Therefore, it's possible to see a past date here, if no more recent dates were configured.


Test and Monitor

Test Run

Test the data flow by clicking  (run test) under Actions. This creates an immediate one-time run for 10 records. If the run was successful, after refreshing the dashboard (with the Refresh button) you will see its timestamp under Last Successful Run.

Notification Email

When scheduling the dataflow, you can enter email addresses to which a success and/or failure notification will be sent. We recommend adding idx-failure-jobs@gigya-inc.com to the list of failure notification email addresses, so that Gigya will receive feedback of system health. 


Job History

You can monitor data flows by reviewing previous runs (jobs). The job history displays the status of each run, its start and end times, and the number of records for which the data flow was completed successfully (under Processed). 

Under Actions, click the Status button  to open the Job History screen.


For advanced monitoring and debugging, click the info icon for the relevant job under Details, and the Job Status Details screen opens.

Note the tabs that display the following detailed information: 

Copying Accounts From One Site to Another

IdentitySync gives you the option of copying the account database from one Gigya site to another, using the read from Gigya and write to Gigya components. When doing so:

    "name": "Copy accounts between 2 different sites",
    "steps": [
            "id": "account",
            "type": "datasource.read.gigya.account", // Read from source site
            "params": {
                "select": "UID,profile.email,profile.firstName,profile.lastName", // The Gigya fields to extract
                "batchSize": 300,
                "from": "accounts",
                "deltaField": "lastUpdatedTimestamp",
                "maxConcurrency": 1,
                "apiKey": "...", // The source site API key
                "userKey": "...", // The user key of the application created on the source site
                "secret": "..." // The secret key of the application created on the source site
            "next": [
            "id": "write",
            "type": "datasource.write.gigya.account", // Write to the target site
            "params": {
                "maxConnections": 10



IP Whitelisting

Depending on your networking policies, you may have to add the IPs of IdentitySync servers to a whitelist in order to allow IdentitySync to upload/pull information.

The full list of Gigya IPs are listed here. In addition, the following addresses are related to IdentitySync:

EU Data Center:


US Data Center:



AU Data Center:


CN Data Center:


RU Data Center


IdentitySync is an ETL solution - Extract, Transform, Load- that offers an easy, API-based way to transfer user information in bulk between Gigya and a third-party platform.