Gigya Job Openings

Silverpop Dataflow - Outbound

Skip to end of metadata
Go to start of metadata

The dataflow that loads data from Gigya into Silverpop involves renaming Gigya fields to match Silverpop's format, and writing to Silverpop's OOTB status field by using the newsletterFieldparameter. In this example, the subscription status is read from a custom Gigya field, data.subscribed. If you are using Enterprise Preference Manager's communication preferences, you can write the status to any subscription field (e.g. subscriptions.mySub.email.isSubscribed). 

The various dataflow steps are described in greater detail here: Component Repository

 

{
 "name": "Silverpop_Dataflow_Outbound",
 "description": "account > rename > silverpop",
 "steps": [
  {
   "id": "account",
   "type": "datasource.read.gigya.account",
   "params": {
    "select": "UID,profile.email,data.subscribed"
   },
   "next": [
    "rename"
   ]
  },
  {
   "id": "rename",
   "type": "field.rename",
   "params": {
    "fields": [
     {
      "sourceField": "UID",
      "targetField": "GigyaUid"
     },
     {
      "sourceField": "profile.email",
      "targetField": "EMAIL"
     },
     {
      "sourceField": "data.subscribed",
      "targetField": "newsletterField"
     }
    ]
   },
   "next": [
    "silverpop"
   ]
  },
  {
   "id": "silverpop",
   "type": "datasource.write.silverpop",
   "params": {
    "clientId": "...",
    "clientSecret": "...",
    "refreshToken": "...",
    "podNumber": 1,
    "username": "...",
    "password": "...",
    "listId": "...",
    "newsletterField": "newsletterField"
   }
  }
 ]
}
  • No labels