Watson Campaign Automation (IBM Engage) getting started resources and guide for UBX ecosystem partners

Body

General education for Engage

Demo walkthru of Engage: https://vimeo.com/112195442 Password: sp2014

A few helpful times in the video if you want to jump ahead.

Programs 1.0 - 7:15
Scoring Models - 12:50
Old Content Editor - 16:45
Dynamic Content - 18:30

Engage/WCA demos: https://www.youtube.com/watch?v=RiVK0A9wN6s
https://www.youtube.com/watch?v=7b_2hWI5Cpk  (you may have to turn off subtitles or change to English subtitles)

General education topics for new Engage users training - extensive collection of education replays

Using Engage with UBX introduction education module

Registering the Engage UBX endpoint:

1. Register the Engage endpoint in your UBX pilot account - go to Endpoints and select Register new endpoint

Select Engage from the list of available endpoints

Click Next.  You will need to enter your Engage refresh token and database id

Once your Engage credentials are verified click Next.  Once the endpoint registration is complete, the Engage endpoint will appear with the Test Drive endpoints and any other registered endpoints in your UBX pilot account.

Note: To obtain your Engage refresh token and database ID, proceed as follows:

Refresh token:  Click Settings, Application Account Access, Add Account Access.  Select an application (ie: IBM UBX) and a user account, click Add, when submitted the refresh token will be emailed to that account's email id.

Documentation reference - Engage refresh token and database id:

https://www.ibm.com/support/knowledgecenter/SSWU4L/Integrations/imc_Integrations/001_How_to308.html

Database ID:  Click on Data, View Data, click on your database and then click open View Additional Details

 

UBX Event Syndication with Engage:

In order for UBX data to flow into IBM Marketing Cloud, you must setup a database for UBX as a Flexible database and the Email and x1id fields enabled as lookup keys.

Once Marketing Cloud has been registered as an Endpoint, it can now subscribe to published UBX events from IBM partner or second or third party applications. Marketing Cloud (Engage) can consume the data either as Universal Behaviors or as Relational Table data.  Once UBX data has been configured with Universal Behaviors, data becomes available for consumption in Queries, Program Entry Criteria, or Scoring Behaviors.

In the below scenario, Digital Analytics acts as a publisher, and Marketing Cloud (Engage) has subscribed to web site behaviors published by Digital Analytics.

Digital Analytics Publishes Data into Marketing Cloud (Engage):

Sharing Audiences from Engage to another UBX Endpoint:

Publishing audiences from Engage thru UBX:  Education session replay (5:38):  https://learnerportal.kenexa.com/lmscontent/public/industry-solutions/6U028/6U028-4.mp4

Procedure for sharing audiences from Engage to another UBX Endpoint:

1. Create an audience segment using an Engage contact list, database or query in SHARED folder/area

Create and add contacts to a  contact list https://www.ibm.com/support/knowledgecenter/SSTSRG/Create_and_Add_Contacts_to_a_Contact_List.html

Create a contact list from a database  https://www.ibm.com/support/knowledgecenter/SSTSRG/Populate_a_contact_list_using_a_database.html

2.  In UBX, select Share Audience, select Engage as the audience source, and under the list of shareable audiences your new audience segment should appear

3.  Select your UBX endpoint as the destination, specify an existing or new destination audience
4.  Map identifiers and attributes between the source and destination audience:

5. Schedule the audience share job – for testing, leave the default choice of Immediate
6. Select which mode of destination audience update (replace/add/delete)
7. Select Share.  Verify that the audience data has been received in the destination endpoint

Publishing audiences from your UBX solution endpoint to Engage as an audience destination

Identifiers to be used for audiences published to Engage can include typical customer identifier types; Engage specific identifier types used in Engage databases and contact lists are: email, sms and engagecontactid.

In order to allow access to audiences previously published to Engage in UBX, for UBX business users to add, replace or delete entries in the existing audience in Engage (rather than the default behavior of just creating a new audience), the proper audience type must be specified when your UBX endpoint publishes audiences to Engage thru UBX.   Supported UBX audience types for UBX audience publishers are "Databases", "Queries" and "Contact Lists".  For UBX audience destinations, only the "Contact Lists" audience type is supported.

Example JSON response for GET v1/segments API with these audience types:

{
  "responseStatus": "success",
  "result": {
    "totalCount": 3,
    "list": [
      {
        "type": "Databases",
        "id": 1,
        "name": "Test"
      },
      {
        "type": "Queries",
        "id": 2,
        "name": "EmailMarketingData"
      },
      {
        "type": "Contact Lists",
        "id": 3,
        "name": "EmailMarketingData"
      }
    ]
  }
}

 

Working with audience segments in Engage

Create an audience segment for mailing contacts:

You can create a database for the audience segment and import audience data the database, documentation link

Working with non-keyed databases

Engage audiences for use with UBX must be in a non-keyed database. For partners and clients new to non-keyed databases, these articles and KB entries may be informative.

Key use cases and benefits for non-keyed databases in Engage: http://www.silverpop.com/blogs/email-marketing/building-marketing-profiles.html

Differences between keyed and non-keyed databases and why non-keyed databases provide benefits for working with universal behaviors and UBX: http://www.ibm.com/support/knowledgecenter/en/SSTSRG/What_are_the_differences_in_Email_keyed_Non-keyed_and_Combination_Key_unique_identifiers.html

Import audience entries to a non-keyed database:  http://www.ibm.com/support/knowledgecenter/SSTSRG/Import_Data_into_a_Non-keyed_Database.html   

Merge email keyed and non-keyed databases in Engage:  http://www.ibm.com/support/knowledgecenter/SSTSRG/Merge_Non-Keyed_and_Email_Keyed_Databases.html

Enable lookup keys in a non-keyed database: http://www.ibm.com/support/knowledgecenter/en/SSTSRG/Enable_Lookup_Keys_on_a_Non-Keyed_Database.html

Using Contact Matching to identify customers in a non-keyed database, for instance, to allow a customer to opt-in to a non-keyed database again:  http://www.ibm.com/support/knowledgecenter/en/SSTSRG/If_I_use_a_non-keyed_database_how_can_a_contact_opt_in_again_to_my_database.html