Gigya Job Openings


Skip to end of metadata
Go to start of metadata



Gigya’s integration with Salesforce offers easy and efficient introduction of Gigya's rich, permission-based social data and other profile info into Salesforce’s customer management platform.

The integration that synchronizes user data between Gigya and Salesforce uses IdentitySync, Gigya's platform for extracting, transforming and loading data between platforms. The integration can run on a recurring basis (daily) or ad-hoc, and is used for creating and updating users in Salesforce based on information from Gigya.


  • This integration supports Salesforce Enterprise Edition and above.
  • The Salesforce account has to have the Bulk API option enabled.
  • In order to synchronize Gigya accounts into Salesforce "person account" objects, the person account feature has to be enabled (by default it's disabled).

Security notes:

  • Data transferred from Gigya to Salesforce is encrypted and transferred via HTTPS POST.
  • User permissions: All the data that is synchronized using this integration will be viewable by anyone who has access to your Gigya account. There is no way to set restrictions or permissions for specific fields for specific users. Therefore, you should only synchronize data fields that are accessible to all your users in Salesforce.


The integration with Salesforce requires some setup on Salesforce, and setting up a job on Gigya's Identitysync.

Salesforce Setup

In order to begin setting up your integration, perform the following steps:

  1. Decide which object type(s) should be synchronized with - leads, contacts or person accounts.
  2. Create a new Salesforce user with Bulk API permissions and give the credentials to Gigya (this is the best practice for this integration). Note: You will need to notify Gigya whenever this user's password changes, otherwise the integration will stop working.
  3. Receive a Salesforce token and pass on to Gigya (see instructions below).

  4. Configure your Salesforce fields (see instructions below).
  5. Check which Salesforce endpoint the integration should use. Note that there may be different endpoints for production and testing environments.

Receiving a Salesforce Token

To receive your Salesforce token:

  • In Salesforce, in the top menu bar, click your name and select "My Settings".
  • Select “Personal” > “Reset Security Token”.
  • The token will be sent by email.

Click to enlarge screenshot

Configuring Salesforce Fields

Creating the Gigya_UID Custom Field


Click “Setup” in the top bar. To add the “Gigya_UID” field to Lead, Contact, and Person Account objects:

  • Select “Customize” in the left sidebar
  • Select an object type. In this example we select “Leads”.
Click to enlarge screenshot


Under “Leads”, select “Fields”, and in the “Custom Fields & Relationships” pane, click “New”

Click to enlarge screenshot


In the “New Custom Field” page, select the field type “Text” and click the “Next” button.

Click to enlarge screenshot


Define the “Gigya_UID” field:

  • Label and name are “Gigya_UID”, Text length - 255

  • Check the "External ID" checkbox; don't check the “Set this field as the unique record identifier” checkbox

  • To finish, click “Save”.


Click to enlarge screenshot

5. The new custom field is added to the custom fields pane.

Note that “API Name” has “__c” added to the end of the field label you specified. This is the name to use when mapping the field to Gigya.

Click to enlarge screenshot

(OPTIONAL) Mapping Lead Custom Field to Contact Custom Field

After adding the Gigya_UID field, you may want to create the following internal mapping if:

  • You are working with both Leads and Contacts in this integration with Gigya
  • And you want the system to recognize a lead and a contact as the same identity if they have the same Gigya UID.

To create the mapping:

In the “Custom Fields & Relationships” pane
(under “Setup” > “Customize” > “Leads” > “Fields”),
select “Map Lead Fields”.
Click to enlarge screenshot
Map the “Gigya_UID” field to the
“Contact Gigya_UID” field as seen below,
and click “Save”.
Click to enlarge screenshot

There are other options for dealing with Leads and Contacts that may share the same Gigya identity, e.g. you may convert leads to contacts.

Creating an Email Field for Person Accounts

If the Person Account object does not have an Email field define, you need to create it and set it as an external ID.

The process is similar to the process of creating the Gigya_UID field:

  • Go to “Setup” > “Customize” > “Accounts” > “Fields”.

  • In the “Accounts Custom Fields & Relationships” pane, click “New”.

  • Select the field type “Email”.

  • Give the field a name, a label and a description.

  • Select the “Set this field as the unique record identifier from an external system” checkbox.

  • Click “Save”.

To find the field name to use when mapping to Gigya:

  • If it's a native Salesforce field, go to "Setup" > "Customize" > "Leads" or "Contacts" > "Fields" and look under "Field Name".
  • If it's a custom field, go to "Setup" > "Customize" > "Leads" or "Contacts" > "Fields" and look under "API Name".


IdentitySync Setup

We recommend that you read through the IdentitySync guide, to familiarize yourself with this tool. 

Set up a job on IdentitySync, using the Salesforce template and the datasource.write.salesforce step to write data to Salesforce.