Preview of CI360 March 2021 release (21.03)

[jimhazen]

Overview

The March 2021 (21.03) release of SAS® Customer Intelligence 360 includes a bunch of exciting new features, but I wanted to take a minute to highlight a couple of additions we've made regarding collecting mobile app behavior and changes to the data model available for download.

Mobile App Events

For quite a while, customers have asked us for the ability to configure additional mobile events to track specific user behavior such as tracking e-commerce interactions - within their mobile applications, similar to how they would track them on their websites.

With the March release, SAS® Customer Intelligence 360 has added mobile versions of the business events that had previously only been available as web events. These events can be used to capture behaviors in the mobile app, such as

• Add to Cart
• Cart View
• Checkout View
• Purchase View
• Product View
• Promotions
• Internal Search

For these event types, when you create an event you will now see a new option Mobile App Action, which you can use to define a mobile version of the event.

These events are defined in the user interface under Events. They display the standard attributes that you can utilize and provide the ability to add custom attributes to the event's configuration.

After the events are published and the mobile SDK is coded to send these events and attributes, the mobile events are recorded in [the same tables in the Unified Data Model (UDM) that currently have the web equivalent of these events. For example: An Add to Cart event for a mobile app will flow into the CART_ACTIVITY_DETAILS table in the UDM.

New columns have been added to the UDM tables as a part of schemaVersion 7 to distinguish the channel and mobile application.

In addition to collecting these events and having them land in the UDM tables, these mobile events can also be used throughout CI 360 ENGAGE for the following uses:

• targeting and triggering task
• primary or secondary metrics for tasks
• data views
• triggering an activity
• cloud segments
• streaming event data

For more information about how to send the events and attributes, see Collecting Mobile Event Data in the Administration Guide. 

UDM Schema Version 7

The March release also has a new schema version of the UDM that adds new tables and columns to the data model. To call for the new schema, make sure you update your API call to ask for schemaVersion=7.

The following columns have been added to most of the tables for SAS 360 Engage:

• response_tracking_cd – stores the response tracking code generated by SAS Customer Intelligence 360 on Engage events
• task_version_id – allows users to connect to the specific version of the task in the metadata
• message_id – stores the message ID if a message was used in a task
• message_version_id – allows users to connect to the specific version of the message in the metadata
• creative_version_id – allows users to connect to the specific version of the creative in the metadata
• segment_id – stores the segment ID if a segment was used in a task
• segment_version_id – allows users to connect to the specific version of the segment in the metadata
• properties_map_doc – used for storing custom attributes on task events, which is a feature coming soon
• event_key_cd – used to distinguish if event came from API

Additional columns were added to some of the email tables in the UDM for SAS 360 Engage:

• program_id – denotes the email program that was used
• recipient_domain_nm – represents the email domain of the individual
• reason_txt – represents the reason an email bounces such as the address being invalid

Additional columns were added to the metadata table MD_TASK_X_CREATIVE to help users understand which creative and spot combinations were used in testing or in multi-spot tasks. The new columns are:

• spot_id
• arbitration_method_cd
• arbitration_method_val
• variant_id
• variant_nm

New tables were added to 360 Engage to give more visibility into how CI 360 is executing tasks:

• IMPRESSION_DELIVERED - represents that content has been delivered to a web spot. Users can use this along with the IMPRESSION_VIEWABLE table to determine content that has been delivered to a spot but not viewed.
• IN_APP_TARGETING_REQUEST – represents when a request is made to execute an In-App Message.
• NOTIFICATION_TARGETING_REQUEST – represents when a request is made to execute a mobile push notification.
• SPOT_REQUESTED – represents that content has been delivered to a mobile spot.

New columns were also added to some of the existing tables for SAS 360 Discover:

• channel_nm – with the introduction of mobile events, Discover tables have which channel the event came from such as mobile or web
• mobile_app_id – provides the mobile application that generated the mobile event
• event_key_cd– used to distinguish if event came from API
• properties_map_doc - used for storing custom attributes
• cart_nm – added to the CART_ACTIVITY_DETAILS, ORDER_DETAILS, ORDER_SUMMARY
• availability_message_txt, saving_message_txt, shipping_message_txt – added to CART_ACTIVITY_DETAILS
• activity_dttm, activity_dttm_tz, cart_id, order_id – added to ORDER_DETAILS
• referrer_url – added to PAGE_DETAILS
• response_tracking_cd – added to EXTERNAL_EVENTS to store response tracking codes for events being injected into the API Gateway