Gigya Job Openings

Silverpop

Skip to end of metadata
Go to start of metadata

 

Overview

Gigya’s integration with Silverpop combines Gigya's rich identity data with Silverpop's automated digital marketing in order to target users more accurately in marketing campaigns and newsletters. Account data and subscription information, including opt-ins and opt-outs, is synchronized between Gigya and Silverpop on a recurring basis (daily batch transfers) or on demand, using IdentitySync, Gigya's ETL service. 

Implementation

The integration is based on inbound and outbound IdentitySync data flows. There are two implementation options:

Option 1: Sync to the Email Status Field

Sync users' subscription status (opted in/out) to the default status field in Silverpop. This is the recommended best practice.   

 

The benefits of this option include: 

  • Keep a clear 1:1 relationship between Gigya and Silverpop lists
  • Ability to support Silverpop's global logout

Click here for an explanation of the Gigya-to-Silverpop dataflow and a code template.  In this option, you will be using the newsletterField parameter of the datasource.write.silverpop IdentitySync component. 

 

Option 2: Sync to a Custom Field

The second option is to have more than one newsletter (i.e., a smart list) in a list. In this option, you add a custom Boolean field to the Silverpop list to which the Gigya subscription status is synced. 

In this scenario, the email status field should be mapped to one main newsletter, and the other newsletters will be mapped to the custom field and have a dependency to the email status. 

Information to Prepare

Before setting up the flows, you should prepare certain information.

  • Your Engage pod number. For example, if you access engage5.silverpop.com, 5 is the pod number.
  • OAuth application details:

    • Client ID
    • Client Secret
    • Refresh token
  • The ID of the Silverpop list you want to synchronize with Gigya. 

    A unique identifier should be assigned in Silverpop to the list.

    If no such identifier is set, you should initiate the sync_fields parameter in your IdentitySync integration to indicate the unique IDs of the rows being transferred.

  • Decide which profile information should be synced into Silverpop, e.g., first name, phone number. 

Silverpop Configuration

1. Set Up an OAuth Application

  • In your Silverpop dashboard, go to Settings > Organization Settings > Application Account Access.
  • Click Add Application.
  • Enter the name Gigya and click Add.

Click to enlarge screenshot

The system displays the Client ID and Client Secret for the Gigya application. Copy these details to give to your Gigya Implementation Consultant

Click to enlarge screenshot

  • Back in the Application Account Access box, click Add Account Access.
  • Select the Gigya application you just created and select a user account.
  • Click Add.
  • A Refresh Token enabling access to the Gigya application will be sent to the user account's email address.

Click to enlarge screenshot

 

2. Configure Your Time Zone

To make sure your Silverpop account is set to GMT:

  • Go to Settings > User Accounts.
  • Select the user account you will be using for the Gigya integration.
  • In the View/Edit User page, under Time Zone, choose GMT.


IdentitySync Configuration

Gigya's IdentitySync is based on scheduled data flows, which are built of a series of preconfigured steps for extracting the data from the source database, transforming it as needed and loading it into the target database.

The following guide outlines the general steps for configuring an IdentitySync dataflow. For integrating with Silverpop, you will require the following components: 

In addition, you can view the following sample flows: 

To create an integration based on IdentitySync, complete the following process:

The license could not be verified: License Certificate has expired!

1. Create Data Flow

  1. Open IdentitySync Data Flows in Gigya's Console. Make sure your are signed in and have selected the relevant site. The IdentitySync dashboard may also be accessed by clicking Settings in the upper menu and then IdentitySync Data Flows in the left menu.

  2. In the dashboard, click Create Data Flow

  3. In the Create Data Flow window, select the data flow integration from the dropdown. If the flow you wish to create is not available in the dropdown, select any available flow: it is customized in the next steps. For more information, see Dataflow Templates.

  4. Select the data flow template: the direction of the flow, whether from or into Gigya. Note that at the bottom of this window, you can see an outline of the flow that will be created (e.g., Account > rename > dsv > gzip >sftp). 

  5. Click Continue. As a result, the IdentitySync Studio screen opens in the dashboard. 

2. Edit the Data Flow

The data flow you created is built of the required steps for data transfer between Gigya and the selected vendor. Use the Component Repository to understand the structure and parameters required in each step.

Using IdentitySync Studio, you can:

  • Specify passwords, IDs, API keys etc. required for accessing each system and customer database.
  • Add the names of fields included in the data flow.
  • Flatten fields, remove non-ASCII strings, specify the compression type, parse in JSON or DSV format, etc. 
  • Map fields and extract array data, for example using field.array.extract.
  • Change the name of the data flow. 
  • Split a data flow, for example if you want to create two duplicate files and upload each file into a different destination. To do so, simply drag and drop the relevant step into the flow, and add connecting arrows as needed. In the code for the flow, this will be expressed in the next attribute, where you will find reference to the next two steps rather than just one. For a sample dataflow which employs this method, see the Epsilon Dataflow.
  • Add Custom Scripts.
  • Write failed records, that did not complete the flow successfully, to a separate file for review. 

The following screenshots include example screenshots for implementing IdentitySync flows. Your actual implementation may require using different components from the ones shown.

 

To do so: 

  1. If it's more convenient, you can work in full screen mode by clicking the full-screen toggle on the top rigt corner. 

  2. Double-click any of the steps to add or edit its parameters. Click OK when finished. 

  3. To add a new step, start typing its name in the Search component box. Drag the step from the list of components into the canvas.
  4. Drag arrows from/to the new step and from/to existing steps, to include it in the correct place in the flow. Make sure the "Success path" arrow is selected, under Connector Type
  5. To add a custom step, locate the record.evaluate step in the list of components and drag it to the canvas. 
  6. Double click the custom step to open a JavaScript editor. Click Test script to validate the code. For a full explanation of custom steps, see IdentitySync Custom Scripts

  7. To split the data flow (for example to write to two target platforms), add the relevant step (e.g. another "write" step) and draw arrows accordingly: 

  8. Handling failed records: You can add additional steps after a "writer" step, for writing to a separate file the records that did not complete the flow successfully. To do so: 
    1. Add the relevant components to the flow (for example, a file.format step to write the records to a file, and a writer to write the file to the relevant destination). 
    2. Under Connector Type, select the "Error path" connector. 
    3. Draw a connection from the original writer, to which successful records will be written, to the next step that handles failed records (e.g., the file.format step). 

    4. Under Connector Type, select the "Success path". 

    5. Connect the next steps that handle the failed records (e.g., the writer) using the "Successful path" connector. 

  9. Delete a step by selecting it and hitting the Delete button on your keyboard.
  10. If necessary, click Source to review the data flow code , and edit the code as needed. 
  11. Click Save

Your dashboard should now look something like this: 

Actions

The following actions are available: 

IconActionDescription
EditOpens the current data flow in IdentitySync Studio and change any of its attributes, steps and parameters.
Run TestRuns the data flow once on 10 records for test purposes. If the test was successful, after refreshing the dashboard, you will see the timestamp of the test run under Last Successful Run. Use the Status button to view the details of the run. See Job History  section on this page.
Schedule

See Schedule the Dataflow.

DuplicateUseful for creating a new data flow based on a flow which has already been customized, if you wish to create a similar flow with slight variations.
StatusDisplays the status of the current jobs running in your IdentitySync configuration. See Job History section on this page.
DeleteDeletes this data flow.

 

3. Schedule the Dataflow

  1. Under Actions, click (schedule) to open the Scheduler. 
  2. Click Create Schedule
  3. Configure the schedule: 
    • Enter a schedule name
    • Change the start time as needed
    • Choose whether to run once or at scheduled intervals
    • "Pull all records" should usually be selected only in the first run, when migrating records from one database to the other, and in any case should be used with caution. If the checkbox is not selected, and this is the first time this dataflow is run, records will be pulled according to the following logic: 
      • If the dataflow is set to run once, all records from the last 24 hours will be pulled. 
      • If the dataflow is recurring, records will be pulled according to the defined frequency. For example, if the dataflow is set to run once a week, the first time it is run, it will pull all records from the previous week. 
    • (Optional) Enter the email adress(es) for success and failure of the dataflow run. 
    • (Optional) Limit to a specific number of records. This is usually used for test runs: when running a test from the dashboard, a one-time schedule is created which runs immediately for 10 records. 
  4. Click Create, and, once you are back in the Schedule dashboard, click the Refresh button. 
  5. The status of the scheduling is indicated in the Status column. 
  6. You can stop a job mid-run by clicking the Stop icon under Actions
  • The dashboard creates a Scheduling Object.
  • Last Successful Run corresponds with the lastRuntime parameter in the Dataflow Object
  • The Scheduled Next Run displays the newest date defined in the scheduler. Therefore, it's possible to see a past date here, if no more recent dates were configured.

 

  • No labels