SMS Campaign - Selecting Personalization Data

Note: The SMS Campaign Workbook now has an updated interface and is now called the SMS Campaign Designer. Campaign Designer is now enabled for all accounts, and it replaces Campaign Workbook for this channel. Unlike the Campaign Designer, there were no major changes made to the Message Designer's interface.

You can select additional data sources (supplemental data tables, profile extensions, and dynamic variables) and select columns to use for a campaign.

About supplemental data tables and profile extensions

Supplemental data tables and profile extensions store additional information that define behavioral, demographic or profile preference characteristics of your contacts.

Note that by default, supplemental data tables and profile extensions apply to the profile list as well as the proof list. However, if you do not want to use a specific data source for the proof list, you can select an alternate one as described later in this topic.

About dynamic variables

Dynamic variables are additional pieces of information available at runtime.

When Oracle Responsys SMS receives an incoming message from a mobile user (for example, JOIN JOHN john@example.com), it fills the predefined dynamic variables with the information from the incoming message. In our example, the dynamic variables will be filled with the following values:

  • SMS_KEYWORD—JOIN
  • SMS_USER_INPUT1—JOHN
  • SMS_USER_INPUT2—john@example.com

These values now can be used in SMS message personalization. In addition, these values will be passed to Program as Entry Tracking variables, where they can be used in either a Data Switch or the Set Data event.

Responsys SMS provides seven predefined dynamic variables:

  • SMS_CODE
  • SMS_KEYWORD
  • SMS_USER_INPUT1 through SMS_USER_INPUT5

You cannot rename, modify or delete pre-defined variables. However, you can create and modify your own dynamic variables.

Dynamic Variables for Custom Values

Important: This feature is currently released under our Controlled Availability program. To request access to this feature, please log in to My Oracle Support and create a service request.

If you intend to pass custom values, add additional dynamic variables to your SMS campaigns. The additional variables defined for this purpose need to follow this nomenclature: the key should begin with " RSYS_SMS_CUSTOM_ ".

You can define upto 5 such additional keys (data source > dynamic variables).

Note: If more than 5 are created, the personalization layer will only take first 5 variables (in sequence of definition).

If the Allow custom parameters flag is ON, and if at least one dynamic variable is defined (with the correct nomenclature), then that parameter is picked and passed to the SMS aggregator in the MT payload.

If the Allow custom parameters flag is OFF and/or the dynamic variable is not defined, then no additional parameter is passed in the MT payload.

Important for Partners:

The partner entity being used for this account also needs to be updated:

  • The customscript.js for such partners should be updated to include 5 additional parameters.

  • The dynamic variable can support varchar(200).

Before you begin:

Before you can select additional data sources, you must:

  • Create the supplemental tables and profile extensions you will use.
    You must assign aliases to the data sources all the fields and columns you want to use.

    Important:Make sure the field names you use for personalization are unique across data sources. Duplicate columns from different data sources with different values can result in missing personalization in campaign messages. Choosing two field names with the same name will prompt a warning message in the validation section. If these columns have the same set of values, this will not be an issue. This warning message will not impact your campaign launch.

    However, when a supplemental data source is used as a look-up table, those columns may have duplicate names, and will not cause a personalization error.

  • Select an audience

To add a data source:

  1. Click Add new source.
  2. In the Add new source dialog, select a data source type from the drop-down list.
  3. Do one of the following:
    • For a Profile extension: Select the table, then select the columns you want to use. Use the Ctrl and Shift keys to select multiple columns.

      Note: Columns from the data source are not automatically added to the campaign. This means that you need to select all columns you want to use.

    • For Supplemental data: Select the folder where the data source is located, select the data source, then click .
    • For a Dynamic variable: Type the variable name ins the Variable name field.
  4. Click Select.

    The data source is added and appears in the appropriate section of the data sources list.

Working with columns

You can customize columns on the Data sources page as follows.

  • To add a column - Click Add Column and select the columns you want to add, then click Select. Use the Ctrl and Shift keys to select multiple columns.
  • To specify a default value - Type the value in the Default field.
  • To insert a personalization token - Click , enter the script, then click Apply.
  • To use a column as a lookup key - Select the Lookup Key checkbox in the column row.
  • To remove a column - Click in the row of the column you want to remove.

To select an alternate data source for the proof list:

  1. Click Settings of the data source you want.
  2. In the Settings dialog, click Select data source.

    The Select Data Source for Proofs dialog opens.

  3. In the Select data source for proofs dialog, select the folder where the data source is located, select the data source, and click .
  4. Click Select.
  5. In the Settings dialog, click Done.

To remove a data source:

  • Click next to the name of the data source you want to remove.

Learn more