Creating a list or channel list

This topic describes how to create profile lists, App channel lists, and Web Push channel lists.

Creating a List

Most accounts use a single primary profile list for all customers. In some cases you may require multiple profile lists.

Tip: For new accounts provisioned after 19A, system administrators can choose to have a predefined set of assets (a profile list, PETs, and supplemental tables) automatically included in the account, based on an industry vertical. For more information, see Preloaded Data Assets.

Generally, one profile list (always your primary customer database) is sufficient for defining and customizing all your data needs. This is particularly true if the Distributed Marketing (DM) feature is enabled for your account. Your primary DM profile list defines your organization's entire audience, special fields within the list define the list members to which your regional (if any) and local marketers can send campaigns, and filters on the list are available to target those campaigns to list members with specific characteristics.

The following steps creates an empty profile list containing only system-defined fields and no records. Even though empty, this list may be linked to associated items, such as campaigns, filters, and programs. At any time you may return to a list, and add to or edit it as you require.

To create a profile list:

  1. Click The Lists icon Data on the side navigation bar, and select Profile Lists. (Not seeing this choice? Refer to the Side navigation bar changes topic.)
  2. Click Create New List.
  3. Enter a unique name, select the containing folder, and optionally provide a description.
  4. Click Save.

After you create the profile list, select one of the following options:

Creating an App channel list

The App channel list is used in Mobile App campaigns. The App channel list is associated with a profile list and stores all user and device information for all apps. You can only have one App channel list for a profile list.

The records in this list are unique based on the combination of API_KEY and DEVICE_ID_.

The known user match key is the identifier used to determine the known user record per device. You must select the known user match key when creating the App channel list.

Important: Coordinate with the mobile app developers when choosing the user match key. Mobile app developers must use the user match key. Mobile app developers must use the user match key for the USER_IDENTIFIER_ parameter in their mobile apps. Only one field may be used as the match key across your app users, and it cannot be changed later.

To create an App channel list:

  1. Click The Lists icon Data on the side navigation bar, and select Profile Lists. (Not seeing this choice? Refer to the Side navigation bar changes topic.)
  2. Select the profile list for which to create the App channel list and click Create App channel list.
  3. Enter a unique name and select the containing folder.
  4. To select a known user match key, select a field from the Map user identifier of the App Channel recipient to drop-down list.

    We recommend one of the following choices:

    • CUSTOMER_ID_
    • EMAIL_ADDRESS_
    • MOBILE_NUMBER_

    The following choices are also available—but not recommended—to be set as the match key:

    • EMAIL_SHA256_HASH_ (SHA-256-hashed email address)
    • EMAIL_MD5_HASH_ (MD5-hashed email address)

    Why are these values not recommended? MD5/SHA are one-way keys. Therefore, the system will be unable to use the incoming USER_IDENTIFIER_ value to populate the EMAIL_ADDRESS_ field in a new profile list record. (Merging with existing profile list records is unaffected.) Not having a plain-text email address in a profile list record is a problem, because Responsys users typically search for profile list records by plain-text email address. Being unable to locate a record may cause confusion.

  5. Click Save.

The App channel list must then be associated to your app. Records will be populated via the Oracle Responsys Mobile App Platform Cloud Service. Learn more about managing the app configurations in Oracle Responsys.

Creating a Web Push channel list

The Web Push channel list is used in Web Push campaigns. The Web Push channel list is associated with a profile list and stores all user and device information for all associated websites. You can only have one Web Push channel list for a profile list.

The records in this list are unique based on the combination of VISITOR_ID_ and API_KEY_. The VISITOR_ID_ field is unique for a website.

The known user match key is the identifier used to determine the known user record per device. You must select the known user match key when creating the Web Push channel list.

Important: Coordinate with the web app developers when choosing the user match key. Web app developers must use the user match key for the USER_IDENTIFIER_ paramater in their web apps. Only one field may be used as the match key across your web app users, and it cannot be changed later.

To create a Web Push channel list:

  1. Click The Lists icon Data on the side navigation bar, and select Profile Lists. (Not seeing this choice? Refer to the Side navigation bar changes topic.)
  2. Select the profile list for which to create the Web Push channel list and click Create Web Push channel list.
  3. Enter a unique name and select the containing folder.
  4. To select a known user match key, select a field from the Map user identifier of the Web Push Channel recipient to drop-down list.

    We recommend one of the following choises:

    • CUSTOMER_ID_
    • EMAIL_ADDRESS_
    • MOBILE_NUMBER_

    The following choices are also available—but not recommended—to be set as the match key:

    • EMAIL_SHA256_HASH_ (SHA-256-hashed email address)
    • EMAIL_MD5_HASH_ (MD5-hashed email address)

    Why are these values not recommended? MD5/SHA are one-way keys. Therefore, the

    system will be unable to use the incoming USER_IDENTIFIER_ value to populate the EMAIL_ADDRESS_ field in a new profile list record. (Merging with existing profile list records is unaffected.) Not having a plain-text email address in a profile list record is a problem, because Responsys users typically search for profile list records by plain-text email address. Being unable to locate a record may cause confusion.

  5. Click Save.

The Web Push channel list must then be associated to your web push app. Records will be populated via the Oracle Responsys Web Push Platform. Learn more about managing the Web Push app configurations in Oracle Responsys.

Learn more