Gigya Job Openings

Adobe Campaign

Skip to end of metadata
Go to start of metadata

 

Overview

Gigya’s integration with Adobe Campaign is based on IdentitySync, our ETL platform. It combines Gigya's rich, permission-based social and other profile info with Adobe Campaign cross-channel personalized marketing.

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

  • Creating and updating users in Adobe Campaign based on information from Gigya.
  • Updating users in Gigya based on new information from Adobe Campaign.
  • Extracting segments using filter criteria.
  • For more information on integrating with Adobe Campaign, contact your Gigya Project Manager. You should prepare in advance the details of the social and site data you want to synchronize between Gigya and Adobe Campaign.
  • Integration with Adobe Campaign is a premium service requiring activation. For more information, please contact your Gigya account manager or enter a support request on our site.
  • Due to limitations of Adobe Campaign, the integration supports transmitting 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.

 

Configuration Parameters

Please create a test site in the Gigya admin console for integration testing (don't use your production site) and use a test list on the target integration platform. We are able to put integrations in "sample mode" for testing, which will restrict audiences to 10 sample accounts.

Setting up the Gigya-Adobe integration requires the following configuration information:

Guidelines

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. 

Parameters for FTP Configuration

RequiredNameTypeDescription
fileNamePrefixstringThe outbound file name prefix created is {fileNamePrefix}{fileNameDateFormat}. We recommend indicating the company name in {fileNamePrefix}.
fileNameSuffixstringThe suffix should include the extension of the created outbound file. (e.g. ".csv", ".txt").
fileNameDateFormatstring

Format for the filename timestamp. This should be in one of the simple date formats.

Default: yyyyMMdd_HHmm

For example, if we transfer a .csv file to a company called "ACME Inc." on March 22, 2015 at 11:15pm, the file may be named acme_20150322_1115.csv.

Date-only formats (such as YYMMDD - without Time) are permitted, but in that case, if the file is transferred more than once a day, it will have the same name each time, and may overwrite a previously transferred file.

fileDelimitercharCharacter used to distinguish columns in the CS file. Supported values are comma (","), semicolon (";"), pipe ("|") and tab ("\t").
outbound.compressstring

Determines whether compression is used, and if so, specifies a format. Permitted values are:

  • "gzip" - Use gzip compression.
  • "lzo" - Use lzo compression.
  • "none" - Do not use compression.
esp.storage.protocolstring"SFTP" or "FTPS".
esp.storage.serverstringIP of the destination server.
esp.storage.portstring Port on the destination server.
esp.storage.userstringFile storage account user name.
esp.storage.passstringFile storage account password.
esp.storage.keystringIf 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.
esp.storage.phrasestringIF SFTP is used, a pass phrase can be set for additional security. This is the passphrase.
outbound.completePopulationFolderNamestringName of the folder to populate the full data import on the outbound server.
outbound.deltaPopulationFolderNamestringName of the folder to populate the data updates on the outbound server.

Parameter for Data Filtering

RequiredNameTypeDescription
ae.filterClausestringAn SQL-like query specifying the data to retrieve from Gigya on outbound data transfers. Refer to the filter criteria in the Identity Query Tool.

Parameters for Inbound Data Transfers 

RequiredNameTypeDescription
inboundFilePatternstringGigya will search for files with a prefix, sorted by date: "Prefix*.extension".
esp.sync.unsubscribed.hourStringThe time of day to retrieve unsubscribe actions in the format of HH:MM. Time is set in 10 min. intervals. (e.g 20:10)

 

Supporting JSON Files

Some Gigya data is in the form of JSON files. If your platform does not support JSON file formats, Gigya can transform the data to a flat format during data export. 

Compression Support

Gigya supports transmitting files in compressed format.

By default files are not compressed, however you can configure gzip or LZO compression.