We recently discovered a minor issue with the SAS download program made available in GitHub. There were occasionally problems downloading tables where errors were generated in the json response file but ignored because the download call itself was successful. The fix made was to include better handling of errors in the download process even when the http call returns a success.    Customers that rely on the SAS version of the download program to retrieve data from the UDM or for CDM should update their program.  To get an updated program, please use this link: https://github.com/sassoftware/ci360-download-client-sas   ... View more

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 ... View more

Overview The October 2020 (20.10) release of SAS® Customer Intelligence 360 will include a new version of the CDM. The original CDM was the data repository for contacts and responses for SAS Customer Intelligence Studio solutions (such as SAS Marketing Automation) and consisted of a data model containing information about targeted customers, campaigns, and communications. With this new version of CDM, SAS is taking elements from the original CDM and combining it with newer concepts coming from SAS Customer Intelligence 360 to generate a new model. The new model will be used to store contact and response history, along with corresponding metadata to be used in segment criteria for SAS 360 Engage: Direct. Eventually, other products within SAS Customer Intelligence 360 will use the new CDM.   How does the CDM differ from the Unified Data Model (UDM)? In the March 2020 (20.03) release of SAS Customer Intelligence 360, the UDM model was released, enabling customers to download event data and metadata from SAS 360 Engage and SAS 360 Discover (and now Plan).   CDM will include data populated from the UDM in the cloud and any historical data that is migrated from SAS Customer Intelligence Studio. As a result, CDM will contain metadata from SAS Customer Intelligence 360 items (tasks, segments, messages, creatives, etc), objects from SAS Customer Intelligence Studio (campaigns and treatments) and event tables.   How do customers get access to the CDM tables? Customers that are interested in getting access to the new CDM data need to contact SAS Tech Support to enable the CDM jobs to run for their tenant(s).  Get the latest SAS download program from GitHub: https://github.com/sassoftware/ci360-download-client-sas Get the sample loader program and DDLs from GitHub and modify loader program to suit your database: https://github.com/sassoftware/ci360-cdm-loader-sas   What’s in the CDM? The CDM consists of 30 tables and primarily sourced from UDM tables. The CDM tables are: Table Name Description CDM_ACTIVITY_CUSTOM_ATTR This table contains custom properties that have been applied to an activity. These custom properties assist in analyzing activities (for example, by grouping them or otherwise distinguishing them from one another). Data for this table is obtained from the MD_ACTIVITY_CUSTOM_PROP table. CDM_ACTIVITY_DETAIL This table contains metadata about published activities. Data for this table is obtained from the MD_ACTIVITY table. CDM_ACTIVITY_X_TASK This table shows the relationship between published tasks and published activities. The data in this table can be analyzed when you want to know which tasks are part of an activity. Data for this table is obtained from the MD_ACTIVITY_X_TASK table. CDM_BUSINESS_CONTEXT This table contains metadata about business contexts. A business context allows you to restrict data access to only the information that is required for a specific business need. A user can have access to more than one business context.   Note: This table will be available for download in the 20.10 release (October 2020), but will not initially be populated with data until November release. Data for this table will soon be obtained from the MD_BUSINESS_CONTEXT table. CDM_CAMPAIGN_CUSTOM_ATTR This table is in the schema but is not currently available for download. If you need more information about this table, please contact SAS Technical Support. Data for this table is obtained from the user-defined field tables that describe campaigns and campaign pages. CDM_CAMPAIGN_DETAIL This table is in the schema but is not currently available for download. If you need more information about this table, please contact SAS Technical Support. Data for this table is obtained from the CI_CAMPAIGN table. CDM_CONTACT_CHANNEL This table contains the channel of the task where the contact events occurred, as well as information about the contact. Keep these items in mind when using this table: This table contains information about the channel of the task, not the event. This table contains information only for known users (users with a subject ID). In the Properties tab, the check box for generating contact events must be selected. In addition, the check box that classifies events as contacts (available when adding an event as a metric) must be selected. Data for this table is obtained from the CONTACT_HISTORY table. CDM_CONTACT_HISTORY This table stores all of the SAS Customer Intelligence 360 events that are marked as contact events either in the Properties tab of a task properties or task metrics from. It might also contain events from SAS Customer Intelligence Studio for known customers. In the Properties tab, the check box for generating contact events must be selected. In addition, the check box that classifies events as contacts (available when adding an event as a metric) must be selected. Data for this table is obtained from the CONTACT_HISTORY table. CDM_CONTACT_STATUS This table contains data from SAS Customer Intelligence Studio. It is not populated by SAS Customer Intelligence 360. CDM_CONTENT_CUSTOM_ATTR This table represents the custom property metadata associated with messages, creatives, and treatments from SAS Customer Intelligence Studio. Data for this table is obtained from the following tables: MD_CREATIVE_CUSTOM_PROP and MD_MESSAGE_CUSTOM_PROP. CDM_CONTENT_DETAIL This table contains metadata about messages and creatives from SAS Customer Intelligence 360 and treatments from SAS Customer Intelligence Studio. Data for this table is obtained from the following tables: MD_CREATIVE and MD_MESSAGE. CDM_DYN_CONTENT_CUSTOM_ATTR This table contains dynamic attributes from SAS Customer Intelligence Studio, as well as their values. There is no data from SAS Customer Intelligence 360 stored in this table. This table is in the schema but is not currently available for download. If you need more information about this table, please contact SAS Technical Support. CDM_IDENTIFIER_TYPE This table contains a lookup of the identity and subject type, as well as a description. CDM_IDENTITY_ATTR This table contains information about a customer’s identity (for example, the subject ID). Data for this table is obtained from the IDENTITY_ATTRIBUTES table. CDM_IDENTITY_MAP This table contains a mapping between identity and the subject level. Data for this table is obtained from the IDENTITY_ATTRIBUTES table. CDM_IDENTITY_TYPE This table contains a lookup of subject levels and descriptions. CDM_OCCURRENCE_DETAIL This table contains metadata about occurrences in direct marketing, bulk email, bulk mobile push tasks, and on-premises segment maps. Occurrences that do not execute are displayed as having failed. Data for this table is obtained from the MD_OCCURRENCE table. CDM_RESPONSE_CHANNEL This table lists the channels where responses have occurred and can be used to create aliases for those channels. Data for this table is obtained from the RESPONSE_HISTORY table. CDM_RESPONSE_EXTENDED_ATTR This table lists custom attributes for responses originating from SAS Customer Intelligence Studio. CDM_RESPONSE_HISTORY This table contains all response events for known customers (those customers who have subject IDs). Data for this table is obtained from the RESPONSE_HISTORY table. CDM_RESPONSE_LOOKUP This table contains a list of response events and can be used to create aliases for those events. Data for this table is obtained from the RESPONSE_HISTORY table. CDM_RESPONSE_TYPE Legacy table that categorizes the type of responses (for example, “converted” or “responded to”). It is populated by SAS Customer Intelligence Studio only if the data has been migrated over. CDM_RTC_DETAIL This table contains metadata about Response Tracking Codes. Use this table to link response history and contact history with an RTC. Data for this table is obtained from the MD_RTC table. CDM_RTC_X_CONTENT Use this table to see which content (creatives, messages, or treatments from SAS Customer Intelligence Studio) is associated with a RTC. Data for this table is obtained from the MD_RTC table. CDM_SEGMENT_CUSTOM_ATTR This table contains custom properties associated with a published segment. Note: Custom properties are added by users. Data for this table is obtained from the MD_SEGMENT_CUSTOM_PROP table. CDM_SEGMENT_DETAIL This table contains metadata about published segments. Data for this table is obtained from the MD_SEGMENT table. CDM_SEGMENT_MAP This table contains metadata about published segment maps. Data for this table is obtained from the MD_SEGMENT_MAP table. CDM_SEGMENT_MAP_CUSTOM_ATTR This table contains custom properties associated with a published segment map. Note: Custom properties are added by users.  Data for this table is obtained from the MD_SEGMENT_MAP_CUSTOM_PROP table. CDM_TASK_CUSTOM_ATTR This table contains custom properties associated with a published task. Note: Custom properties are added by users. Data for this table is obtained from the MD_TASK_CUSTOM_PROP table. CDM_TASK_DETAIL This table contains metadata about published tasks. Data for this table is obtained from the MD_TASK table.   How does data end up in the CDM? The prerequisite to having data for the CDM is having SAS Customer Intelligence 360 Engage tasks that generate contact and response events for known customers. A known user is a customer that has a subject_id in SAS Customer Intelligence 360.   Data that populates CDM is sourced from the UDM in the SAS Customer Intelligence 360 cloud, as well as from any historical data that is migrated from SAS Customer Intelligence Studio. As a result, the model consists: Metadata from SAS Customer Intelligence 360 objects (tasks, segments, messages, creatives, and so on) Migrated data from SAS Customer Intelligence Studio (campaigns and treatments) Event tables (contacts and responses) An hourly job runs in the cloud to produce CDM tables in the right format to be loaded straight into the on-premises CDM with minimal transformation occurring on-premises. Here is an overview of that process:   First, contact and response events need to be generated. Contact events are generated by SAS Customer Intelligence 360 either: when a user selects to generate a contact in the Properties tab of a task, or from classifying a primary or secondary metric as a contact in the Insights tab of a task. Figure 1 Properties tab with contact event selected   Figure 2 Metric classified as contact event   Responses are generated by the user selecting to classify the primary or secondary metric in the Insights tab as a response. Figure 3 Metric classified as response event   When the hourly jobs in the cloud run, the contact and response events are filtered by using the IDENTITY_ATTRIBUTES table in the UDM to filter out anonymous contacts or responses. The filter ensures that the contacts and responses have a subject_id associated with them.   After the jobs have run in the cloud, the data is placed in partitioned and nonpartitioned files in the cloud. The event data is partitioned based into hourly buckets. The nonpartitioned data consisting of the metadata are full snapshots of the data each time.   Downloading CDM Data from SAS Customer Intelligence 360 SAS makes the CDM data available directly through the Download API, as well as through a SAS program which also uses the download API. With the release of CDM, SAS added a new category to the Download API called ‘cdm’. Use this category along with schemaVersion=6 to download tables for the CDM from the cloud. Note: Only those events marked as contact or response will be included in the CDM category.   Here is an example of an API call that download non-partitioned data: https://extapigwservice-<tenant> /marketingGateway/discoverService/dataDownload/eventData/detail/nonPartitionedData?schemaVersion=6&category=cdm   Here is an example of an API call that download partitioned data: https://extapigwservice-<tenant> /marketingGateway/discoverService/dataDownload/eventData/detail/partitionedData?schemaVersion=6&dataRangeStartTimeStamp=2020-11-01T00:00:00.000Z&dataRangeEndTimeStamp=2020-11-06T23:59:59.999Z   The recommended method to download these tables is to use the SAS program. The SAS program is a program that can be utilized to download data, unzip the files, and combine the files into staging tables on-premise that are ready to be loaded into the database. The program will reside in GitHub so that users of the program can subscribe to updates that happen over time. You can find the download program here: https://github.com/sassoftware/ci360-download-client-sas   In the download program, make sure you set the following variables in the dsc_download.sas macro: %let mart_nm=cdm; %let DSC_SCHEMA_VERSION=6; %let CATEGORY=cdm;   The download program performs the following functions: Downloads the CDM tables from the cloud based on a time period specified in macro Unzips all the files Combines files into SAS datasets that are used by the loader program   Modifications that you can make to macro: Start/End Time Update the tenantId/secret key in order to generate a new JWT   Prerequisites for the SAS download program: BASE SAS9.4(M4) (Unicode Support) Enable the “SAS to Allow XCMD System Option” on the Workspace and Pooled Workspace Servers Python3 Python is used to generate token for API authentication. Make sure following python libraries are installed getopt, http.client, urllib, re, base64, jwt gzip utility program Download gzip.exe. Add gzip utility program location to PATH environment variable. This is required for SAS program to read .gz files without un-compressing the file. From SAS Customer Intelligence 360, navigate to General Settings -> External -> Access and create new access point if it's not already created. If it is created, get the tenantId and client secret to use in the download program.   Loading Data into On-Premises Database Once the data has been downloaded from the cloud, it is now ready to be loaded into the on-premises database. SAS is making a sample loader program available in GitHub: https://github.com/sassoftware/ci360-cdm-loader-sas. You can use it as a reference for building a program that can take the downloaded data and load into the CDM. The sample program was built with Oracle in mind as the target database. To use a different target database, you can write your own loader program or modify the sample program. The sample program includes some database-agnostic code that can be utilized.   The loader program performs the following functions: Loads the downloaded SAS datasets to the data model Keeps track of successes and failures   The sample loader program can be edited in the following ways: Specify the location of the downloaded CDM data sets Designate the location of the loader macros Change the database credentials Change the level of log messaging   Which tables will not be populated in the initial release? The CDM_BUSINESS_CONTEXT table will not be populated initially but will be populated with the November release. The CDM_IDENTITY_TYPE, CDM_IDENTITY_MAP and CDM_IDENTIFIER_TYPE will either be empty or very sparsely populated until SAS Customer Intelligence 360 supports different identity levels (account, household, individual, etc). Once this feature is in place, the tables will be populated. CDM_CAMPAIGN_DETAIL, CDM_CAMPAIGN_CUSTOM_ATTR, CDM_RESPONSE_EXTENDED_ATTR, CDM_CONTACT_STATUS and CDM_RESPONSE_TYPE will not be populated from SAS Customer Intelligence 360. Instead will be populated from data migrated from SAS Customer Intelligence Studio. Which fields aren’t being populated? CDM_RESPONSE_HISTORY content_version_id – the unique identifier for specific content tied to the response contact_id – the unique identifier of a unique contact row (associating contact and response) CDM_IDENTITY_ATTR valid_from_dttm valid_to_dttm What target databases are supported with DDLs? DDLs can be found in GitHub: https://github.com/sassoftware/ci360-cdm-loader-sas/tree/main/ddl SAP HANA Snowflake Google BigQuery Postgres IBM DB2 Teradata EMC Greenplum Microsoft SQL Server Amazon Redshift Oracle Statement of Support The SAS product functionality described above is provided for informational purposes only based on SAS’ current product roadmap. It does not represent nor alter official SAS product documentation nor is it a guarantee as to the timing of the availability of any product functionality or that such functionality will be made available.   ... View more

As a part of the March release (20.03) for SAS® Customer Intelligence 360, SAS 360 Engage and SAS 360 Discover customers will be able to configure events using JavaScript API as a method in the user interface which enables events for use in SAS 360 Engage as well as populating tables in the Unified Data Model. This means that events configured using the JavaScript API can be used in SAS 360 Engage for targeting, triggering, metrics and other use cases. Previously, JavaScript API events could not be used in SAS 360 Engage.   This capability is especially useful in the following situations: Configuring events on a website that is a Single Page Application (SPA). Users can now use the JavaScript API to send the SPA interactions without having to rely on a page load. Collecting information on pages where using page elements is fragile or unreliable. The developer can control exactly what information is being passed on the event. When selecting JavaScript API as a method for defining an event in the user interface: The user will first need to create a unique event key that will be sent on the event. Standard attributes for the event will be listed in a table as a reference for the developer. Users can add additional custom attributes to the event configuration. To utilize the new JavaScript API functionality, customers have to first implement the new tag (ot-all.min.js) which can be found under General Settings -> SAS Tag Instructions.   This latest release of the JavaScript API enabled many more event types, including:   User-defined business events: Cart Events (purchase, checkout, cartview) Cart-Action Events (add, update, remove) Custom Events Document Events Internal-Search Events Media Events Product View Events Promotion Events Raw events which can be used to define other events such as steps in a Business Process: Change Events Click Events Content-Change Events JavaScript Variable-Change (jsvarchange) Events Load Events Submit Events Engage specific events: Click-Through Events Impression Events Impression-Viewable Events Identity related: Attach Identity Detach Identity ... View more

As we get closer to the March release (20.03) of the Unified User Interface for configuring events for SAS CI360 Discover and SAS CI360 Engage, there was a small change made that differs from what was originally communicated with the previous post found here.   Originally, the user interface was going to have a button to convert Custom Attribute events (from SAS 360 Discover) into Custom Events if the user wanted to use the event in SAS 360 Engage. The 'convert' button has been removed in the 20.03 release. Instead, if customers want to use the Custom Attribute event in SAS 360 Engage, they will need to create a new Custom Event as opposed to converting the older Custom Attribute event.    Custom Attribute events will continue to populate the Custom_Attributes table in the data model.          ... View more

A reminder to customers that updated download programs are available now in GitHub to take advantage of the new tables and columns being introduced with the Unified Data Model for SAS® Customer Intelligence 360 in 20.03. Additionally, please follow the advice in the previous post when downloading tables after 20.03 is released: Important information regarding CI360 March 2020 release (20.03)     The following links will take you to to the download programs that are available: • For SAS language and software: https://github.com/sassoftware/ci360-download-client-sas • For Python scripts: https://github.com/sassoftware/ci360-download-client-python   Customers can subscribe to notifications to receive notifications when these programs are updated. ... View more

As customers prepare to start downloading the new Unified Data Model tables and columns as a part of the 20.03 release, there are two guidelines customers should follow before downloading any data:   1. Customers should wait at least a day after the 20.03 release before downloading data with schema 4 (the API parameter “schemaVersion=4”). The 20.03 release is planned for the 3rd week in March, but to find out specific dates, please go to SAS Ci 360 Status. On the Status page, customers can subscribe to notifications and find information about planned maintenance in their respective regions (as it varies).   2. Customers should first download all data through the current date and time with schema 3 (“schemaVersion=3”). When customers are finished downloading with schema 3, then they can start downloading Discover data with schema 4. If customers specify schema 4 to download older data, the returned data will be structured with schema 4 but the data itself will be based on schema 3. This means that customers might receive fewer tables and columns than what exist in the current schema.   The sample download programs that are supplied by SAS are designed to handle this case. Customers that are not using our programs need to make sure that their download programs handle this situation. When their programs send download request that include time periods that cover both schema 3 and schema 4, the programs should treat new columns from schema 4 as empty if no data is returned.   SAS has supplied sample programs on GitHub that use the download API. Customers can subscribe to notifications to receive notifications when these programs are updated: • For SAS language and software: https://github.com/sassoftware/ci360-download-client-sas • For Python scripts: https://github.com/sassoftware/ci360-download-client-python ... View more

Overview Test the Unified Data Model Prior to Release IMPORTANT: Test the Unified Data Model Prior to Release Changes for SAS® 360 Discover Customers Changes for SAS® 360 Engage Customers Deprecation of Ad Hoc Export API Updated Download Programs Changes to the Data Model Statement of Support   Overview/Explanation: The March 2020 release of SAS® Customer Intelligence 360 will include changes to the data model and the user interface. The changes will introduce a comprehensive data model and enable customers to use any event across CI360.   Our customers have routinely requested the ability to use any event, including those previously only available in SAS® 360 Discover, for task targeting, metrics, triggers, and segmentation/data views within SAS® 360 Engage. In addition, the ability to stream event data into other applications for use in real-time scenarios has been requested. Lastly, customers have wanted the ability to download SAS 360 Engage data and join it with SAS 360 Discover data in order to get a more comprehensive view of customer behavior and to have the ability to conduct further analysis and data integrations. To meet the demands of our customers, the March 2020 release of SAS Customer Intelligence 360 will enable the following:    Provide previously configured SAS 360 Discover events for use in SAS 360 Engage for targeting, metrics, triggering, and segmentation/data views. Implement a unified UI known as “Events” as a single place to configure any event. Provide the ability to download a rich set of SAS 360 Engage  tables and metadata, in addition to SAS 360 Discover tables, to create a unified data model.  Stream almost all events in real time, including previously configured SAS 360 Discover events.   These new capabilities will result in changes to the UI, the unified data model, and the download programs used to retrieve data from the cloud.    Testing the Unified Data Model Prior to Release   Prior to official release, customers can begin to familiarize themselves with the tables using the Test Mode API. This method of downloading new tables utilizes the existing SAS Customer Intelligence 360 Download API. With the release of the unified data mart, this API now has categories of tables that allow users to specify groupings of tables they want to download. These categories are enforced by the product licenses held by each customer. By default, not using any specific category yields SAS 360 Discover tables.   Customers are strongly advised to test the new release and tables prior to March 7, 2020, using the Test Mode API with the following parameters:    schemaVersion=4  code=PH4TESTMODE  category=<see below>  Customers must have a license in order to download the categories of tables below. For example, in order to download SAS 360 Engage tables, the customer must have a license for SAS 360 Engage.    Category  License Required  DISCOVER  SAS® 360 Discover  ENGAGEDIGITAL  SAS® 360 Engage: Digital  ENGAGEWEB  SAS® 360 Engage: Digital  ENGAGEMOBILE  SAS® 360 Engage: Digital  ENGAGEMETADATA  SAS® 360 Engage: Digital, SAS® 360 Engage: Direct, SAS® 360 Engage: Email  ENGAGEDIRECT  SAS® 360 Engage: Direct  ENGAGEEMAIL  SAS® 360 Engage: Digital    Example calls using the TEST MODE API   Requesting Discover only data using category:  https://extapigwservice-<server>/marketingGateway/discoverService/dataDownload/eventData/detail/partitioned?code=PH4TESTMODE&schemaVersion=4&category=discover    Downloading Email and Direct data: https://extapigwservice-<server>/marketingGateway/discoverService/dataDownload/eventData/detail/partitioned?code=PH4TESTMODE&schemaVersion=4&category=engageemail,engagedirect    Requesting data using Engage Digital category and specific time window: https://extapigwservice-<server>/marketingGateway/discoverService/dataDownload/eventData/detail/partitionedData?&dataRangeStartTimeStamp=2020-01-08T04:00:00.000Z&dataRangeEndTimeStamp=2020-01-08T04:59:59.999Z&includeAllHourStatus=true&code=PH4TESTMODE&schemaVersion=4&category=engagedigital    Requesting metadata using category: https://extapigwservice-<server>/marketingGateway/discoverService/dataDownload/eventData/detail/nonPartitionedData?code=PH4TESTMODE&schemaVersion=4&category=engagemetadata    Important Note: A new column representing custom attributes is being added to the following SAS 360 Discover tables: GOAL_DETAILS, CART_ACTIVITY_DETAILS, ORDER_DETAILS, ORDER_SUMMARY, and PRODUCT_VIEWS but cannot be tested using the Test Mode API. However, customers can see the new tables.    Changes to the UI    Changes for SAS® 360 Discover Customers    A single unified UI (Events) is being introduced for configuring all events that can be used by both SAS 360 Discover and SAS 360 Engage. SAS 360 Discover users will notice a variety of changes in the UI:    All events and event configurations are either in Events or in General Settings. The Advanced Configuration Rules and Basic Collection Rules sections of the UI have been removed. Some events that were configured in the Advanced Collection Rules section of SAS 360 Discover are automatically migrated in Events. These previously configured events continue to work without any changes being required by the user, including Business Process, Goal, Internal Search, Promotion, and Custom Attribute. The remaining items in Advanced Collection Rules were automatically moved to the General Settings > Classification page and continue to work as previously configured, including Page Category, Form, Profile, and View. The items included in the Basic Collection Rules section have also been moved to the General Settings > Classification page and continue to work as previously configured, including Page URL and Document Download. In the General Settings > Classification page, Profile has become Visitor Profiles and View has become Page View.  With the March 2020 release, most of the previously configured SAS 360 Discover events will be available to SAS 360 Engage for task targeting, metrics, data views, triggers, streaming, and starting activities. These events will be eligible for segmentation selection criteria in an upcoming release. Custom Attribute events must first be converted to Custom Events in order to use them in SAS 360 Engage. If a user does not want to use any Custom Attribute events in SAS 360 Engage, there is no need to convert them, and the events will continue to work as is. The UI has a button that provides users with an option to convert. If a user converts a Custom Attribute event to a Custom Event, that event will no longer populate the Custom_Attributes table in the data model, nor appear in custom attribute reporting. If converted, this event will populate the GOALS_DETAILS and CUSTOM_EVENTS tables.  Custom Events are a new event type that allows users to configure any events that do not already have a standard configuration type (such as Product View). SAS 360 Discover Goal events are automatically migrated to Custom Events, but the configuration remains the same. Users are no longer required to create Custom Attribute events to capture an attribute that is beyond the standard configuration. Instead, they can now add custom attributes to Product View, Add to Cart, Cart View, Checkout View, Purchase View, and Custom events.    There are some additional functionality differences in the new UI:    Page Category and Visitor Profile (previously named Profile) cannot have special characters (for example, double-byte characters) or use spaces in names. This limitation has been in place since the latter part of 2019 (19.09). Migrated Page Categories and Profiles retain the original label but are concatenated with one of the 14 page category slots. New Page Categories or Visitor Profiles cannot use special characters. For Business Process, new configurations of events do not contain step errors or step limits, and previous configurations continue to work.  For Promotion, the conversion event (previously named Promotion Use) must be defined on the same page as Promotion Displayed. This limitation has been in place since the latter part of 2019 (19.09). The UI now only allows the conversion event to be on the same page.   Changes for SAS® 360 Engage Customers    Changes for SAS 360 Engage customers are as follows:    Previous SAS 360 Engage events that were defined using as a Page View, Click, or Form submit are being migrated to Custom Events.  In the targeting, triggering, and metrics interfaces, SAS 360 Discover events now show up as options. Previously, the only way to download SAS 360 Engage data was to use the Ad Hoc Export API. Customers that have a SAS 360 Engage license can now download structured tables associated with SAS 360 Engage events, such as impression_viewable and conversions. SAS plans on deprecating the Ad Hoc Export API and urges customers to start using the SAS Customer Intelligence 360 Download API to retrieve SAS 360 Engage tables instead.   Upcoming releases will include more metadata tables that show cross-associations between objects.   Deprecation of Ad Hoc Export API Due to an architectural change in how data is to be stored and provided, the Ad Hoc Export API is being deprecated by mid-2020 and is being replaced by the unified data mart. With the new SAS 360 Engage tables, organizations can now create custom ad hoc queries and joins once data has been downloaded into a data warehouse. This allows organizations to replicate and expand upon the functionality previously found in the Ad Hoc Export API. In upcoming releases, SAS will introduce the ability to specify tables to make it easier to obtain the specific data required by users.   Updated Download Programs Prior to release, new download programs will be released for SAS software and Python. SAS has begun to add these download programs in GitHub so that customers can subscribe to notifications for program updates. The SAS software version of the download program can be found at https://github.com/sassoftware/ci360-download-client-sas, while the Python version is at https://github.com/sassoftware/ci360-download-client-python.   Changes to the Data Model    With the introduction of the Unified Data Model, there have been changes to some existing SAS 360 Discover tables, as well as additional tables for SAS 360 Discover and SAS 360 Engage.    Changes for SAS® 360 Discover Customers    New SAS 360 Discover tables include the following:    CUSTOM_EVENTS: captures user-defined custom events. This table will eventually replace the GOAL_DETAILS table. Initially, both tables will be populated by Custom Events. CUSTOM_EVENTS_EXT: extension table for custom events DATA_VIEW_DETAILS: captures data view events EXTERNAL EVENT: captures events that are coming from outside of SAS Customer Intelligence 360 through the API gateway MOBILE_FOCUS_DEFOCUS: captures mobile focus and defocus events   New columns are being added to existing SAS 360 Discover tables to represent the custom attributes for events. The following tables will have the new column properties_map_doc added to the end of the table as the last column:    GOAL_DETAILS  CART_ACTIVITY_DETAILS  ORDER_DETAILS  ORDER_SUMMARY  PRODUCT_VIEWS    As described, Custom Attribute events continue to go to the CUSTOMER_ATTRIBUTES table unless a user converts them to a Custom Event. When the conversion occurs, these events no longer populate the CUSTOMER_ATTRIBUTES table and instead populate the CUSTOM_EVENTS and GOAL_DETAILS tables.   Previously configured goal events go to both CUSTOM_EVENTS and GOAL_DETAILS. Newly created Custom Events also go to both CUSTOM_EVENTS and GOAL_DETAILS tables.    Changes for SAS® 360 Engage Customers    New SAS 360 Engage tables include the following:   AB_TEST_PATH_ASSIGNMENT: captures which A/B path individuals are assigned to in an activity ACTIVITY_FLOW_IN: captures the movement of individuals through nodes in an activity ACTIVITY_START: captures the start of an activity ACTIVITY_CONVERSION: captures the primary and secondary metrics for the activity CONTACT_HISTORY: captures contacts made CONVERSION_MILESTONE: captures conversion and milestone events of tasks DIRECT_CONTACT: captures when someone is contacted in a direct marketing task EMAIL_BOUNCE: captures email bounces EMAIL_CLICK: captures email clicks EMAIL_COMPLAINTS: captures email complaints EMAIL_OPEN: captures email opens EMAIL_OPTOUT: captures email opt-outs EMAIL_REPLY: captures email reply events EMAIL_SEND: captures email sends EMAIL_VIEW: captures views of an email on a webpage IMPRESSION_SPOT_VIEWABLE: captures impression viewable events IN_APP_FAILED: captures in-app failed events IN_APP_MESSAGE: captures in-app message interactions IN_APP_SEND: captures in-app send events MOBILE_SPOTS: captures mobile system events (spot_failed, spot_closed, and spot_default_delivered) NOTIFICATION_FAILED: captures push notifications that failed NOTIFICATION_OPENED: captures push notifications that were opened NOTIFICATION_SEND: captures push notifications being sent OUTBOUND_SYSTEM: captures trigger-action events for external system tasks RESPONSE_HISTORY: captures responses SPOT_CLICKED: captures spot-clicked events   In addition to the tables above, the Unified Data Model introduces metadata about the objects used in tasks and activities. The following metadata tables will be available:   md_activity – metadata for all activities md_activity_custom_prop – custom properties of activities md_activity_x_task – cross table that associates activities and tasks md_creative - metadata for all creatives md_creative_custom_prop – custom properties of creatives md_dataview - metadata for all data views md_event - metadata for all event objects md_message - metadata for all messages md_message_custom_prop – custom properties of messages md_segment - metadata for all segments md_segment_custom_prop – custom properties of segments md_segment_map - metadata for all segment maps md_segment_map_custom_prop – custom properties of segment maps md_spot - metadata for all spots md_task - metadata for all tasks md_task_custom_prop – custom properties of tasks   Statement of Support The SAS product functionality described above is provided for informational purposes only based on SAS’ current product roadmap. It does not represent nor alter official SAS product documentation nor is it a guarantee as to the timing of the availability of any product functionality or that such functionality will be made available.   ... View more