Gigya Job Openings

CheetahMail

Skip to end of metadata
Go to start of metadata

 

Overview

Gigya’s integration with CheetahMail combines Gigya's rich, permission-based social and other profile info with CheetahMail's enterprise email marketing service solutions. 

The integration synchronizes user data between Gigya and CheetahMail on a recurring basis, including:

  • Creating and updating users in CheetahMail based on information from Gigya.
  • Updating user data in Gigya based on information from CheetahMail.
  • Extracting segments using filter criteria.

The integration uses IdentitySync, Gigya's ETL platform. Each direction of data transfer (from Gigya into CheetahMail, or from CheetahMail into Gigya) requires extracting data from the source platform, saving it as a file in a middle platform (such as SFTP, S3 or Azure Blob), and extracting the file from there into the target platform. This means that on Gigya's side, you should set up an outbound job that reads Gigya data and saves it to SFTP, and an inbound job that extracts a file from SFTP and writes the data to Gigya. In addition, you should set up the parallel data extract and file import  jobs on CheetahMail. 

In this  guide, we will refer to SFTP as the example, but it could mean Amazon S3 or Azure Blob for your implementation.

Implementation

Setting up a Gigya-Cheetah mail 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. 


Inbound flows update existing users on the Gigya database. If your implementation allows the creation of new users on the ESP regardless of whether they exist on Gigya, you should contact your Customer Engagement Executive to assist in supporting this.