Gigya Job Openings


Skip to end of metadata
Go to start of metadata


This integration is currently under construction. For our integration with the Selligent product, see Selligent. For more information, please contact us at



Gigya’s integration with StrongView combines Gigya's rich, permission-based social and other profile info with StrongView's automated digital marketing.

Integration with StrongView requires no implementation by the customer. Just contact your Gigya Implementation Consultant and we will handle the details. You can specify exactly which social and site data you want Gigya to synchronize.

The integration synchronizes user data between Gigya and StrongView on a recurring basis (daily) or ad-hoc, including:

  • Creating and updating users in StrongView based on information from Gigya.
  • Updating user data in Gigya based on information from StrongView.
  • Extracting segments using filter criteria.
  • Integration is by transferring single value Gigya user account fields such as name, age, address or email. Field names are matched with corresponding fields on the target system. Gigya account fields which hold complex multi-value object data such as user photos' URLs or Facebook likes cannot be integrated using this method.

Gigya's integration with StrongView supports 'On-Premise' implementations as well as cloud based implementations, provided that the customer provides Gigya with FTP account access. The StrongView file digest may by defined by the customer, or by permission, by the Gigya Implementation Consultant on the customer's behalf.

For more details, please contact your Gigya Implementation Consultant.

Integration with StrongView is a premium service requiring activation. For more information, please contact your Gigya Customer Engagement Executive or enter a support request on our site.

Configuration Parameters

Setting up the Gigya-StrongView 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. 


Configuring the Integration with Gigya

To configure the integration with Gigya on the StrongView UI, execute the following steps:

  1. Define an internal data source

  2. Configure the sync file and frequency

Defining an Internal Data Source

  1. Under Data Management select Data Sources | Internal
    Click to enlarge screenshot


  2. Click "Create" to create a new data source. Give your new data source a name, a description (optional) and specify the type of campaign. In the example below the data source called GigyaDS will be used for a Newsletter campaign.

    Click to enlarge screenshot

    Click Next to continue to the next step.


  3. In this step you will specify how you are going to define your data structure. Select By Importing File.
    Click to enlarge screenshot

    Click Next to continue to the next step.


  4. In the Import Database step you will import a file that specifies. You can either select Upload File and then select the corresponding file to import, or select Paste and just paste the file contents in the field provided.

    Since the file created by Gigya contains a header row, set First Line Contains Field Names to Yes.

    Set Field Dlimiter to Comma (CSV).

    Click to enlarge screenshot

    Click Next to continue to the next step.


  5. Choose the fields that should be imported. Make sure to specify the email field as an Email Address data type, and set the gigya_uid as the primary key.

    Click to enlarge screenshot

    Click Save to complete defining the data source. Any records present in Import Database step will be loaded into the database. Your new data source should now be displayed in the list.

    Click to enlarge screenshot

Configuring the Synchronization

To configure the new data source, select it in the list and click Edit in the top menubar.

When your data source information is displayed, click Next at the bottom of the screen to display Recurring Imports.

To define a new import schedule, click Add Import.

Click to enlarge screenshot

The field settings should be as follows:

FieldSet to

Import type

FTP - Your files will be synched by FTP.

File name prefix

This should match the fileNamePrefix parameter in the properties file ().

File name suffix

This should match the fileNameSuffix parameter in the properties file ().

Import mode

Set this according to your preference. Usually this should be Merge.

Field Delimiter

Comma (CSV). This is the format of the data file that is synched.

Click Next to set the import schedule.

Be sure to coordinate with the Gigya Implementation Consultant so that you run the import after the file has been updated.

Click to enlarge screenshot

Click Add to complete your schedule configuration. You should see your new import definition.

Click to enlarge screenshot

Finally, click Save at the bottom of the screen to save your new data source and its recurring import schedule.