Updates for Schema 14 in the UDM for SAS Customer Intelligence 360

[Will_F_SAS]

Starting with the release for January 31st, SAS Customer Intelligence 360 includes updates to the Unified Data Model (UDM) for schema 14. Schema 14 contains enhancements to support these features:

• Audience membership
• Support for A/B testing of email tasks
• Improvements in data collection for cart events, checkout events, and purchase events

These are updates to the existing tables in the UDM:

Table	Updates
MD_AUDIENCE MD_AUDIENCE_OCCURRENCE MD_TASK_X_AUDIENCE	The category for the tables is changed to AUDIENCE. You must have a license for SAS 360 Audiences to download these tables.
MD_DATAVIEW_X_EVENT	The DISCOVER category is added to this table.
MD_TASK	The test_duration column is added. This column indicates the duration of an Email A/B test in the number of hours.
ORDER_SUMMARY	The total_unit_qty column is added. This column contains the number of items that are in the cart, checkout process, or purchase.
OUTBOUND_SYSTEM	This table includes new columns to support audiences as a targeting source in custom bulk tasks. The following columns are added: audience_id - Unique ID that represents the audience in SAS Customer Intelligence 360. aud_occurrence_id - Unique ID that represents the specific occurrence for an audience in SAS Customer Intelligence 360.

These are the new tables in the UDM:

Table	Updates
AUDIENCE_MEMBERSHIP_CHANGE	This table captures data on when individuals enter or exit an audience in SAS Customer Intelligence 360. The category for the table is AUDIENCE. You must have a license for SAS 360 Audiences to download these tables.

With the introduction of audiences in SAS Customer Intelligence 360, the addition of the table AUDIENCE_MEMBERSHIP_CHANGE  enables you to understand who was in an audience during a period of time.

With each entry and exit event, SAS Customer Intelligence 360 stores the timestamp, audience, and occurrence of the audience run that led to the change.

These are the scenarios for when a user enters or exits an audience:

• Entry events:
  1. When an audience runs for the first time, every customer in the audience gets an entry event with that audience, the timestamp, and the occurrence that is associated with that audience run.
  2. On subsequent runs, any new customers that are added to the audience generate an entry event for that audience (which includes the timestamp and occurrence of the run). Customers that remain in the audience do not generate another entry event.

• Exit events:
  1. When an existing audience runs, every customer that is no longer in the most recent run of the audience generates an exit event for the audience with the timestamp and occurrence of the audience run that caused them to no longer be a part of the audience.
  2. If an audience expires because the expiration date is reached (and the audience was not refreshed, exit events are generated for all members of the audience. The timestamp of the exit event is the expiration date. In this case, there is not an occurrence that is associated with the exit event.