Salesforce Marketing Cloud

Skip to end of metadata
Go to start of metadata

 

Overview

Gigya’s integration with Salesforce Marketing Cloud (formerly ExactTarget) enables seamless integration of Gigya's rich social info with SFMC's cloud-based email, mobile and social marketing services, in order to target accurately users in marketing campaigns and newsletters.

The integration uses the Salesforce Marketing Cloud Data Extensions, which hold the contact information for Contact Builder, which is, in turn the foundation for the Marketing Cloud's Journey Builder.

The Salesforce Marketing Cloud integration requires no implementation on the client side, other than opening and configuring a Marketing Cloud account. To connect with Marketing Cloud, just contact your Gigya Implementation Consultant.

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

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

You can specify exactly which social and site data you want Gigya to synchronize. Gigya can both pass and receive subscribe and unsubscribe information from users who opt out of marketing in their social account or who press unsubscribe links in Marketing Cloud marketing media.

 

Note:

Configuration

For a complete integration between Gigya and Salesforce Marketing Cloud, you need to:

  1. Create an app to enable Gigya to connect to SFMC
  2. Configure the data transfer from Gigya to SFMC
  3. Configure the data transfer from SFMC to Gigya (Optional)

Finally, see the Parameters Summary for all the parameters you need to provide to the Gigya team.

(I) Creating an App

In order for Gigya to access Marketing Cloud systems, you need to create an app through which Gigya will connect. Once you create the app, Marketing Cloud generates a clientID and clientSecret which are needed by Gigya in order to be able to transfer data from Gigya to Marketing Cloud. You need to provide these parameters to your Gigya Implementation Consultant.

In order to create an Marketing Cloud application, open an account at the Marketing Cloud App Center. In the App Center Overview screen, click Create New App to start the wizard that will create the app, and then select an API Integration app.

  • Specify a Name, Description and Package name for your app.
  • Click Next.
    Click to enlarge screenshot
  • Choose a Production or Sandbox account.
    Click to enlarge screenshot
  • Click Link to Account. Marketing Cloud will display the account to be linked.
    Click to enlarge screenshot
  • Click Integrate.
  • Now you need to define the data access privileges you want Gigya to have through your app. For this integration, you need to enable Read and Write access for Data Extensions.
    Click to enlarge screenshot
  • Click Next.
  • The summary screen displays all your settings for the app. Click Finish to create the app.

Once the app is created, Marketing Cloud displays a summary showing your clientID and clientSecret values which you need to provide to your Gigya Implementation Consultant

Click to enlarge screenshot

Parameters to Provide to Gigya

When you have completed defining your app, make a note of the following parameters which you need to provide your Gigya Implementation Consultant:

  • Client ID
  • Client Secret

(II) Configuring the Data Transfer from Gigya to SFMC

Gigya transfers information to Salesforce Marketing Cloud by creating a file with the Gigya data and sending it to SFMC by FTP. Then you call an API that invokes the Salesforce Marketing Cloud import activity to read the file and ingest the data into Salesforce Data Extensions. The Salesforce import activity configuration includes specifying the exact file that it should look for in order to ingest the data.

To start configuring the transfer, login to Marketing Cloud and select Email.

 

From the Email module, you need to execute the following steps:

 

1.

Define Data Extensions to hold data from Gigya

2.

Define an Import Activity for each Data Extension

3.

If you have Gigya Signals, you can repeat step 2 for transferring signal data

4.

If you have Game Mechanics (Loyalty), you can repeat step 2 for GM data

5.

Test your configuration

 

Defining Data Extensions

Data Extensions are database tables that hold the data transferred to your Marketing Cloud account from Gigya.

You need to define a separate Data Extension for each Gigya object for which you want to receive data. At a minimum, you need to define a Data Extension to hold Gigya subscriber data. Depending on additional data you may want to transfer from Gigya, you may also define additional Data Extensions for Facebook Likes, Facebook Favorites, Gigya Phones or any other data that is available in the Gigya Profile object.

In order to get a complete listing of Gigya Data Object and Gigya Profile Object fields in your Gigya account, you can use the accounts.getSchema API method.

Note that for a Data Extension that receives data that is inherently "flat" (e.g. strings), the Primary Key for a table should be the Gigya GID (as in the Data Extension defined for GigyaSubscribers below).

However, if a Data Extension is defined to receive an array value (i.e., phones, publications, patents, certifications, skills, education, work, favorites and likes), the Primary Key should be defined as a separate and unique "key" field since array profile objects are "flattened' in order be passed as a table, and therefore, there may be several data items with the same GID (e.g., if a user has received several "likes", there will be several "like" records with his GID). See the example below for GigyaFBLikes.

To create a Data Extension in the Email module:

  1. From the menu, select Subscribers > Data Extensions.
  2. Select Create.
  3. The Data Extension for Gigya Subscribers should be configured as follows:
    • Name: Provide a name for this Data Extension (e.g., GigyaSubscribers)
    • External Key: Specify an external key. We strongly recommend giving the External Key the same value as the Name field since this value is used by your Gigya Implementation Consultant when configuring the transfer on Gigya's side.
    • Fields: Make sure you define all fields as Nullable except for the field used as the primary key.

      Important: SFMC only supports data-type text. Make sure to define all the fields with data type = text. All fields from Gigya will be only sent as strings.

      Click to enlarge screenshot


      NameData TypeLengthPrimary KeyNullable
      GIDText50Yes 
      firstNameText100YesYes
      lastNameText100YesYes
      profileURLText300YesYes
      usernameText50YesYes
      emailText254YesYes
      cityText100YesYes
      zipText50YesYes
      Newsletter ATextYesFalseYes
      Newsletter BTextYesFalseYes
  4. Click Save to save this Data Extension.

In a similar fashion create any other Data Extensions you need. For example, to create a Data Extension for Facebook likes, use the following settings:

  • Name: Provide a name for this Data Extension (e.g., GigyaFBLikes)
  • External Key: Specify an external key. We strongly recommend giving the External Key the same value as the Name field since this value is used by your Gigya Implementation Consultant when configuring the transfer on Gigya's side.
  • Fields: Make sure you define all fields as Nullable except for the field used as the primary key.

    Important: Make sure to define all the fields with data type = text. All fields from Gigya will be sent as strings.

 

NameData TypeLengthPrimary KeyNullableDefault Value
keyText50Yes  
GIDText50 Yes 
categoryText50 Yes 
nameText200 Yes 
timeText  YesCurrent date

When transferring Facebook likes from Gigya to Marketing Cloud the email notification sent may indicate Duplicate Keys. You may ignore this because, in the case of duplicate keys in the transferred file, only one of the keys is loaded to your Data Extension.

For more details on how to define a Data Extension, see the Salesforce Marketing Cloud Documentation.

Once you have defined all of your Data Extensions, you will need to provide your Gigya Implementation Consultant with the mapping from Gigya fields to the corresponding fields in your Data Extension (e.g., Gigya firstName field is mapped to your "Name" field).

Defining Import Activities

The Import Activities govern when and how data from Gigya is imported into Data Extensions that were defined.

You need to define an Import Activity for each Data Extension separately. At a minimum, you will need an Import Activity for the data extension you created for Gigya subscriber data. If you are importing additional data such as Facebook likes, Facebook favorites etc., you will need to define a separate Import Activity for each of those types.

To define an Import Activity in the Email module, from the menu, select Interactions | Import, and then select Create.

Click to enlarge screenshotClick to enlarge screenshot

 

Fill in the fields as follows:

 

FieldDescription
NameThe same name used for the corresponding Data Extension
External KeyThe same as Name

Description (optional)

Free form description of this import
File locationEnhanced FTP
File Naming Pattern{fileNamePrefix}{flatJsonFileName}%%Year%%%%Month%%%%Day%%{fileNameSuffix}

where:

fileNamePrefix: same name as in the Gigya file configuration and export file type. For example, for likes: {fileNamePrefix}=etImportlikes.

flatJsonFileName: If data being imported is for files that have been flattened to JSON format, then this should be the flattened JSON file name (e.g., likes). For Gigya subscriber data, this component of the file naming pattern should just be contacts.

fileNameSuffix:  the file name suffix including the dot (e.g., .csv)

These should be coordinated with your Gigya Implementation Consultant.

File TypeComma Delimited (CSV)
Destination TypeSelect Data Extensions and then select the corresponding Data Extension that should receive the data from this import activity.
Update TypeFill in the settings according to your preference
File MappingMap using column headings
Import Completion SettingsCheck Send notification email to and fill in the email that should receive notifications about this import activity.

 

For more details see Import Activity in the Salesforce Marketing Cloud documentation.

Testing Your Configuration

Once you have completed your configuration (i.e., created your App, defined the appropriate Data Extensions and corresponding Import Activities), and your Gigya Implementation Consultant has completed the configuration on Gigya's side, we strongly recommend coordinating with your Gigya Implementation Consultant to test your configuration.

When running tests, data is loaded into the Data Extensions you have defined. Be sure to delete any test data once testing is complete and you are ready to receive real data.

To test your configuration, execute the following steps:

  1. In the Email module view your list of Data Extensions by selecting Subscribers | Data Extensions. All the Data extensions you have defined should be displayed in a list.
  2. Set the checkbox next to the GigyaSubscribers Data Extension and then select the Clear  Data button to make sure the Data Extension does not contain any data (the Last Import Time field should now be blank).
    Click to enlarge screenshot

  3. Ask your Gigya Implementation Consultant to transfer data from Gigya.

  4. Once the transfer is complete, an email notification should be sent to the email address you specified in the Import Completion Settings of your Import Activity. The Last Import Time  field should also be updated accordingly.

  5. To verify that data was transferred, in your list of Data Extensions, check GigyaSubscribers and now select the View Data button to view the data that was transferred. Your data should look as below:

Click to enlarge screenshot

Note that when viewing your data, only the first 200 records are displayed

In a similar way, you can test data transfer for any other Data Extensions you have created.

Parameters to Provide to Gigya

When you have completed configuring transferring data from Gigya to Salesforce Marketing Cloud, make a note of the following parameters which you need to provide your Gigya Implementation Consultant:

Date Extensions:

  • External Key of each Data Extension you want to synch from Gigya
  • Field Mapping from Gigya object fields to corresponding fields for each Data Extension

Import Activities: The File Naming Pattern specified for each import activity, including 

  • fileNamePrefix
  • flatJsonFileName
  • fileNameSuffix

(III) Configuring the Data Transfer from SFMC to Gigya

This step is optional and should only be followed if you need to transfer data from your own Data Extensions back to Gigya.

For inbound user synchronization, the integration with Gigya can only update data for users already existing in Gigya's database. New users are not created.

Transferring data from Salesforce Marketing Cloud to Gigya is based on a Data Extract activity. You use data filters to specify the data that should be extracted from Salesforce, and then set up an export to extract that data to a file. Then, Gigya's Data Extract process runs according to timed intervals and looks for the corresponding file (as specified in Gigya's configuration file) to import. It is important to give the Salesforce Data Extract activity enough time to complete before Gigya's process looks for the data file. Therefore, you need to coordinate with your Gigya Implementation Consultant, that Gigya's Data Extract will always be invoked 30 minutes after Salesforce Data Extract activity.

To configure the transfer of data from Marketing Cloud back to Gigya, you need to execute the following steps:

  1. Define a Data Filter to filter out records that should not be transferred.
  2. Define a Filter to hold those records that were extracted from the Data Extension according to your Data Filter.
  3. Configure Data Extract to define how data should be extracted from the Data Extensions
  4. Configure File Transfer that governs when and how the data should be transferred to Gigya
  5. Define a Program to automate the transfer of data

Defining Data Filters

Data filters give you control over which records should be extracted from your Data Extensions for transfer to Gigya.

Through the flexible UI, you can define any complex conditions to filter your data.

In the Marketing Cloud Email module, from the menu, select Subscribers | Data Filters and click Create to define a new Data Filter.

Click to enlarge screenshot

 

FieldDescription
NameProvide a name for this Data Filter
External KeyThe same as Name
Description (optional)Free form description of this Data Filter
Data SourceData Extensions
Data ExtensionSelect the Data Extension you want to filter.
Outer GroupingWithin the Outer Grouping, you may click on /Add Condition and Add Grouping to specify any filtering condition on the specified Data Extension.

 

Marketing Cloud will display the filter text that results from your configuration.

Defining a Filter 

Defining a filter creates a new temporary Data Extension to hold the records that pass through your defined filter before transferring them to Gigya.

To create a new Filter Activity, from the menu select Interactions | Filter, and then select Create.

Click to enlarge screenshot

 

FieldDescription
NameProvide a name for this Filter
External KeyThe same as Name
Description (optional)Free form description of this Filter
Filter DefinitionClick Select... to select the filter that you want to apply (this should be the filter you defined in the previous Defining Data Filters step)
Result Data Extension NameProvide a name for the resulting Data Extension after the filter is applied
Result Data Extension External KeyThe same as Result Data Extension Name.
Result Data Extension External KeyFree form description of the resulting Data Extension

 

To save your Filter, click Save.

Once your Filter is saved, select it and click Start to create the new Data Extension with the filtered records.

Configuring Data Extract

The Data Extract specifies the parameters needed for Marketing Cloud to pass data to Gigya.

Login to in the Marketing Cloud Email module, and from the menu, select Interactions | Data Extract.

To create a new Data Extract Activity select Create.

Click to enlarge screenshot

Fill in the fields as follows:

 

FieldDescription
NameProvide a name. We recommend using the same name used for the corresponding Data Extension
External KeyThe same as Name
Description (optional)Free form description of this Data Extract
File Naming Pattern

{fileNamePrefix}{flatJsonFileName}%%Year%%%%Month%%%%Day%%{fileNameSuffix}

where:

fileNamePrefix: same name as in the Gigya file configuration and export file type. For example, for likes: {fileNamePrefix}=etImportlikes.

flatJsonFileName: If data being imported is for files that have been flattened to JSON format, then this should be the flattened JSON file name (e.g., likes). For Gigya subscriber data, this component of the file naming pattern should just be contacts.

fileNameSuffix: the file name suffix including the dot (e.g., .csv)

These should be coordinated with your Gigya Implementation Consultant.

Extract TypeData Extension Extract
Column Delimiter, (This should be the same delimiter that Gigya uses which is a comma)
DE Customer KeyThis should be the same name as the corresponding Result Data Extension Name you defined in the previous step.
HasColumnHeadersCheck
TextQualifiedCheck
UsesLineFeedCheck

 

Click Save to save your configuration.

Configuring File Transfer

The file transfer configuration configures how and when the data extracted from the Data Extension is transferred to Gigya.

From the Marketing Cloud Email module, from the menu, select Interactions | File Transfer.

To define a new File Transfer configuration click Create and fill in the fields as below:

Click to enlarge screenshot

Your File Transfer configuration:

 

FieldDescription
NameProvide a name for this file transfer configuration
External KeyThe same as Name
Description (optional)Free form description of this file transfer configuration
File LocationEnhanced FTP
File Naming Pattern

{fileNamePrefix}{flatJsonFileName}%%Year%%%%Month%%%%Day%%{fileNameSuffix}

where:

  • fileNamePrefix: same name as in the Gigya file configuration and export file type. For example, for likes: {fileNamePrefix}=etImportlikes.
  • flatJsonFileName: If data being imported is for files that have been flattened to JSON format, then this should be the flattened JSON file name (e.g., likes). For Gigya subscriber data, this component of the file naming pattern should just be contacts.
  • fileNameSuffix: the file name suffix including the dot (e.g., .csv)

These should be coordinated with your Gigya Implementation Consultant.

Be sure to use the same File Naming Pattern that you used in the Data Extract configuration.

Defining a Program to Automate Data Transfer

You can define a program to automatically perform Data Extract and File Transfer according to any schedule or on demand.

To define a newProgram, in the Marketing Cloud Email module, from the menu, select Interactions | Programs and then click Create.

Click to enlarge screenshot

Fill in the fields as follows:

 

FieldDescription
NameFill in a name for the programs
External KeyThe same as  Name
Description (optional)Free form description of this import
Status Notificationcheck
Notification Email Address(es)Fill in the email addresses that should be notified when this program runs

 

Create a new process by selecting Edit Process.

  • Your process should contain three steps, each with a single task.
  • The first step should contain the Filter Activity you defined. This updates the filtered data whenever the Data Extension is updated.
  • The second step should contain your Data Extract activity.
  • The third step should contain the corresponding File Transfer activity.
    Once your steps are defined click Save.
    Click to enlarge screenshot
  • Create a Schedule by selecting Edit Schedule.
    You should schedule your program should run at least 30 minutes before Gigya's system is timed to receive the file and extract its data. This should be coordinated with your Gigya Implementation Consultant.

For example, a program to run the noNewsletter Filter, Data Extract and File Transfer activities used on this page, should look as below:

Click to enlarge screenshot

To test your program, you can run in manually by clicking Start.

Parameters to Provide to Gigya

When you have completed configuring transferring data from Marketing Cloud back to Gigya, make a note of the following parameters which you need to provide your Gigya Implementation Consultant:

  • DataThe File Naming Pattern for each Data Extract defined.
  • File Transfer: The File Naming Pattern for each File Transfer defined. This should be the same as the one defined for the Data Extract.
  • Program:
    • Program schedule - this should run at least 30 minutes before Gigya's system is timed to receive the file and extract its data as specified in Gigya's esp.update.hour internal configuration parameter.
    • Field Mapping from Gigya object fields to corresponding fields for each Data Extension.

Parameters Summary

This section provides a summary of all the parameters you need to provide your Gigya Implementation Consultant in order to complete your integration with Gigya.

StepParameters to provideNotes
General
 Email for notificationsProvide your Gigya Implementation Consultant an email address that should receive notifications following data transfer between Gigya and your systems.
FTP settingsesp.storage.protocol"SFTP" or "FTPS"
esp.storage.serverIP of the destination server
esp.storage.userFile storage account user name
esp.storage.passFile storage account password
esp.storage.portPort on the destination server
esp.storage.key(Optional)  If a value is entered, this field is used instead of the SFTP password, otherwise the SFTP password will be used.
The key should be in OpenSSH format. For more information see  http://www.ietf.org/rfc/rfc4716.txt .
Creating an App
 clientIDDisplayed when you complete the process of defining the app.
clientSecretDisplayed when you complete the process of defining the app.
Transferring data from Gigya to SFMC
Defining Data ExtensionsExternal Key For each Data Extension you want to synch from Gigya.
Field mappingFor each Data Extension you have defined. This specifies how to map Gigya object fields to fields you have defined in your Data Extension
Defining Import ActivitiesFile Naming PatternSpecified for each Import Activity defined.
(Optional) Transferring data from SFMC back to Gigya
Configuring Data ExtractFile Naming PatternSpecified for each Data Extract defined.
Configuring File TransferFile Naming PatternSpecified for each File Transfer defined. This should be the same as File Naming Pattern defined for Data Extract
Program to Automate Data TransferProgram scheduleCoordinate with your Gigya Implementation Consultant that this should run at least 30 minutes before Gigya's system is timed to receive the file and extract its data
 

IdentitySync Integration

If you are using IdentitySync, you can set up dataflows to export identity data from Gigya to Silverpop. For a sample dataflow, see Salesforce Marketing Cloud - Exacttarget Dataflow - Outbound.

Save

Save

Save

Save

Save

Save

Save

Save

Save

Save

Save