Changing Channel Status Records

The Change Channel Status option allows you to conveniently change multiple opt-in/out status records related to the email, mobile, and/or postal channels.

Note: Using a step-driven process, you select a delimited text file containing the status field changes you want to apply to a preexisting List. However, only records that currently exist within the associated List are changed. New customer records and/or new data (excluding status) from the imported Change Channel Status file are not added to the associated List.

To change Channel Status list records:

  1. Click Folders on the side navigation bar, and select the folder containing the List.
  2. Click s next to the list name, and select Change Channel Status.

Step 1: Inbound Source

  1. Enter path and name, or click browse to select desired file to load. File should be in .CSV (comma separated value) format.
  2. Confirm the character set of the file.
  3. Click Next.

    Note: For large files, the next step may take a few moments to appear.

Step 2: File Handling

  1. Select the delimiter (typically a comma) that divides the fields (columns) in the file.
  2. Specify whether text columns are enclosed in single or double quotation marks.
  3. Check whether the first line contains column names, or the file starts with a data record.
  4. Click Next.

Step 3: Table Fields

The purpose of the Table Fields page is to display all fields from your incoming file, and allow you to map and select new field specifications, as needed.

Notes

  • Long field names are truncated to 30 characters.
  • Field names are not case-sensitive.
  • If any changes result in duplicate field names, you will need to manually rename them.
  • For fields unrelated to email, mobile, and postal status channels: Click next to the related List field, and select --skip this field--.
  • All system-defined field names (defined and reserved by Oracle Responsys) end with an underscore character, for example: EMAIL_ADDRESS_. Therefore, imported/custom-defined field names may not end with an underscore.
  • Where ever possible, match (if not already auto-matched) like-named incoming fields with existing List fields, for example: CUST_ID matched to CUSTOMER_ID_.
  • If an equivalent predefined name does not exist: Click next to the related List field. Select the appropriate data type for your field. A new field entry immediately appears with the name used from the import field. Change, if needed.

For more details about data type and field name requirements, see Data Types and Field Names

Step 4: Record Handling

This step allows you to define importing merge rules, as well as the opt-in/out status and deliverability actions for email, mobile, and postal channels.

  1. Define the merge rules for matching new to existing records. You can match on email address, email address and another selected field, or selective combinations.
  2. Select and check whether to opt-in or opt-out for matching records (based on the merge choices you made above) for each status channel. Select deliverability for the three channels. You may also choose to permanently delete matching status records from your existing List.
  3. When done, click Next.

Step 5: Load File

  1. Elect whether to trigger a custom event(s) for any customers associated with your defined status changes.

    Note: REI events cannot be triggered in this step.

  2. When done, click Next to begin loading file.

    Note: When your load completes, click View Import History (via the List Management page) to view and audit load record details. You may download rejected records, resolve any issues, and repeat the Import Data option. (It is recommended that you check for rejected records after every load.)

Learn more