Erwin Diagrams More erwin diagrams are available for SAS Customer Intelligence 360. The links are in the Help Center in the "About" topics for each set of tables (for example, the topic “About SAS 360 Engage Detail Tables” in the SAS Customer Intelligence 360: Administration Guide).   We plan to update these the diagrams for each schema and to improve readability where we can. Currently, the recommendation is to download the PDFs and use Adobe Reader to view them. This lets you get a zoom level higher than 500% (Chrome's default).   Job Summary Email Notification for Segment Maps and Direct Marketing Tasks You can define a list of email recipients who are notified when the execution of segment maps or direct marketing tasks is complete. The notification includes success or failure metrics.   Two levels of configuration are available for the notifications: a global system configuration setting and an item-level setting.   With a global system configuration, you define a list of email addresses and distribution lists that apply to all segment maps or all direct marketing tasks. To configure your global list of email recipients, navigate to General Settings => System Configuration => Job Summary Notifications, select the On-Premises Segment Maps or the Direct Marketing check box, and enter the email addresses or email distribution lists that should receive an email.   In the following figure, the Wizard and recipients in the “Wizard Employees” distribution list receive email updates on all the direct marketing tasks that are in the system.   Notification Configuration for Direct Marketing Tasks   In addition, you can specify email distribution lists that apply only to a specific segment map or direct marketing task. To configure the specific email distribution lists, open the segment map or direct marketing task, navigate to the Orchestration tab, and select the Job Status Notifications page. Enter the specific email distribution lists that should receive updates in the Segment-specific email distribution list field or the Task-specific email distribution list field.   Note: The email addresses from the global settings are visible on this page, but the global list is read-only.   It is recommended that you use email distribution lists instead of individual email addresses. If you update the email addresses of individual recipients, you must republish the segment map or direct marketing task.   In the following figure, Brenda and recipients in the “Accommodations” distribution list will receive email notifications for the direct marketing task. If the list of task-level recipients needs to be changed, you can make changes to the email distribution list itself (that is, outside of SAS Customer Intelligence 360). You do not need to republish your task because you are retaining "Accommodations@oz.com“ in your definition of the task.   Task-Level Configuration for a Direct Marketing Task   (Available in SAS 360 Engage: Direct)   Updated User Interface Components and Locale Settings As part of an ongoing effort to modernize and improve the user interface, SAS Customer Intelligence 360 is switching to the latest corporate SAS user interface components. The changes are mostly subtle. Here are some examples:   a smaller font so that more information fits on the screen, thus reducing the need for scrolling slightly updated colors The main user interface changes are for the Region and Language settings for a user. By default, the user locale is set to match your browser locale. In this release, the Locale for regional formats and sorting setting provides the locale that is used for sorting data and formatting values such as dates, times, numbers, and currency. The language of the application is controlled by the browser locale.   (Available in SAS 360 Engage: Digital, SAS 360 Engage: Direct, SAS 360 Engage: Email, and SAS 360 Plan)   Usage Report Added to Insights Tab The new Usage report provides a way for users to monitor and track the metrics that are associated with contractual consumption limits. With this additional information, customers can anticipate and proactively manage potential overages more effectively. In the first release of this feature, users gain insight into a number of key metrics:   web and mobile sessions email messages that you attempted to send email previews and spam tests that were run SAS 360 Plan users SAS 360 Engage: Direct data subjects Note: The API Usage tab will be populated in a later release.   To view the report, navigate to Insights and select Usage Report. The report is available to users who are assigned the SAS administrator role in SAS App Central and to users who are specifically given access to the report.   (Available in SAS 360 Engage: Digital, SAS 360 Engage: Direct, SAS 360 Engage: Email, SAS 360 Discover, and SAS 360 Plan)  ... View more

            Include Variable Tags in the File Name of an Export Template This feature enables users to add dynamic information, known as variable tags, to the file name of an export template in General Settings =>  Content Delivery => Export Templates. The file name changes based on the value of the tag that is included. You can use the following variable tags:   Task Name Task Code Segment Map Name Segment Map Code Export Date Export Time User ID Add Variable Tag to File Name   You can include multiple variable tags in the file name, similar to what is used in the export tables for direct marketing tasks and segment maps. Variable tags are available when you edit an export template as well.   Some variable tags are not supported by certain file types. For example, the CSV file type supports all variable tags, but the table and SAS data set file types do not support the %%USERID%% tag.   Note: Changing the file type after variable tags have been added could change the supported variable tags.   When you select an export template, the template’s export name is prefilled with information from the selected variable tags. When a name for an export template contains a variable tag that does not apply to the object, a default name is used instead.   (Available in SAS 360 Engage: Direct)   Schema Version 8 for the Unified Data Model and Common Data Model Organizations that are downloading data from SAS Customer Intelligence 360 now have access to a new schema version for the Unified Data Model (UDM) and Common Data Model (CDM). Depending on your license, you have access to new enhancements as a part of schema version 8. This schema version primarily involves the addition of new columns to existing tables to enable cross-table queries and compatibility.   Here are some of the changes that are part of schema 8:   Columns were added for recommendation tasks in the IMPRESSION_DELIVERED and SPOT_CLICKED tables. This update makes the IMPRESSION_DELIVERED and SPOT_CLICKED tables consistent with the IMPRESSION_SPOT_VIEWABLE table. Columns were added to the CDM tables to ensure that full CDM details are captured and that the integrity between tables is maintained. The EXTERNAL_EVENT table is now available to the categories for SAS 360 Engage. This table was previously available only for SAS 360 Discover.   For a complete list of updates, see Updates for Schema 8 in the UDM and CDM for SAS Customer Intelligence 360 in the SAS Communities.   (Available in SAS 360 Engage: Digital, SAS 360 Engage: Direct, SAS 360 Engage: Optimize, SAS 360 Discover, and SAS 360 Plan)   Cost-Center Budgeting Cost-center budgeting is a top-down approach that gives marketers more granular control over their marketing budgets and expense tracking. SAS 360 Plan provides users an option to configure settings for budgeting with or without cost centers.   With appropriate role-based capabilities, marketers can create and manage a planning item budget for a given time period by allocating funds from the budgets that are available for predefined cost centers. A user can select multiple cost centers and associate them with a fiscal period to create a cost-center budget. The combination of the selected cost centers and the fiscal period creates a unique entity in the application.   Example of Cost-Center Budgets   The planning item budget is calculated as the sum of the funds that are allocated from each cost center.   Example of a Planning Item Budget   Expenses are also tracked for specific cost centers and fiscal periods. This enhancement enables marketers to track expenses at a more granular level.   For example, for the fiscal year 2022, consider a hierarchy of a plan that contains three programs. Each program contains two campaigns.   Example of a Plan Hierarchy   The budget for the plan is the sum of the amounts that are allocated from each of the selected cost centers.   Only the cost centers that are selected for a plan (parent item) are available for the programs (child items). Only the cost centers that are selected for a program (parent item) are available for the campaigns (child items).   Note: A child item can access the cost centers that are selected for the parent item only.   If the budget for the plan is allocated from two cost centers, the program’s budget can be allocated only from those two cost centers. Finally, if the program budget is actually allocated from only one of the two cost centers, then the campaign’s budget is also allocated from that single cost center.   When you track expenses for a planning item, only the cost centers that are available to the parent item are available for commitments and invoices.   To select a budgeting approach that is most suitable for your organization, contact your SAS technical representative.   (Available in SAS 360 Plan)   Configure Report Permissions Users who are assigned the SAS Administrator role in SAS App Central can manage access to the reports that are available from the   Insights page from the navigation bar. By default, all global-level reports are available to all users and groups.   To manage permissions for a report, open the report and click   in the top right corner of the report.   Location of the Icon to Manage Report Permission     In the Add Members window, select the users or groups that you want to give access to the report.   Example of the Add Members Window   (Available in SAS 360 Engage: Digital, SAS 360 Engage: Direct, SAS 360 Engage: Email, SAS 360 Discover, and SAS 360 Plan) ... View more

          New Method of Uploading Geofence Data The option that is used to upload geofence location data has moved to a new location. Starting with this release, navigate to General Settings => Content Delivery => Mobile Applications to upload geofence data. Select the mobile app for which you want to upload geofence or beacon data, click , and then select the CSV file to upload.   This new method of uploading location data places the option with other settings that are related to mobile application management.   (Available in SAS 360 Engage: Digital)   Improved Error Message for Entry of Mobile Certificates If there are issues with your messaging key or certificate registration, the user interface provides an improved, detailed error message, when appropriate.   (Available in SAS 360 Engage: Digital)   Update to Email Header Information As of this release, the To field in an email task can be populated using only the merge tag option. Manually entering hardcoded email addresses in the To field is no longer supported. If you want to send a test email to a single email or a list of internal recipients, you can use the email preview function.   (Available in SAS 360 Engage: Email)   New REST API to Execute Segment Maps and Direct Marketing Tasks Administrators can now execute segment maps and direct marketing tasks by using the Marketing Execution REST API (/marketingExecution). This REST API enables you to run operations on direct marketing tasks.   Published tasks can be executed by calling the REST API and sending either the task ID or the task name. If the task’s name is not unique, you can send the folderPath parameter to uniquely identify which task should be executed.   Note: By default, the REST API does not execute tasks that have a defined schedule. However, an administrator can send the overrideSchedule parameter to override the defined schedule and execute the task when the request is submitted.   The REST API returns a URL that enables you to check the status of the execution (also known as the occurrence). This status gives you the ability to see whether the task executed successfully and the time stamps for when the task started and finished.   The Marketing Execution REST API enables administrators to execute these tasks with an external scheduler. Furthermore, administrators can manage all the dependencies on demand, such as uploading customer data, imported lists, or transient files after an on-premises warehouse has been updated. This feature provides more flexibility for fluent schedules or delays in processes that need to happen before the task execution.   For more information, see Marketing Execution REST API in SAS Customer Intelligence 360: Programming Interfaces.   (Available in SAS 360 Engage: Direct and SAS 360 Engage: Digital)   Additional Component Statuses Included in Maintenance Notifications The SAS® Customer Intelligence 360 status page (https://status.360.sas.com/) currently shows seven components and their respective statuses. These seven components are also used in maintenance notifications and in the RSS feed to indicate which parts of the solution might be affected.   The current components are as follows:   Data Collection Services User Interface APIs Engage Content Delivery Engage Email Delivery Reporting Services SparkPost Email Service   Each of the seven components includes large functional areas of the solution. However, often only a small subset of functionality is affected by maintenance or an incident.   Starting on January 21, 2022, the status page will list 16 components that show more specifically which functionality is affected. The complete list of new components is provided here:   Web and Mobile App Data Collection Accessing the User Interface Changing and Publishing Tasks Managing Workflows and Receiving Notifications Download of UDM Injecting and Receiving Events through the API Gateway Executing Tasks and Segment Maps via the API Upload of Customer Data, Imported Lists, or Transient Files (Includes Uploading of Segments from Classic CI) 360 Plan Related APIs Delivery of Web and Mobile Spot Content Delivery of Mobile Messages (push, in-app) Delivery of Emails Insights Execution of Direct Marketing Tasks and Segment Maps Using Email Overview and Spam Test (Email On Acid) SparkPost Email Service   After this update takes effect, you might need to take these additional actions:   If you currently subscribe to a subset of the current seven components, you must re-subscribe in order to select from the more detailed components. If you currently subscribe to all seven components, you will automatically be subscribed to all of the 16 new components. No action is required. If you implemented an automated notification process based on the subscription emails, RSS feed, or any other integration, you might need to adjust scripts in order to work with the new component names. SAS recommends that you change the scripts ahead of time so that they use both the current and new component names. In this way, the scripts continue to work seamlessly when the new component names are rolled out to production. If you do not refer to the individual component names and receive the emails or integrated feeds, you are not affected by this change. The new component names are automatically listed in any maintenance or incident notification.   For more information, contact your Customer Success Manager.   Deprecated Domains To communicate with SAS® Customer Intelligence 360, you must indicate which specific domains to allow in your firewall depending on the action that you want to perform. The following domains that were required are no longer used:   https://ci-360-data-prod-us-east-1.s3-amazonaws.com https://ci-360-deployment-prod-us-east-1.s3-amazonaws.com https://ci-360-datahub-data-prod-us-east-1.s3-amazonaws.com https://ci-360-udm-data-prod-us-east-1.s3-amazonaws.com https://ci-360-datahub-transfers-prod-us-east-1.s3-amazonaws.com https://ci-360-config-prod-us-east-1.s3-amazonaws.com   Domain List Cleanup in Environment Setup Guide In SAS Customer Intelligence 360: Environment Setup Guide, deprecated URLs were removed from Task 6: Allow Domains. In addition, the lists in these rows were consolidated:   Segment downloads for direct marketing only Segment uploads for direct marketing only Static link node list uploads and downloads for direct marketing only   The new row, called SAS 360 Engage: Direct, lists all the required domains. No new URLs were added.   ... View more

  Specify a Target Audience in Marketing Plans In a marketing plan brief, marketers can now define the target audience that they plan to reach with a specified message and through a specified digital channel. For this function to be enabled, an administrator must configure settings for one or more levels in the planning hierarchy.   When the setting for targeting is enabled for a level, a Targeting page is available on the Details tab of the planning items at that level. For example, if you enable the setting for programs, the Targeting page is available on the Details tab of each new program. On the Targeting page, you can select one or more segments and associate a message and a task type with the selected segment.   Targeting can be configured for planning items only if you have a product license for SAS 360 Plan and SAS 360 Engage: Direct. Note that the targeting feature is currently supported only for direct marketing task types.    (Available in SAS 360 Plan and SAS 360 Engage: Direct)   Enhancements to the User Interface In this release, there are enhancements to the user interface to make the user experience more efficient and consistent:   The settings for custom properties were consolidated on the General Settings=>Custom Properties page. You now use this page to upload the custom properties spreadsheet and manage the tags for custom properties.   On the Orchestration tab for a task, the notifications page is renamed to Job Summary Notifications to match the corresponding label in the General Settings area.   (Available in SAS 360 Engage) ... View more

          Time-Out Setting for Segment Map Executions A new Settings tab is added to business contexts. On this tab, you can specify the number of hours to allocate for on-premises segment map executions. After the specified number of hours elapses, the execution fails and error messages that are associated with the failure are displayed. Any tasks that are dependent on the execution of the segment map also fail. The default setting is 23 hours. Setting the time-out value prevents tasks from being held in a queue indefinitely when system errors cause issues with the execution of an associated segment map. If the segment map or task execution fails due to the time-out setting, the occurrence history for the map or task indicates the failure and provides an informational message.   (Available in SAS 360 Engage: Direct)   All Rows within Jobs Monitor Are Searchable In this release, the search keywords that you enter on the Job Information page are applied to all the rows within the Jobs Monitor and not just those rows on the active page.   Search Option in Jobs Monitor   (Available in SAS 360 Engage: Digital, SAS 360 Engage: Direct, and SAS 360 Engage: Email)   Mark Any Email Link as an Opt-Out Link in the Layout Manager In this release, email designers can set the location of the opt-out landing page by customizing a link in the content of an email, rather than using the tenant configuration.   Typically, the opt-out link is added to an email by the Opt-out Text element, which uses a special merge tag. This merge tag redirects the recipient to a predefined URL that is configured for the tenant. Here is the default opt-out link that is inserted by the Layout Manager:   Sample Opt-Out Link   To define your own custom link to use for the opt-out link, select the link in the Layout Manager and click Configure Tracking. The settings for link tracking now include an Opt-out Link option that can be enabled. Here is the interface for setting the opt-out link:   Configure Link Tracking   Furthermore, there is a new attribute that is added to the link’s element in the resulting HTML of the email content. When you import or export HTML to and from the layout editor, the following attribute is included on links that are configured to use the opt-out option:   data-link-tracking-type="opt-out"   Note: This feature does not remove support for the default opt-out merge tag approach that was also described. Both the merge tag method and this new option are supported, and no migration is required to switch between them.   If you use this new method, the opt-out merge tag can still be used to redirect recipients to the opt-out URL from the tenant configuration.   (Available in SAS 360 Engage: Email)   New Job Summary Notifications for Bulk Email Tasks In this release, you can define a list of email recipients in your organization that you want to be informed about the status of bulk email tasks. The recipients receive an email when the bulk email task starts executing and finishes processing. The email includes related success and failure metrics.   Two levels of configuration are available for the notifications: a global system configuration setting and a task-level setting.   Global System Configuration With global system configuration, you define a list of email addresses and distribution lists that apply to all bulk email tasks. To configure your global list of email recipients, navigate to General Settings=>System Configuration=>Job Summary Notifications. Enable the Bulk Email check box and enter the email addresses or email distribution lists that should receive an email.   In the following figure, Simu, Awkwafina, and recipients in the “Avengers” distribution list receive email updates on all bulk email tasks in the system.   Notification Configuration for Bulk Email Tasks   Task-Level Setting A task-level setting enables you to enter email distribution lists that apply only to a specific task in addition to whoever is defined as a recipient in the global system configuration. To configure the email distribution lists at the task level, open your bulk email task. Navigate to the Orchestration tab and select the Job Status Notifications page. For the Task-specific email distribution list field, enter the specific distribution lists that should receive updates for that email task.   Note: The email addresses from the global settings are visible on this page, but the global list is read-only.   It is recommended that you use only email distribution lists—instead of individual email addresses—for the task-level settings. If you want to update the task-level recipients, you must republish the task. When you republish a task, the data that is used to govern impression limits for the task is reset. For example, if you republish a task that tracks impression limits for users, that means that each customer’s impression limit history for that task data is cleared during the republish. As a result, republishing a task can affect metric accuracy and your task’s contact policies of that task.   In the following figure, recipients in the “Agents of Shield” distribution list will receive the email updates on all bulk email tasks in the system. If, for some reason, the list of task-level recipients needs to be amended over time, you can simply make those changes to the email distribution list itself (that is, outside of SAS Customer Intelligence 360). This means that you do not need to republish your task because you are retaining “Agents@SHIELD.com” in your definition of the task.   Task-Level Notification for Bulk Email Tasks   In earlier releases, job notifications could be configured only in a send agent’s definition. This method is still available. However, if your email programs use a combination of send agents and you want a consistent distribution list, you could consider using this new feature to maintain global or task-level settings.   Currently, both the send agent distribution list and this new method coexist. In addition, job summary notifications are sent to recipients in both. Eventually, the send-agent method is deprecated and summary notifications should be managed solely through the global and task-level settings.   (Available in SAS 360 Engage: Email)   New Job Summary Notifications for Bulk Push Notification Tasks In this release, you can define a list of email recipients in your organization that you want to be informed about the status of bulk push notification tasks. The recipients receive an email when the bulk push notification task starts executing and finishes processing. The email includes related success and failure metrics.   Two levels of configuration are available for the notifications: a global system configuration setting and a task-level setting.   Global System Configuration With global system configuration, you define a list of email addresses and distribution lists that apply to all bulk push notification tasks. To configure your global list of email recipients, navigate to General Settings=>System Configuration=>Job Summary Notifications. Enable the Bulk Push Notification check box and enter the email addresses or email distribution lists that should receive an email.   In the following figure, Jung, Janet, and the recipients in the “Kim’s Managers” distribution list receive the email updates on all bulk push notification tasks that are in the system.   Notification Configuration for Bulk Push Notification Tasks   Task-Level Setting A task-level setting enables you to enter email distribution lists that apply only to a specific task in addition to whoever is defined as a recipient in the global system configuration. To configure the email distribution lists at the task level, open your bulk push notification task. Navigate to the Orchestration tab and select the Job Status Notifications page. For the Task-specific email distribution list field, enter the specific distribution lists that should receive updates for that push notification task.   Note: The email addresses from the global settings are visible on this page, but the global list is read-only.   It is recommended that you use only email distribution lists—instead of individual email addresses—for the task-level settings. If you want to update the task-level recipients, you must republish the task. When you republish a task, the data that is used to govern impression limits for the task is reset. For example, if you republish a task that tracks impression limits for users, that means that each customer’s impression limit history for that task data is cleared during the republish. As a result, republishing a task can affect metric accuracy and your task’s contact policies of that task.   In the following figure, recipients in the “Volunteers” distribution list will receive the email updates on all bulk push notification tasks in the system. If, for some reason, the list of task-level recipients needs to be amended over time, you can simply make those changes to the email distribution list itself (that is, outside of SAS Customer Intelligence 360). This means that you do not need to republish your task because you are retaining “Volunteers@CommunityCenter.com” in your definition of the task.   Task-Level Notification for Bulk Push Notification Tasks   (Available in SAS 360 Engage: Digital)   New Role for Job Summary Notifications A new Alert Notifications Manager role enables users to configure who receives notifications for some task types. This role is useful for users who need to configure job summary notifications in General Settings.   (Available in SAS 360 Engage: Digital and SAS 360 Engage: Email)   Pass Session Information from a Mobile App to an Internal Web View Mobile applications often use internal web views to provide functionality from a website to be used inside the mobile application. In most situations, this setup is used for a checkout or payment process. When your mobile app uses an internal web view, the user behavior in the web view is not collected by the mobile SDK. Instead, the behavior is collected by the SAS tag in the pages that are accessed through the web view.   In previous releases, connecting behavior from a mobile session and a web view's session could be done only by copying cookies and implementing additional code in the web view to process that information. However, the focus on data privacy is making this method less reliable, and companies might place more restrictions around this area in the future. For example, Apple currently disables ApplePay in a web view, even if you copy cookies to a web view and include the extra code to access it.   With this release, you can now connect a mobile app's session to the web view's session through URL query parameters. You can pass the visitor ID (a mobile app's device ID) and session ID through the URL with the _ci_ query parameter. Using this parameter enables you to connect the sets of user behavior and ensure that the user's identification data is also passed on.   This new method of passing user data enables you to use a safe and reliable way of connecting a mobile session with an embedded web view, without triggering any security concerns by the mobile operating system.   (Available in SAS 360 Engage: Digital)   Improvements in Reports This release delivers major improvements in how fast all the reports in SAS Customer Intelligence 360 render, based on a newly updated infrastructure to support reporting. The updated infrastructure also enables SAS Customer Intelligence 360 to expand on capabilities in the future.   There are subtle differences in the labeling and descriptions, along with bigger changes. Here are a few of the major updates:   A new Export Data tab enables you to download data in CSV format. However, there is no longer support to export a report as a PDF. The format of the exported data represents percentages as decimals rather than as the percentages that are shown in the graphs. Reports that had subtabs, such as the Mobile Push Notification reports, now appear in the menu on the left as stand-alone reports.   (Available in SAS 360 Engage: Digital, SAS 360 Discover, and SAS 360 Email)   Workflows Are Enabled for Creatives Designers of creatives in SAS Customer Intelligence 360 can now use workflows to support their collaborative business processes. This feature can be helpful for organizations that want to use workflows for processes that are related to reviewing and approving creatives.   Administrators can enable this feature by navigating to the General Settings=>System Configuration=>Workflows check box.   Enable Workflow for Creatives   When the feature is enabled, a Workflows tab is available for creatives.   Workflows Tab Enabled   (Available in SAS 360 Plan)   Deprecation of Plan Reports on the Insights Tab Starting with the October 21.10 release, the following Plan reports on the Insights tab are deprecated:   Plan Budget Allocations Plan Expense Plan Over Allocated Budget Plan Over Spent   (Applicable to SAS 360 Plan)   Deprecation of API Endpoints in the Design Center As part of improving the stability, reliability, and security of the SAS Customer Intelligence 360 platform, the REST API endpoints in the Design Center are deprecated starting with the October 21.10 release. The endpoints begin with https://design-<region name>.ci360.sas.com.   These endpoints used the less secure Basic Authentication method, and they have been replaced in recent years with more secure endpoints in the external API gateway. These new endpoints require you to generate a JSON Web Token (JWT) and authenticate through the Bearer Token authentication method.   Starting with this release, the only supported endpoints are those that use the external API gateway. Customers need to verify that all REST API calls are made through the external API gateway. The URL begins with https://extapigwservice-.   For more information about the REST API endpoints in the external API gateway, see List of REST API Developer Documentation Links in SAS Customer Intelligence 360: Programming Interfaces in the SAS Help Center.   If you are still using REST API calls from the old Design Center endpoints (for example, https://design-<region name>.ci360.sas.com/SASWebMarketingMid/rest/...), you must update these calls to the corresponding API endpoints in the external API gateway. If you do not update these REST calls, those endpoints will no longer be accessible starting with the October 2021 release.   (Applicable to SAS 360 Discover, SAS 360 Engage: Digital, SAS 360 Engage: Direct, SAS 360 Engage: Email, and SAS 360 Plan)   Deprecation of Cloud Direct Marketing Tasks Starting with the October 21.10 release, cloud direct marketing tasks are deprecated. The cloud direct marketing task type had limited functionality in comparison to the features that are available in the on-premises direct marketing task type. As a result, Cloud Data Hub is no longer available as a selection for the source type for a direct marketing task.   (Applicable to SAS 360 Engage: Direct) ... View more

          Nested Display Conditions in Email Layout Manager In this release, email designers can define display conditions for both an outer element group (a “parent”) and any elements that are placed inside (the “child” elements).   This feature can help save time when you configure the display rules for hiding or displaying personalized email content.   For example, you want to send an email to a customer that showcases their favorite sports figure based on the customer’s first name. You might define the display conditions for the parent element group based on the sport and define a child element that is an image block for each player.   This is the top half and bottom half of an example layout:       Here is an example of display conditions for the parent level (the sport) with the condition Customer State = ‘Football’:     Here is an example of display conditions for the child element (the player) with the condition First Name = ‘David’:     You can then use Responsive Preview to validate that your nested display conditions are working as you expect. Here is an example of how the preview renders when the parent level is ‘Football’ and the child level is ‘David’:     (Available in SAS 360 Engage: Email)   Ability to Interrupt an In-Process Bulk Push Notification Task As part of continued enhancements to executing bulk push notification tasks, users with either the SAS Administrator role in SAS App Central or the Configuration Admin role in SAS Customer Intelligence 360 can now manually interrupt a bulk push notification task that is in process. This feature enables you to stop a task in cases where there is an issue with the task’s processing.   In the task, navigate to the Execution page of the Orchestration tab. If a task is still running and you suspect that you might need to stop it, you can click Stop Task Execution. When you are asked to confirm the action, you are presented with an up-to-date status on your bulk push notification task. The status contains this information:   most recent execution start date and time most recent update date and time most recent metrics: Total Recipients Recipients Processed Recipients Completed Recipients Failed Recipients Skipped Note: These metrics are also available on the Jobs Monitor page.   After reviewing the information, you can decide to stop the processing of the bulk push notification task or let the processing continue.   Stop Bulk Push Notification Task   (Available in SAS 360 Engage: Digital)   Improved Handling of Unreachable Mobile Devices In this release, the number of scenarios in which SAS Customer Intelligence 360 invokes a Notification Failed (notificationFailed) event for an unreachable device is expanded. For example, a Notification Failed event is invoked for devices that are chronically unreachable.   This change also means that SAS Customer Intelligence 360 stops resending push notifications to those devices that have been consistently unreachable. This process streamlines the sending of bulk push notifications and results in fewer repeat errors across different tasks.   (Available in SAS 360 Engage: Digital)   Reorganized General Settings For improved usability, under General Settings, the following items are reorganized or renamed:   The Site Configuration section and all but one of the items in the Data Classification section are combined under one new section called Website Configuration. These items are removed from the Data Collection section and added to the new Website Configuration section: Personally Identifiable Information Form Fields Event Tracking The Analytic section is renamed Applied Analytics. The Engage Optimize item is removed from the Analytics section and added to a new Engage Optimize section. The Global and Product Management sections are combined under one new section called System Configuration. The Messages item is renamed Message Properties. This item is removed from the Content Delivery section and added to the System Configuration section. The User Identities item is removed from the Data Classification section (which is eliminated) and added to a new section called Identity Management. The Export item in the Content Delivery section is renamed Export Templates.   (Your license and role determine the options that you see in General Settings.)   Changes to Configuration Settings for Planning Items Now when you configure settings to enable cost centers, you can select only a single currency. You cannot add and configure multiple currencies for selection in planning items. When cost centers are enabled, the currencies that you might have added are automatically archived.   Settings for configuration of the start month of a financial year and for selection of business units are no longer supported.   (Available in SAS 360 Plan) ... View more

          Occurrence IDs and Occurrence Numbers Are Available for On-Premises Exports   Occurrence IDs and occurrence numbers are now available for on-premises segment maps and on-premises direct marketing tasks. The IDs and numbers can be included in an on-premises export template.   You can include these additional metadata items in either a predefined on-premises export template or when you create an export template. When you set up an on-premises export template, the data items for a segment map occurrence ID and a segment map occurrence number are now available for exports that are used in an on-premises segment map.   Likewise, the task occurrence ID and task occurrence number data items are available for on-premises direct marketing tasks.   (Available in SAS 360 Engage: Direct)   Agent Version Number Is Displayed In General Settings=>Access Points, the new Agent Version display column is added. The value in this column is the current version of the agent that is in use, regardless of the type of access point (general, direct, Optimize, or diagnostics). If the agent version is expired or is nearing expiration, an appropriate warning icon and message are displayed. Agent versions that are more than three versions old are disabled.   This feature enables SAS Customer Intelligence 360 administrators who are responsible for maintaining access point definitions and on-premises agents to view the agent version status more easily.   Agent Version Column   (Available in SAS 360 Engage: Digital and SAS 360 Engage: Direct)   Specify How Long to Store Event Personalization Data In this release, you can specify how long personally identifiable information (PII) from events is available for personalization. This option ensures that attribute values are not stored for longer than necessary, up to a maximum of six months. Along with this feature, SAS Customer Intelligence 360 marks any custom attribute for an event as PII by default, which enables users to set up events without having to remember to specify PII data.   When you create a custom attribute for an event, define the number of days, weeks, or months to temporarily store an attribute for personalization. If the attribute is not PII, clear the check box. Any attribute that is marked as PII is not collected in the UDM tables.   PII Data Storage   (Available in SAS 360 Engage: Digital)   Enhanced Cross-Domain Tracking Some organizations have multiple web domains, and they want to be able to combine user behavior and maintain the same visitor ID, session ID, and identity information across these domains. Previously, SAS Customer Intelligence 360 could perform cross-domain tracking but only through the use of third-party cookies. With browsers increasingly blocking third-party cookies, this method is becoming less useful.   With this release, administrators can enable enhanced cross-domain tracking between two or more domains. When this feature is enabled, the SAS website tag adds session_id and visitor_id as query parameters to cross-domain links. When users click the links, their visitor ID, session ID, and identity information are maintained across domains.   To enable this feature, navigate to General Settings=>Domains and select the domains that you want to enable for enhanced cross-domain tracking. This functionality can also be turned off.   Cross-Domain Tracking   (Available in SAS 360 Engage: Digital)   Add Event Attributes to Triggered Email Tasks In this release, you can select attributes from the trigger event to forward to downstream task events. Task events include sends, opens, clicks, conversions, contacts, and responses.   For example, you can use an external event that contains a tracking code as a trigger for a triggered email task. You can pass that tracking code on the send event and attach the code to conversion events. The attributes are stored in the SAS 360 Engage detail tables in the properties_map_doc column that was added with schema 7. The attributes are available on the task events if the events are sent outside of SAS Customer Intelligence 360.   This functionality enables organizations to perform these actions:   tie behavior to another system, including passing an external tracking code that originates outside of SAS Customer Intelligence 360, such as SAS Intelligent Decisioning or some other engine that makes an offer decision pass a promotion or voucher code that is tied to an individual and understand the user’s behavior pass an attribute that can be used to map to the set of dynamic personalization variables used for the individual without requiring SAS Customer Intelligence 360 to store the personalization variables on the events   Set these attributes on the Orchestration=>Event Attributes tab for triggered email tasks. You can add up to five attributes to be inherited by the task events. The attributes must be part of the triggering event. In upcoming releases, this feature will be available for other task types.   Event Attributes in a Triggered Email   (Available in SAS 360 Engage: Email)   Enable or Disable VML Code for Rounded Buttons In this release, email designers now have the option to disable Vector Markup Language (VML) code that is associated with the rounded buttons in their email content. VML is necessary to support buttons with rounded corners for some Microsoft Office email software, but it might have some unintended consequences. For example, button text might not be displayed properly depending on a recipient’s view settings.   You can now decide how to balance these trade-offs in the Layout Manager when you edit a button element. The Enable VML option, which is enabled by default, keeps the VML code that is associated with rounded buttons. Alternatively, you can disable this option when you do not want your email’s buttons to use VML code.   Enable VML   (Available in SAS 360 Engage: Email)   Edit a Custom HTML Block In Place In this release, email designers have a new way to add and edit custom HTML content from within an email task’s Layout Manager. In addition to selecting an existing custom HTML file from a file system or from the Assets repository, email designers can now edit the Custom HTML code snippets in place.   To edit custom HTML in place, drag the custom HTML element onto an email layout. In the Select Custom HTML Source window, select Edit New HTML.   Edit New HTML   (Available in SAS 360 Engage: Email)   Improved Tracking of Open Rates for Extra-Long Emails In this release, SAS Customer Intelligence 360 now provides the ability to track open rates for extra-long email messages.   Before this release, email-open events were counted based on a tracking pixel that is placed at the bottom of the email message. Although this behavior is industry-standard, it can sometimes lead to under-reporting of open rates for longer email messages, because email recipients might not scroll or swipe to the bottom of the email content in their inbox.   To improve the accuracy of open rates for extra-long emails, SAS now injects an initial-open pixel that is placed at the top of the email content. This pixel ensures that the email-open event is properly captured. However, the initial-open pixel cannot be injected when an email designer defines preview text in the email layout manager.   Because preview text is defined in the email header, there is a conflict with the initial-open pixel. As a result, when you define preview text the end tracking pixel must load in the client in order for an open event to be recorded. Depending on the length of your emails, consider setting preview text based on how accurately you need to track open events.   Email marketers with extra-long email content should weigh the trade-off between having preview text versus more accurate open rate reporting.   (Available in SAS 360 Engage: Email)   Set a Primary Identity Type to Make Identity Value Changes You can set which identity type is the primary identity type to enable companies to make changes to other identity values. The primary identity type becomes the anchor identity, which means that the identity type is the base for any subsequent imports and identity processing. After you set the primary identity type, this type is always used as the primary type and cannot be changed. Currently only the following identity types can be designated as primary:   subject_id login_id customer_id   For example, a company defines three identity types: subject_id, login_id, and customer_id. The company changes its eCommerce system, which then creates new values for its customers’ login_id type.   The company needs to change all the values for the login_id. Previously, this was not an option in SAS Customer Intelligence 360. With this release, if an administrator designates one of the other two identity types (customer_id or subject_id) as the primary type, it is possible to make changes to the values for the other two identity types.   In this case, the company uses subject_id as the main record for the individual, so an administrator designates subject_id as the primary identity type. The company can now import records that update the values that are associated with the login_id. These tables contain sample login IDs before and after updating the values:   Login IDs before Update   Login IDs after Update   Note: To make changes to the other non-primary identity values, the imported data needs to contain the primary identity type as well as the non-primary identity that is being updated.   Set the primary identity type, navigate to General Settings=>User Identities=>Definitions. Select either subject_id, login_id, or customer_id and enable Use as primary identity type.   Primary Identity Type Option   After you click OK, a warning appears to alert users that this action cannot be undone.   (Available in SAS 360 Engage: Digital, SAS 360 Engage: Direct, and SAS 360 Engage: Email)   Specify the Color of a Push Notification Icon in the Android SDK By default, the mobile SDK for Android uses the mobile app's main icon in a push notification. The icon is flattened to a single color. In this release, your mobile app developer can specify a color for the icon by calling the SASCollector.setMobileMessagingIconColor API during initialization of the app.   (Available in SAS 360 Engage: Digital)   Change in How the Mobile SDK for Android Handles Push Notifications IMPORTANT All mobile apps that deploy the mobile SDK version 21.08 or later require specific code changes to avoid disruption to URI or deep link-driven push notifications.   The upcoming release of Android 12 requires a change in how push notification actions are handled in the context of the following push notification life cycle: push notification sent => push notification received => push notification viewable => push notification opened.   Unlike prior mobile SDK releases, in release 21.08 the call-to-action URI information is no longer provided to the app codebase when the notification is opened. As a result of changes to Android 12, when a push notification is received, mobile app developers must provide the Android mobile SDK with a desired Android Activity Intent to be launched when the push notification is opened. The mobile app developer will use the notification URI to determine the correct Intent.   For additional information about changes that affect SAS Customer Intelligence 360, see Anticipated Behavior Changes with Android 12. For Android’s summary of the updates in Android 12, see Behavior changes: Apps targeting Android 12.   (Available in SAS 360 Engage: Digital)   Detach Invalid SAS Device IDs Organizations that maintain a set of test devices might often install, uninstall, and then re-install their mobile app multiple times during their test cycles. That situation can lead to invalid SAS device IDs that remain attached to your data hub ID but never become reachable (due to uninstalling). This situation can lead to a growing list of unreachable SAS device IDs that make management more cumbersome.   To address this situation, the Diagnostics console enables you to detach SAS device IDs that have been cycled through the install and uninstall process and are no longer needed. To detach one or more devices from their associated data hub ID, on the Identity Profile tab, select one or more devices and click .   Detach a Device ID   Detached devices are removed from the table. A device can be detached regardless of its reachability.   (Available in SAS 360 Engage: Digital)   New REST API to Execute Bulk Email and Bulk Mobile Push Tasks Administrators can now execute bulk email or bulk mobile push notification tasks by using the Marketing Execution REST API (/marketingExecution). This REST API enables you to run operations on bulk email tasks that are in the cloud or on premises.   Tasks that are in a published state can be executed by calling the REST API and sending either the task ID or the task name. If the task’s name is not unique, you can send the folderPath parameter to uniquely identify which task should be executed.   Note: By default, the REST API does not execute tasks that have a defined schedule. However, an administrator can send the overrideSchedule parameter to override the defined schedule and execute the task when the request is submitted.   The REST API returns a URL that enables you to check the status of the execution (occurrence). This status gives you the ability to see whether the task executed successfully or failed, and the time stamps for when the task started and finished.   The Marketing Execution REST API enables administrators to execute these tasks with an external scheduler and to manage all the dependencies on demand, such as uploading customer data, imported lists, or transient files after an on-premises warehouse has been updated. This feature provides more flexibility for fluent schedules or delays in processes that need to happen before the task execution.   For more information, see Marketing Execution REST API in SAS Customer Intelligence 360: Programming Interfaces.   (Available in SAS 360 Engage: Digital, SAS 360 Engage: Direct, SAS 360 Engage: Email, SAS 360 Discover, and SAS 360 Plan)   Directly Post Comments to Plan and Workflow Items without Adding Topics With the integration of the Comments Manager in SAS 360 Plan, you can now directly post comments to planning items or workflow items without adding a topic. Previously comments could be posted only within a topic.   Attachments can also be added directly to planning items and workflow items. Adding attachments in a comment post is not supported now.   (Available in SAS 360 Plan) ... View more

With each new release of Android, SAS proactively researches and identifies behavior changes that might impact organizations who use SAS Customer Intelligence 360. In anticipation of the release of Android 12, here are some behavior changes that mobile apps that target Android 12 should be aware of.   Restrictions Imposed on Notification Trampolines   IMPORTANT If you are targeting an early release of Android 12 (specifically, Android 12 API Level S), you must use version 21.08 or later of the mobile SDK. Specific code changes are required to avoid disruption to URI or deep link-driven push notifications. If you use an earlier mobile SDK release, when a user taps the notification to launch the mobile app, there will be no response.   As a result of changes to Android 12, when a push notification is received, your mobile app developer must now provide the mobile SDK with a desired Android Activity Intent to be launched when the push notification is opened. The mobile app developer will use the notification URI to determine the correct Intent. Here is an example:   SASCollector.getInstance().setMobileMessagingDelegate2(   new SASMobileMessagingDelegate2() {   @Override   public void dismissed()  {     //The user has dismissed an in-app message   }   @Override   public void action(String link, SASMobileMessageType type) {     // The type parameter is SASMobileMessageType.IN_APP_MESSAGE.     // The user clicked one of the actions in the in-app message.     // The String parameter is the notification URI that is specified     // in the definition of the creative in SAS Customer Intelligence     // 360.   }   @Override   public Intent getNotificationIntent(String link) {     // The FCM message that is given to the mobile SDK contains a push     // notification.     // The app must provide an Intent to handle if and when the user     // opens the notification.     // The Intent must launch an Activity.     // The String parameter is the notification URI that is specified     // in the definition of the creative in SAS Customer Intelligence     // 360.   Intent intent = new Intent(myContext, DeepLinkActivity.class);     // This is an example of how to send the link to your Activity.   intent.putExtra("my_deep_link", link);   return intent;   } }); Access to Location Information To enable location-based features that support geofencing and beacon capabilities, in addition to declaring these permissions in your mobile app's manifest file, your mobile app developer must request ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION run-time permissions. Previously, only FINE permission was needed. Here is an example:   String[] permissions = { Manifest.permission.ACCESS_FINE_LOCATION, Manifest.permission.ACCESS_COARSE_LOCATION }; activity.requestPermissions(permissions, MY_REQUEST_CODE); Restrictions Imposed by Low App Usage A new app standby bucket called Restricted is added in Android 12. Because it reflects the lowest level of app usage on a device, the restricted bucket has the highest restrictions of all the standby buckets. If your mobile app is placed in the restricted bucket, there are limitations on how many Firebase Cloud Messaging (FCM) messages the device can receive per day. The result is that there can be delays in the receipt of push notifications on that device.   Limitations Imposed by App Hibernation Unused app hibernation is an extension of a feature delivered in Android 11. Beginning with Android 11, if a user does not interact with the mobile app for a period of time (Android documentation specifies "a few months"), the system removes permissions for that app, putting the app in a hibernation state. With mobile apps that target Android 12, not only are permissions revoked, but temporary files are cleared to free up storage space. While in hibernation, the app cannot receive push notifications that are created in SAS Customer Intelligence 360 and sent through the Firebase Cloud Messaging service. When the user interacts with the mobile app again, push notification activity resumes. To prevent disruption of push notification delivery to infrequent mobile app users, consider requesting that the user grant an exception from hibernation and permissions auto-reset.   For Android's summary of the updates in Android 12, see Behavior changes: Apps targeting Android 12.   ... View more

          Manually Enter URL and Selector for Spots and Events   In this release, you can manually enter URLs and selector information when you define a web spot, a JavaScript spot, or a web event. Previously, you had to select page elements by using the inline browser. This new functionality enables you to configure spots and events that reside on pages that require a login or that are part of a single-page application (SPA).   When you create an event or a spot, you no longer need to select elements or pages with the inline browser. Instead, you can manually enter the selector path or URL values.   URL and Spot Selector for Spot and Event Configuration   (Available in SAS 360 Engage: Digital)   Enhanced User Experience within a Personalized Preview in Email In this release, the preview and sample email features are improved on the email task’s Responsive Previews page.   In a previous release, SAS introduced a new preview feature for emails that enabled you to see how personalized emails would render for various inboxes, depending on the values of their sample data. In addition, you could send sample emails from this same page to verify the email output in a real email client.   In this release, the feature to preview emails and send sample emails is more efficient. The interface is improved to provide a more straightforward way for designers to preview each email variation one by one. You can also select up to 50 individual emails to be sent directly to specific recipients. There is now a Preview column that enables you to decide which row of sample data to display in the preview pane. With this new capability, it is easier to preview or send sample test emails.   Personalized Preview for Email     (Available in SAS 360 Engage: Email)   Ability to Interrupt an In-Process Bulk Email Task As part of continued enhancements to bulk email task executions, users with either the SAS Administrator role in SAS App Central or the Configuration Admin role in SAS Customer Intelligence 360 can now manually interrupt a bulk email task that is in process. This feature enables you to stop a task in cases where there is an issue with the task’s processing.   In the task, navigate to the Execution page of the Orchestration tab. If a task is still running and you suspect that you might need to stop it, you can click Stop Task Execution. When you are asked to confirm the action, you are presented with an up-to-date status on your bulk email task. The status contains this information:   most recent execution start date and time most recent update date and time most recent metrics: Total Recipients Recipients Processed Recipients Completed Recipients Failed Recipients Skipped   Note: These metrics are also available on the Jobs Monitor page.   After reviewing the information, you can decide to stop the bulk email task’s processing or let the processing continue.   (Available in SAS 360 Engage: Email)   Separation of Task Execution and Publish for Bulk Push Notification Tasks In this release, when you create a bulk push notification task, you have the following options:   Publish and Run Now, which executes the task and sends push notifications. Publish Only, which makes the task active but does not execute it. Push notifications are not sent when you publish the task. Push notifications are sent only when you run the task. This option is useful if you want to use an API to execute the task. In earlier releases, before push notifications were sent for a bulk push notification task, the bulk push notification task had to be executed in a separate step after the task was published.   Note: In this release, the capability to interrupt an in-process bulk email task is available. This same capability is planned for bulk push notification tasks in a future release. (Available in SAS 360 Engage: Digital)   Improved Image Rendering of Mobile In-App Messages In the 21.03 release, changes were made to improve the rendering of large images for mobile in-app messages to take advantage of advanced screen displays on newer mobile devices.   In this release, you see an even more accurate conceptualization of images because of additional improvements to image-handling in the user interface. Previously, images could appear cropped; now, images are scaled to fit. Here we use an image of Stonehenge to compare the conceptualization of the image in the user interface before release 21.07 and now:   Sample Rendering before Release 21.07   Sample Rendering in Release 21.07   Note: It is recommended that you test your in-app message creatives across a variety of mobile devices to ensure that they meet your expectations. (Available in SAS 360 Engage: Digital)   Copy and Paste Nodes across Segment Maps You can now copy and paste nodes from an on-premises segment map to another on-premises segment map or from a cloud segment map to another cloud segment map. The segment maps must be within the same browser tab and on-premises segment maps must be in the same business context.   Any node can be copied and pasted. Pasted nodes retain their settings, but the status is reset and the counts are cleared. You can also copy and paste Process nodes from a direct marketing task to another direct marketing task.   Copying and pasting increases productivity because it enables you to use complex node settings and selected sections of segment maps and direct marketing tasks without re-creating existing settings.   (Available in SAS 360 Engage: Direct)   On-Premises Direct Marketing Task ID Available in the Macro Variables Table You now have access to the on-premises direct marketing task ID for post-processing purposes in the macro variables table. The ID name is TASKINFO, TASKID. In addition, TASKINFO, OCCURNUM is available for the occurrence number and TASKINFO, OCCURID is available for the occurrence ID.   These new values in the macro variables table are typically used as input values into post processes.   (Available in SAS 360 Engage: Direct)   Create Summary Report Documents for On-Premises Segment Maps You can now create and access documents that contain information about the contents of your on-premises segment map. These documents can be automatically created with each successful execution of the on-premises segment map or can be created on-demand. You can share these documents or use them as audit records for segment map executions.   Each document is created as a Microsoft Excel spreadsheet that can be downloaded to a local file system for viewing. The spreadsheet contains various tabs that represent the contents of the on-premises segment map, such as summary information, node details, segment sizing details, and execution history. If the document is created on-demand, you can specify that the spreadsheet contain a resizable image of the on-premises segment map.   The option to create the document is on the Properties tab for the on-premises segment map. A Report Setup option enables you to specify the sections of the document that you want to create. Documents that are created during scheduled executions are available on the Attachments tab in the on-premises segment map and can be downloaded for viewing.   Sample Report   Sample Microsoft Excel Output   (Available in SAS 360 Engage: Direct)   Selection of Value and Display Name for Custom Properties within Planning Items and Workflows In this release, you can now add a display name to a custom property value in a planning item or in a workflow. This feature enables you to provide a more descriptive label for the value in the user interface and retain a record of the unique value.   Note: This functionality will also be supported for Assets in a future release.   (Available in SAS 360 Plan)   Improved User Interface for Folders in Assets In this release, the user interface of the folder structure in Assets has been updated. The new user interface for folders can be viewed when you attach assets in planning items and workflows and when you catalog files in workflows.   (Available in SAS 360 Plan) ... View more

          Recommended Method for Inserting the SAS Tag in HTML In the user interface, the General Settings => Site Configuration => SAS Tag Instructions page is updated to describe how to insert the SAS tag in your HTML by using JavaScript preloading, which is now the recommended method.   Note: The updated instructions only describe the recommended method for how to insert the SAS tag in your site's HTML. This change does not modify the SAS tag or its functions. The SAS tag continues to operate normally when it is loaded based on previous instructions from the user interface or from SAS Customer Intelligence 360: Administration Guide. JavaScript preloading can provide a performance boost on modern browsers, and it enables you to queue events through version 2 of the JavaScript Events API before the tag is fully loaded. Browsers that do not support preloading or the async attribute safely fall back to synchronous operations to load and execute the SAS tag.   (Available in SAS 360 Discover and SAS 360 Engage: Digital)   Use Default Text for Personalization Variables Beginning with this release, you can substitute text for the personalization variables. In previous releases, when you used a creative in a task and that creative contained a personalization variable, you had to select a merge tag to use in place of the variable. Now, you can enter the text in the Default Value field without selecting a merge tag. This feature results in the task delivering the text in all instances of the creative that it delivers.   When you build a creative that contains multiple personalization variables, some of those variables can be replaced with merge tags and others can be replaced with static text. As a result, you can use one creative in multiple tasks where some of the content might be dynamic to the user and some of the content is based on the task.   The following types of creatives and tasks support default text substitution:   HTML creative Plain text creative Web tasks (except Recommendation tasks) Mobile spot tasks External system tasks Email tasks (only content blocks with HTML creatives)   (Available in SAS 360 Engage: Digital)   Add Attributes to Task Events In this release, users of web tasks, mobile spot tasks, and external system tasks can designate attributes from targeting or triggering events to be forwarded to downstream task events such as impressions viewable, conversions, contacts, and responses.   For example, you can use an external event that contains a tracking code as a trigger for an external system task. You can pass that tracking code on the outbound event and attach the code to conversion events. The attributes are stored in the SAS 360 Engage detail tables in the properties_map_doc column that was added with schema 7. The attributes are available on the task events if the events are sent outside of SAS Customer Intelligence 360.   This functionality enables organizations to perform these actions:   tie behavior to another system, including passing an external tracking code that originates outside of SAS Customer Intelligence 360, such as SAS Intelligent Decisioning or some other engine that makes an offer decision pass a promotion or voucher code that is tied to an individual and understand the user’s behavior pass an attribute that can be used to map to the set of dynamic personalization variables used for the individual without requiring SAS Customer Intelligence 360 to store the personalization variables on the events Set these attributes on the Orchestration => Event Attributes tab for web tasks, mobile spot tasks, and external system tasks. You can add up to five attributes to be inherited by the task events. The attributes must be part of the triggering or targeting event. In upcoming releases, this feature will be available for other task types.   (Available in SAS 360 Engage: Digital)   Tasks in Attribution Analysis With this release, you can now include tasks in the attribution analysis of data views. Marketers have always wanted to better understand the customer journey and the actions that are driving conversions to continuously improve marketing efficiency. Previously, you could see only the impact of traffic sources on driving conversions. Now you can also understand the value of your SAS Customer Intelligence 360 tasks in the customer journey.   With the addition of tasks to attribution analysis, you can get a more complete view of the factors that contribute to conversions and how traffic sources and tasks work together to drive conversions. By understanding the marketing efforts that are influencing the conversions, you can better optimize how they acquire and communicate with prospects and customers.   To enable this feature, navigate to the Attribution tab for the data view and enable attribution analysis. On the Default Parameters page, select the Tasks check box, and then select up to 10 tasks to include in the analysis. Only tasks that use that data view as a primary metric appear in the list of tasks to choose from.   Parameter Settings for Tasks   When enough data is collected, you can toggle the analytical results to look at only tasks, only traffic sources, or both. In addition, you can select which model results to include in the visualizations.   Traffic Source and Task Attribution Results (Available in SAS 360 Engage: Digital, SAS 360 Engage: Direct, SAS 360 Engage: Email, and SAS 360 Discover)   Detect and Edit Detailed Link Label and Group Values in Custom HTML In this release, email designers have increased flexibility when viewing and editing the link label and group values that are associated with their email.   In addition to viewing and configuring link tracking in the Configure Individual Link Tracking window of an email’s Layout Manager, you can now verify and edit these link settings from inside a Custom HTML element.   After you import a Custom HTML element into the email content, SAS Customer Intelligence 360 automatically detects any pre-existing settings in that HTML code that are related to link tracking. For example, you might examine an HTML code snippet for a button called “Get Offer” that was already set up in the Layout Manager with the call-to-action link https://www.sas.com/offer. When you review the code in HTML format, you would notice these references for link tracking:   data-link-tracking-enabled=”true” data-link-tracking-label=“July Offer” data-link-tracking-group=”Summertime Promotions” data-link-tracking-id=”1” (This number is assigned by SAS and must be unique per email.)   This new feature enables you to configure detailed tracking more quickly for any links in an email. This feature can also improve your efficiency, and for emails that contain a large number of links, save much-needed time.   (Available in SAS 360 Engage: Email)   Reference Custom Properties by Using Custom Property Tags Custom property tags enable you to reference custom properties without knowing the custom property name. For example, this feature can be useful in an export template for an on-premises direct marketing task or in the Export node for an on-premises segment map.   In these situations, you might add a custom property tag (instead of the specific custom property) as a data item to the export table. The custom property tag acts as a placeholder for the value of a custom property. When the task is run, the custom property tag is resolved to the actual value, which is then inserted into the output data.   You can use custom property tags in activities, tasks, segment maps, segments, and messages. The types of custom property tags that can be defined are text, numeric, date, and Boolean.   Custom Property Tag   Before you can associate custom property tags with an item, you must define the tags in General Settings => Data Collection => Custom Property Tags and ensure that the tags are associated with one or more custom properties in the custom property spreadsheet.   (Available in SAS 360 Engage Direct)   Table Management User Interface In earlier releases, the only way you could define tables in SAS Customer Intelligence 360 was by manually creating JSON descriptors and using the REST API to import them. As a result, it was easy to make mistakes when you defined tables, and it was not always clear when specific JSON properties should be used.   In addition, the REST API was the only way to view the import history for the corresponding data that was uploaded for these tables.   In this release, SAS Customer Intelligence 360 introduces a new user interface to create and manage tables. You can access the interface in General Settings => Data Collection => Table Management.   The new table management interface enables you to perform these actions:   create tables and set properties on the columns in the table through a user-friendly interface. edit existing tables. For example, you can add a new column, modify some properties, and edit labels. select a table to import data. view the table’s JSON definition and copy it. review the import history for a table. You can view all of the import history for a table, regardless of whether an import job was initiated through the user interface or the REST API.   Note: Previously, customer data that was imported through the user interface could be verified on the General Settings => Data Collection => Data Sources page. These statuses are now available from the Table Management page.   The table management interface enables you to create tables more quickly and avoid common mistakes that the manual process might introduce.   Table Management   (Available in SAS 360 Engage: Digital, SAS 360 Engage: Direct, and SAS 360 Engage: Email)   Configure Cost Center Codes In this release, plan administrators can add a cost center code that uniquely identifies each cost center record, which is listed in General Settings for Plan. In addition to the existing cost center names, cost center codes can be used as an alternative way to reference various cost centers that are added to the system.   Cost Center Codes   (Available in SAS 360 Plan)       ... View more

            Send Sample Test Emails from a Personalized Preview of an Email Task In this release, email designers can send sample emails from within an email task that is still in the Designing state. This feature saves time by enabling you to review and validate how personalized email content is rendered across a variety of real email inboxes.   With this feature, you can perform these actions:   send preview emails without publishing the task send up to 50 versions of an email at one time repeat the same email address, in case you want to compare different personalization scenarios in the same inbox   You can use this new feature to complement the existing preview features that are available in other areas of an email task.   Responsive Previews     (Available in SAS 360 Engage: Email)     Improved User Experience within Detailed Link Tracking   Recommended Global Groups for Link Tracking In this release, an administrator can create a set of global groups for link tracking. The groups that are added to the global list are available for users to select when they configure link tracking in an email task. Manage group names on the Link Tracking Groups page of General Settings.   Use global group names to encourage consistent nomenclature when users add link groups to email tasks. Consistency in group names allows for more consistent Link Engagement Reporting.   Note: This global list does not restrict or enforce rules on group names in a specific task. Email designers can still enter any names that they want in a task.   (Available in SAS 360 Engage: Email)   Configuring Link Tracking To improve how you configure detailed link tracking, improvements were made to the user interface where you configure the Link Label and Link Group in an email task. It is now easier to edit a group name and create a group from the interface.   (Available in SAS 360 Engage: Email)   Improved Processing for Large Numbers of Display Conditions In this release, SAS Customer Intelligence 360 improves the way that display conditions for email content are processed. Large numbers of display conditions can be evaluated much faster, which improves how quickly bulk emails can be sent.   (Available in SAS 360 Engage: Email)   Separation of Task Execution and Publish for Bulk Email Tasks Previously, before emails were sent for a bulk email task, the bulk email task had to be executed in a separate step after the task was published. Now when you create an email bulk task, you have the following options:   Publish and Run Now, which executes the task and sends emails. Publish Only, which makes the task active but does not execute it. Emails are not sent when you publish the task. Emails are sent only when you run the task. This option is useful if you want to use an API to execute the task.   (Available in SAS 360 Engage: Email)   Expanded Merge Tag Functionality for Mobile Messages In this release, SAS Customer Intelligence 360 supports a larger variety of merge tags that you can use to personalize mobile push notifications and mobile in-app messages. This feature adds similar personalization capabilities that are available for web and mobile spots, providing more consistency across messaging.   Merge tags are now available in the following components of these creatives:   Push notification creatives: Merge tags can be inserted in push notification title text, notification text, and the notification URI when the notification action is set to “Link to application”. In-app message creatives:  In a small in-app message, merge tags can be inserted in the body text and in the banner URI when the banner action is set to “Link to application”. In a large in-app message, merge tags can be inserted in the header text, body text, button labels, and in the button URI when the button action is set to “Link to application”.   In a creative, you can supply a default value to use if the merge tag cannot retrieve data. For example, if the user’s identity is not known, you might replace the name with “Valued Customer”.   You can use data that is specified in the task itself (not in the creative) to supply your merge tags. This functionality is enabled by personalization variables that act as placeholders in the creative design process. When you include the creative in a task, you can select the source data to replace the variables. Due to differences in how bulk tasks and triggered tasks are orchestrated, the available source data to replace variables varies across task types.   Here is a summary of the data that can be used as the source for merge tags for each task type:   In-app messages and triggered push notifications: uploaded customer data (except transient files) customer behavior events or data views; more specifically, the attributes that are specified for the selected task targeting or task triggering events or data views Bulk push notifications: uploaded customer data Note: The attributes of customer behavior and data view events are selectable only from within a task. In the creative, insert a variable. In the task that includes the creative, replace the variable with an event or data view attribute after you specify a task targeting or task triggering event.   Here are some important caveats:   Pre-existing push notification creatives and in-app message creatives that use merge tags continue to work, even with a task republish. However, once a creative is republished, regardless of whether it is included in a task, the new merge tag behavior applies. You should not apply the newer merge tags to those pre-existing creatives. Instead, it is strongly recommended that you build new creatives that use the new merge tag features. When using uploaded customer data, make sure the channelContactInformation property for the data items in your customer tables is set to true.   (Available in SAS 360: Digital)   Specify Custom Properties for Invoices You can now set your own custom properties for invoices. This feature gives you the flexibility to define attributes that are specific to your business needs.   Note: SAS 360 Plan already supports custom properties for planning items, workflows, assets, and commitments. (Available in SAS 360 Plan)   Attach Files to Vendors In this release, you can attach files to the vendor details that you add in General Settings => Plan => Vendors. This enhancement means that electronic files in supported formats such as .pdf, .docx, and .xlsx, or asset files that represent vendor information, or supporting documentation, can now be directly associated with your vendor record.   (Available in SAS 360 Plan)   Add Columns to a Transient Descriptor Previously, you could add columns only to tables (data descriptors) that contained persistent customer data, and you could not add columns to an existing transient descriptor. In this release, you can now add columns to a transient descriptor, which means that you no longer have to create a transient table to add an additional column.   You can add a column by using the PATCH call to the marketingData/tables/<table ID> endpoint in the Marketing Data API. The call should include the table’s definition in the JSON body, including the new column that you want to add.   Note: When you add a new column to a transient table, the system deletes the existing data file that is associated with that transient table. You must re-import the transient data file to use it in the system.   (Available in SAS 360 Engage: Digital, SAS 360 Engage: Direct, and SAS 360 Engage: Email)   Add New Values to the List of Metadata Values in Criteria, Map, or Split Nodes You can now manually add a metadata value for nominal data items to the list of selectable metadata values for a Criteria, Map, or Split node.   This new feature enables you to enter a metadata value that exists in the on-premises data before the value has been included in a metadata upload.   The custom metadata values can now be added to Criteria, Map, or Split nodes. In a Criteria node, the count for a custom value can also be included.   Custom Values   (Available in SAS 360 Engage: Digital, SAS 360 Engage: Direct, and SAS 360 Engage: Email)   Monitor the Updating of Counts in an On-Premises Segment Map You can now use the Update Counts Progress page to monitor the updating of counts in an on-premises segment map. The information about this page enables you to view how counts are progressing and to gauge the time that is needed to complete the count update based on the progress results.   To open the page, click the Show update counts progress icon on the toolbar in the segment map workspace while a count is being updated. A progress bar appears, which indicates the completion of the count updates by percent. The status of the individual counts also appears in a table that includes these default columns: Step, Name, Type, Start Date, Duration, and Status. You can insert additional columns in the table. Click Download Details to download a JSON file that includes the contents from the Progress table so that you can create a record of count updates.   (Available in SAS 360 Engage: Direct)   Time-Based Option for Clearing a Direct Marketing Agent’s Request Queue Administrators can now define a time-based option to discard requests after a direct marketing agent is brought back online. This feature is helpful when the direct marketing agent is brought down to upgrade to a new version of the agent. In this case, you might decide that streaming requests older than 24 hours should be discarded when the direct marketing agent is reactivated.   To enable this option, select a direct marketing access point from the General Settings => External Access => Access Points page. On the new Queued Requests tab, you can enable the option to clear the request queue when coming back online. You can choose to clear all queued requests or requests that are older than a specific time period. The default is set to 24 hours. Requests can include executions or update count requests for on-premises segment maps and tasks.   (Available in SAS 360 Engage: Direct)   Enhanced Search with Elasticsearch Support for Assets, Planning Items, Invoices, and Commitments Implementation of Elasticsearch support enhances the search experience, which enables you to search through very long lists and find items quickly and easily. This feature provides pagination of item lists and also gives improved search results for a group of search keywords as well as subsets of keywords. Note that pagination is currently supported for assets, invoices, and commitments, but not for planning items.   Elasticsearch support is not available by default. The feature can be enabled by request. Contact your SAS technical representative to modify the property that enables the feature for your organization.    (Available in SAS 360 Plan) ... View more

              Select a Segment Map for an On-Premises Direct Marketing Task and a Bulk Email Task On the Targeting tab for an on-premises direct marketing task or a bulk on-premises email task, you can now select an on-premises segment map. When you select the segment map, all segments within that map are automatically included. There are two new columns to help you understand the context of a specific segment: the segment map name and the folder path.   Select a Segment Targeting Tab Before this feature was introduced, you could select segments only one at a time in a segment map.   This feature is helpful when the segment map contains many segments and you want to make sure that all of the segments are selected each time.   (Available in SAS 360 Engage: Direct and SAS 360 Engage: Email)   Monitor the Execution of an On-Premises Segment Map In this release, you can monitor the execution progress of an on-premises segment map. The feature is available on the Execution page of the Orchestration tab for an on-premises segment map.   Execution Page   When the execution of a segment map begins, a progress bar displays the percent completion status for the map execution. The tasks that are shown in progress are the task sequence steps in the segment map execution. Because the task sequence steps are derived from all the segment map nodes, the steps might not exactly correspond to each node. Instead, each task sequence step indicates the current execution step in the segment map. During execution, a table is created that dynamically displays rows for each step and also displays the Name, Type, Start Date, Duration, and Status columns for each step row. Additional columns can be added to the table display. As the execution progresses, the table rows are updated. If an execution step fails, that step is flagged in the progress bar and in the table. You can use the task ID for that failed step to search the log for details. In addition, a download details option is available that creates a downloadable JSON file that contains all the execution steps and the associated data for each step. The progress information is retained until the next execution of the map or for a specific time period that is displayed on the Execution page.   This feature provides insight into the progression of the execution steps for an on-premises segment map while the map is executing. You can use the information from the execution step table to compare the duration of the individual execution steps and the overall map execution time. To reduce the time to resolve an execution failure, copy and paste the task ID of the execution step that failed into the log file.   (Available in SAS 360 Engage: Direct)   Access the Run Now Option for On-Premises Direct Marketing Tasks or On-Premises Segment Maps The Run Now option is now available on any page from the Orchestration tab for on-premises direct marketing tasks or on-premises segment maps. In previous releases, the Run Now option was available from only the Execution page on the Orchestration tab.   If a task or segment map already has a defined execution schedule, you are notified of the schedule before you are prompted to proceed with the Run Now option.   (Available in SAS 360 Engage: Direct)   New Data Item Limit for Information Maps You can now add up to 2,000 data items to an information map that is used for on-premises data. This limit reduces performance issues that can occur when the information map includes a large number of data items.   (Available in SAS 360 Engage: Direct)   Send an Email to SAS Technical Support from the User Interface In this release, you can use the Contact Support link throughout the user interface to generate a new SAS Technical Support ticket. To see an example of the link, click the user button on the application bar and select About.   When you click the support link, SAS Customer Intelligence 360 creates an email that you can send to support@sas.com. Before you send the generated email, include details such as your contact information and specifics about the issue that you are reporting.   The Contact support shortcut is accessible from the following areas in the application:   About menu Diagnostics Console Task Jobs Monitor   (Available in SAS 360 Engage: Digital, SAS 360 Engage: Direct, SAS 360 Engage: Email, SAS 360 Discover, and SAS 360 Plan)   Data-Type Awareness for Conditional Merge Tags Email-based merge tags play an important role in personalizing email content for each of your customers. In this release, the logic for conditional merge tags can consider the data type for data items that you specify in the merge tag’s conditional test. This feature enables you to define conditional merge tags that are more precise.   By having merge tags that are data-type aware, email marketers can do these things:   control the formatting that is used when applying these merge tags as text in their email content consider the type of data when setting logic for conditional merge tags and display conditions for block selectors   For example, you can compare numeric types to display different personalization data based on the total value of items in a customer’s online Shopping Cart: Display the 20% coupon if total Cart value > 50; otherwise, display 10% coupon   In addition to improving the merge tag processing for published email tasks, data-type awareness is also enabled for the Responsive Preview section of an email task’s Review tab. This feature ensures that you can verify the conditional logic and output in a sample preview before you run the email task.   Note: This feature is not enabled by default. Data-type awareness depends on the data types that you have defined in your customer tables, and changing the behavior might affect your current merge tags. Contact your SAS Global Customer Success Manager to discuss this option and how to enable it for your environment.   (Available in SAS 360 Engage: Email)   Responsive Previews for More iOS 14 Devices In this release, the responsive preview feature for email tasks now includes support for additional devices on iOS 14. This feature enables you to ensure that email content is rendered correctly when it is delivered to customers.   Responsive previews are now supported for these devices:   iPhone XR iPhone XR Dark Mode iPhone SE - 2nd Generation iPhone 11 Dark Mode (Available in SAS 360 Engage: Email)   Time-Based Option for Clearing a General Agent’s Event Queue Administrators can now define a time-based option to discard events after a general agent is brought back online. This feature is helpful when the general agent is brought down to upgrade to a new version of the agent. In this case, you might decide that streaming events older than 24 hours should be discarded when the general agent is re-activated.   To enable this option, select a general access point from the General Settings=>External Access=>Access Points page. On the new Queued Events tab, you can enable the option to clear the event queue when coming back online. You can choose to clear all queued events or events that are older than a specific time period. The default is set to 24 hours.   General Agent Event Options   (Available in SAS 360 Engage: Digital, SAS 360 Engage: Direct, SAS 360 Engage: Email, SAS 360 Discover, and SAS 360 Plan)   Attach Files to Commitments and Invoices With this release, you can attach files to commitments and invoices within your planning items. This enhancement means that electronic files in supported formats such as .pdf, .docx, and .xlsx, or asset files that represent purchase orders, invoices, or supporting documentation, can now be directly associated with commitments and invoices.   (Available in SAS 360 Plan)   Specify Custom Properties for Commitments You can now set your own custom properties for commitments. This feature gives you the flexibility to define attributes that are specific to your business needs.   Note: SAS 360 Plan already supports custom properties for planning items, workflows, and assets.   (Available in SAS 360 Plan)   Specify Which Users Can Access and Use a Workflows Template In this release, administrators can restrict access to specific workflow templates so that only authorized users can use the template to initiate workflows.   To configure access, navigate to General Settings=>Workflow, select the active workflow template, and click the pen icon   to configure it. On the Template Access tab, click Customize access, and then click Add Users or Groups.   Users or groups that are granted access can use the template to create workflows.   Note: This feature does not impact or restrict admin users from importing or editing workflow templates.   (Available in SAS 360 Plan)   Configure Template Settings to Specify Default User Permissions in Workflows Administrators can now configure workflow template settings to specify default permissions for users and groups in a workflow.   To set default permissions, navigate to General Settings=>Workflow, select the workflow template, and then click   to configure it. On the Default Permissions tab, click Customize permissions. Click Add Users or Groups and specify View or Edit permissions.   Users or groups with specified permissions are automatically added as default users and groups in each workflow that is created from the template. Users with sufficient access can edit a specific workflow to override the default settings.   (Available in SAS 360 Plan)   Specify Which Users Have Access to a Workflow In this release, administrators and workflow initiators can specify users and groups that can access a workflow. Administrators and workflow initiators can customize permissions in a workflow by adding and modifying permissions for users and groups.   To set permissions, navigate to the Permissions tab in a workflow and click Customize permissions. Click Add Users or Groups and assign View or Edit permissions.   From My Workflows on the navigation bar, the signed user can see the workflows that they created and the workflows for which they have View or Edit permissions. By default, administrators can view and edit all workflow and approval instances.   (Available in SAS 360 Plan) ... View more

            Improved Usability in an Activity To improve the user experience when adding a task to an activity, more tasks are displayed in the Add Task window.   (Available in SAS 360 Engage: Digital and SAS 360 Engage Direct)   Improved Large Image Rendering for Mobile In-App Messages In this release, changes are made to improve the rendering of large images for mobile in-app messages. The mobile SDK now gives preference to larger images on newer devices. To ensure that images are rendered correctly, use the latest mobile SDK, test across a variety of devices, and choose the graphic that works best across all devices.   (Available in SAS 360: Digital)   Control the Display of Message Types When you create a message, the Properties tab of the message displays a Type field. The field lists the options for message types. Now, you can configure settings to show or hide the Type field in the message properties. If you choose to hide the Type field, you can use the user-defined categories and custom properties fields to display a customized list of options for message types. This feature can be accessed from the navigation bar by selecting General Settings => Content Delivery => Messages.   (Available in SAS 360 Engage)   New Mobile App Events In this release, you can use the SAS Customer Intelligence 360 user interface to define events that capture behaviors in a mobile app, such as making purchases or adding a product to a cart. These are the events that you can now create specifically for mobile apps:   These eCommerce events: Add to Cart Cart View Checkout View Product View Purchase View Internal Search Promotion When you create an event, you specify the event type (for example, Add to Cart) and an action, which in this case, is Mobile App Action. You provide a unique mobile event key that both you and your mobile app developer use, and custom attributes (if desired).   The new mobile events are available for selection throughout SAS Customer Intelligence 360, including for these activities:   Creating data views Creating cloud segments Defining metrics Targeting the audience for a task Triggering a task or activity   Data from these new mobile events flows into the following tables in the Unified Data Model (UDM):   Product View to the PRODUCT_VIEWS table Add to Cart to the CART_ACTIVITY_DETAILS table Cart View to the ORDER DETAILS and ORDER_SUMMARY tables Checkout View to the ORDER DETAILS and ORDER_SUMMARY tables Purchase View to the ORDER DETAILS and ORDER_SUMMARY tables Internal Search to the SEARCH_RESULTS table Promotions to the PROMOTION_USED and PROMOTION_DISPLAYED tables New columns are added to the UDM tables to be able to distinguish mobile events from web events.   (Available in SAS 360: Digital)   Expanded Options for Triggering In-App Messages Based on Event Attributes In this release, you can orchestrate the sending of personalized in-app messages to mobile app users based on an additional set of trigger events and their associated event attributes.   In the previous release, you could specify a trigger condition based on the value of the trigger event attribute for Standard events (such as Click-Through, Page View, and Mobile App Focus) and for Custom mobile events. In this release, you now choose from an expanded list of events that are defined specifically for mobile app behaviors:   These eCommerce events (only the mobile app eCommerce events): Add to Cart Cart View Checkout View Product View Purchase View Internal Search (only the mobile app Internal Search events) Promotion (only the mobile app Promotion events)   Note: For these events to have maximum effect as triggers, the events must be deployed in the mobile app code by using the mobile SDK version that is applicable to release 21.03 and configured in SAS Customer Intelligence 360. After the new mobile app code is available for download in the Play and App stores, respectively, it might take some time before the trigger events are available for orchestration. (Available in SAS 360 Engage: Digital)   Monitor Job Execution and Delivery Progress of Bulk Push Notification Tasks In this release, the Job Information page includes more details about bulk push notification tasks. This feature enables you to track the progress of tasks and to review specific operational metrics.   To access the Job Information page, on the Tasks page, click  . The Task Execution tab provides the following information:   Total Recipients Recipients Completed Recipients Failed Recipients Processed Recipients Skipped    When looking at Recipients Failed and Recipients Skipped, click    to see these additional details about the reason for failure and how many recipients are affected:   Failed to Create Message Failed to Send Message Device Endpoint Invalid Device Recently Logged Out Impression Limit Device Token Revoked Device Has Not Registered a Token   (Available in SAS 360 Engage: Digital)   Send Test Push Notifications as Part of Diagnostics When mobile devices are not receiving push notifications, it is important to understand why and if there is an issue that needs to be addressed. In some cases, the mobile device is not technically reachable. (For example, this issue can occur if the user opted out of push notifications for your app or the app was uninstalled.)   In this release, there is a new diagnostic feature that helps you identify the source of the issue by determining the validity of the device’s token. For example, if you confirm that the device can technically receive a push notification, you can rule out an “invalid token,” and then investigate other potential origins of the issue, such as the recipient having exceeded impression limits.   To use this capability, navigate to General Settings => Content Delivery => Diagnostics. After you enter your ID type in the console, you can see associated mobile device IDs on the Identity Map tab. If you select the Table view and scroll to the Mobile devices table, you can select multiple device IDs, and then press Submit Test. If the mobile device is technically reachable, you see a test push notification that says, “Push test successful < current date/time UTC > for Device ID < device ID >”.   Here is an example:   Sample Test Message   (Available in SAS 360: Digital)   Imprint URL Included in Email Send Events Email send events now include an imprint URL so that you can audit or reference email imprints that were generated in the past 90 days. This imprint URL enables you to view the exact email content that was received as part of an email task.   You can retrieve the imprint URL for each recorded event from the EMAIL_SEND table in the Unified Data Mart.   (Available in SAS 360 Engage: Email)   Set the Email Background Color You can now set specific conditions that control the background color for the entire body of an email. This feature enables you to personalize an email’s theme for recipients who meet a specific business condition.   To set a background color based on business cases, you can use conditional merge tags and specify the corresponding color (by name or color code). For recipients who do not meet the business conditions, the email can use the background color that you set as the default.   (Available in SAS 360 Engage: Email)   Hard Bounce Events for Malformed Email Addresses In this release, SAS Customer Intelligence 360 generates a hard bounce event for emails that are addressed to malformed email addresses.   When an email generates a hard bounce event due to a malformed address, the system adds an event attribute that specifies the hard bounce as a “bad address”. You can use these events to help identify and remove email addresses from your database.   (Available in SAS 360 Engage: Email)   Enhanced View of Expenses in Planning Item Financials You can now view the cumulative expenses for a planning item and its associated child items in the hierarchy below it. The rolled-up information about the allocated expense amounts for all the dependent items is now represented through a tree view when you view totals on the Expenses page. In addition, you can hide or display the available financial columns to customize your views.   (Available in SAS 360 Plan)   Associate Planning Items with Tasks and Activities In this release, you can directly associate a planning item with a task or an activity if you have a license for SAS 360 Engage: Digital and SAS 360 Plan. Planning properties must already be added to the task or an activity that you want to associate with the planning item.   To access the new option in a task or activity, your view must be in Planning mode. On the Properties page of the Details tab, a new Parent planning item field is added. The system displays a filtered list of planning items that are available for association based on the planning start and end dates and either the business unit or the currency settings.   The planning item that is associated with the task or activity is designated as a parent level object for the task or activity in the marketing hierarchy.   (Available in SAS 360 Plan and SAS 360 Engage: Digital)   View Upcoming Workflow Task Assignments If you are assigned to workflow tasks, you can now view and plan for upcoming task assignments to workflows that are not yet active. In addition to the pending tasks, you can filter and view workflow tasks with a non-initiated status from the list view and the calendar view. For group assignments, this feature can be accessed by clicking   on the My Workflow Tasks page.   (Available in SAS 360 Plan)   Schedule a Connector Endpoint to Activate at Specified Hours or Minutes Administrators who set up connectors and endpoints have several options to configure a schedule for activating the endpoint. The administrator can specify a one-time schedule or a recurring schedule by selecting various frequency options such as daily, weekly, and monthly.   In this release, the recurring schedule of a connector endpoint can be specified by the number of hours (1 to 23) or the number of minutes from the listed options. This feature provides more flexibility in scheduling API calls.   (Available in SAS 360 Engage: Digital, SAS 360 Engage: Direct, SAS 360 Engage: Email, SAS 360 Discover, and SAS 360 Plan)   REST API for Managing Users, Groups, and Roles If you have administrative access, you can now manage users’ permissions through the SCIM API. This REST API enables you to perform these actions:   add and remove users add and edit groups add and remove roles that are assigned to users and groups   You can use the REST API to change these settings on an as-needed basis, but the API interface also enables you to automate role management and integrate this process with external systems.   For more information about this REST API, see SCIM API.   (Available in SAS 360 Engage: Digital, SAS 360 Engage: Direct, SAS 360 Engage: Email, SAS 360 Discover, SAS 360 Engage: Optimize, and SAS 360 Plan)   Marketing Design REST API The Marketing Design REST API provides a way to access and view information about some SAS Customer Intelligence 360 items. You can use this REST API to perform these actions:   access task information (for example, channel, details, status, and usage). filter and sort a list of tasks based on query parameters. access segment maps. For example, you can update the membership of a segment map and see information about the most recent job that affects the segment map. retrieve metadata about response tracking codes (RTC). The API enables you to use filters to get specific RTC metadata. This metadata can help you understand which content was shown to an individual. query metadata about occurrences of bulk tasks and segment maps. Similar to the features of the RTC endpoints, you can use filters to find the status of an execution and the metadata that is related to the execution.   For more information about this REST API, see Marketing Design API.   (Available in SAS 360 Engage: Digital, SAS 360 Engage: Direct, SAS 360 Engage: Email, SAS 360 Discover, and SAS 360 Plan)   Workflow REST API The Workflow REST API enables you to access and manage workflow resources for SAS 360 Plan through a public REST API. You can manage workflow items such as workflow processes, workflow tasks, approvals, assignments, and attachments.   For more information about this REST API, see Workflow API.   (Available in SAS 360 Plan)   Unified Data Model Schema Version 7 Organizations that are downloading data from SAS Customer Intelligence 360 now have access to a new schema version for the Unified Data Model (UDM). Depending on your license, you have access to new enhancements as a part of schema version 7.   The following columns are added to most SAS 360 Engage tables:   response_tracking_cd: stores the response tracking code on SAS 360 Engage events task_version_id: enables users to connect to the specific version of the task in the metadata message_id: stores the message ID if a message is used in a task message_version_id: enables users to connect to the specific version of the message in the metadata creative_version_id: enables users to connect to the specific version of the creative in the metadata segment_id: stores the segment ID if a segment is used in a task segment_version_id: enables users to connect to the specific version of the segment in the metadata properties_map_doc: is used for storing custom attributes event_key_cd: is used to determine whether the event came from the API   The following columns are added to some SAS 360 Engage email tables:   program_id: denotes the email program that is used recipient_domain_nm: represents the domain of the individual who is opening an email reason_txt: represents the reason an email bounces, such as an invalid address   The following columns are added to the MD_TASK_X_CREATIVE metadata table to help users understand which creative and spot combinations were used in testing:   spot_id arbitration_method_cd arbitration_method_val variant_id variant_nm   Five new SAS 360 Engage tables that provide more visibility into how SAS Customer Intelligence 360 executes tasks are added for download:   AB_TEST_PATH_ASSIGNMENT: represents the A/B test assignment in activities IMPRESSION_DELIVERED: represents that content has been delivered to a spot 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 the spot-requested event   These new columns are added to some existing SAS 360 Discover tables:   channel_nm: with the introduction of mobile events, provides the channel that the event came from mobile_app_id: provides the mobile application that generated the mobile event event_key_cd: is used to determine whether an event came from the API properties_map_doc: is used for storing custom attributes cart_nm: is added to the CART_ACTIVITY_DETAILS, ORDER_DETAILS, and ORDER_SUMMARY tables availability_message_txt, saving_message_txt, and shipping_message_txt: are added to the CART_ACTIVITY_DETAILS table activity_dttm, activity_dttm_tz, cart_id, and order_id: are added to the ORDER_DETAILS table referrer_url: is added to the PAGE_DETAILS table response_tracking_cd: is added to the EXTERNAL_EVENTS table to store response tracking codes for events that are being injected into the API gateway   (Available in SAS 360 Engage: Digital, SAS 360 Engage: Direct, SAS 360 Engage: Email, and SAS 360 Discover)   ... View more

  Execute JavaScript on a Web Page by Using JavaScript Spots You can now execute JavaScript on a web page by using a JavaScript spot, a plain text creative, and a web task. The plain text creative must be valid JavaScript to execute properly. When the web task executes the JavaScript on the web page, SAS Customer Intelligence 360 collects impression events.   To use JavaScript with web tasks, users need access to one of these roles:   JavaScript Spot Admin. With this role, an administrator can complete these actions:  create a JavaScript spot. edit an existing JavaScript spot. select a JavaScript spot and use it in a web task. JavaScript Spot User. With this role, a user can select a JavaScript spot and use it in a web task.   Although only text creatives are allowed, JavaScript spots can be used to execute third-party retargeting pixels and to create pop-up creatives.   (Available in SAS 360 Engage: Digital)   Use Email Link Tracking in HTML When creating email content, you can now add link-tracking information to custom HTML. To add link tracking to an element in your HTML, add the link-tracking attribute data-msys-linkname to an anchor tag.   Custom HTML is supported in these places:   custom HTML elements in the Layout Manager HTML that you author by using the HTML Editor HTML that you upload and use as the email layout Link tracking enables you to monitor how recipients interact with email content so that you can determine which parts of your email message are the most engaging. With link tracking enabled, you can track how many times a recipient clicks a link or a call-to-action URL on text, images, or buttons. You can also label and categorize the links to make reviewing the data easier. In addition, when you enable link tracking, the system generates a unique identifier for each link, even when the link has the same URL as other links.   (Available in SAS 360 Engage: Email)   Add Vertical Space in Email Layouts In the email Layout Manager, the new Spacer element enables you to add vertical space between other layout elements. With spacers, you control vertical space by using a method that is rendered consistently across email clients.   To add a spacer, navigate to the email Layout Manager and drag a Spacer element from the elements list. After the spacer is added, you can modify attributes such as its height and background color.   (Available in SAS 360 Engage: Email)   Diagnose Email Reachability Issues When email customers cannot receive communication, it is important to understand why and if there is an issue that needs to be addressed. In this release, you can use the Diagnostics settings page to retrieve the contact preferences for email addresses.   From the Diagnostics page, select the Email option and enter one or more email addresses in the field. For each email address, a table displays these results:   global opt-out preferences opt-out preferences for specific programs other reachability settings such as hard bounces or communications that were marked as spam (Available in SAS 360 Engage: Email)   Notifications for Email Tasks Contain More Information When you define an email task, you have the option to enable notifications that provide summary information about that task. When the email task completes, SAS Customer Intelligence 360 sends you a notification email with information about the results of the email task.   Now this email provides more detailed information about the corresponding email task. Here is a list of information that you can expect in your notification email:   Customers in the target audience Customers that were processed. For example: imprints that were sent successfully to the mail server customers for whom an imprint was not created or sent and the imprints that failed to be created or sent customers who were skipped, including those who previously opted out, were hard bounced, were marked as spam, or had invalid email addresses   (Available in SAS 360 Engage: Email)   New Filter for Merge Tags in Bulk Email Tasks When you design the content for a bulk email, in many cases you want to use merge tags to personalize the content that customers receive. The values for merge tags can come from different data sources, depending on your configuration and the data that you imported.   There is now an option that enables you to filter the merge tags based on their associated data source:   On-premises Cloud System   This is an example of the filter option:   Merge Tag Filter                                           (Available in SAS 360 Engage: Email)   Trigger In-App Messages Based on the Attributes of the Trigger Event When you create an in-app message task, you can specify a trigger condition that is based on the value of a trigger event attribute. This feature enables you to orchestrate more precisely the sending of personalized in-app messages to mobile app users.   For example, a mobile marketer for a hotel chain might want to send a specific mobile in-app message based on a user filling out their hotel amenities preferences in the app. More specifically, if the user selects Coffee Maker as their preferred hotel amenity, the marketer wants an in-app message that says, “We have rooms available with an espresso machine. Would you like to explore these room options?”. To enable this behavior, the marketer would create a custom mobile event called Favorite Amenities and add a custom attribute called Amenity. In the in-app message task, they would choose Favorite Amenities as the trigger event. Next, they would specify that the in-app message be triggered only for users who invoke the Favorite Amenities custom event, where the Amenity attribute is equal to “Coffee Maker”.   Note that in-app messages can be triggered only by an event that takes place in the mobile app. An example is when the user performs an action in the app, such as navigating to a specific page. External events, geolocation events (such as Geofence Entered, Geofence Exit, and Beacon Discovered), and events from other channels (such as web or email) cannot be used to trigger in-app messages. For example, a web-based Page View event cannot trigger an in-app message because an in-app message requires a mobile app-based Page View event.   In this release, you can use the following customer behavior events as trigger events for in-app message tasks:   Custom mobile events Standard events that are defined specifically for mobile apps. These events include Click-through, Page View, and Mobile App Focus.   In an upcoming release, the list will include eCommerce events, Promotion events, and Internal Search events.   (Available in SAS 360 Engage: Digital)   Show or Hide Messages That Are Associated with Planning Items In this release, you can control the display of messages that are associated with planning items at each level in the marketing hierarchy.   This feature is available if your organization has a license for SAS 360 Plan and SAS 360 Engage. To enable messages, navigate to General Settings => Plan => Marketing Hierarchies. At a selected level, click the Configure button. In the Level Configuration window, select Messages.   When the setting is enabled, a Messages tab is available within the Details tab of the planning item at the configured level. Note that the setting for messages is disabled by default.   (Available in SAS 360 Plan)   Enable Workflows for Messages You can now initiate workflows when you create messages in SAS Customer Intelligence 360. This feature enables you to use the workflows functionality to assign tasks for the creation, review, and approval of messages.   This feature is available if your organization has a license for SAS 360 Plan and SAS 360 Engage. To enable workflows for messages, navigate to General Settings => Global => Workflows, and then select Messages. When the setting is enabled, a Workflows tab is displayed within the message.   Workflows Tab                               (Available in SAS 360 Plan)   Enable External Sharing of Assets By Default Administrators can enable an option to make assets externally available by default when the assets are uploaded to the repository in SAS Customer Intelligence 360.   To enable external sharing as a default setting, navigate to General Settings => Product Management => Asset, and then click Enable external sharing on upload of assets. Users can override the default setting when they perform an upload.   (Available in SAS 360 Plan)   Enhanced Financials View within a Planning Item Planners can now get a comprehensive view of financial information related to a planning item and its associated planning items in the marketing hierarchy. The Budget page on the Financials tab of a planning item now displays information about the planned budgets and the total as well as rolled-up expenses for that planning item and the child planning items below that level.   In the Track Allocation and Expenses section, the planning item and all the child planning items below that level are displayed in a tree view. This information is represented in columns and makes it easy for planners to track the allocated budgets and the expenses that are related to a marketing plan and the associated planning items at the lower-level. For example, if you are viewing the budget of a plan, on the same page you can also view allocations for the total and level budgets and the expenses amounts for that plan and for the associated programs, campaigns, tasks, and activities in the hierarchy below the plan.   (Available in SAS 360 Plan) ... View more

            Enable the External Sharing of Assets during the Upload Process You can now generate asset URLs that can be externally shared during the asset upload process. Previously, you could enable external sharing only after an asset was uploaded. This option is available for single file uploads and batch uploads.   This feature enables you to quickly create content with one or more assets for which external sharing is already enabled. For example, you can create an email task and directly use the externally shared asset in the content of the email.   (Available in SAS 360 Engage: Digital, SAS 360 Engage: Direct, SAS 360 Engage: Email, and SAS 360 Plan)   New Diagnostics Admin Role A new Diagnostics Admin role grants users access only to the General Settings => Diagnostics page without granting access to other pages in General Settings. This role is useful for users who are interested in diagnostics but not in other configuration options in General Settings.   Note: The Config Admin role no longer provides access to the Diagnostics page. If you want a user with Config Admin permissions to access the Diagnostics page, add the Diagnostics Admin role to that user. By default, SAS administrators have access to the Diagnostics page.   (Available in SAS 360 Engage: Digital, SAS 360 Engage: Direct, SAS 360 Engage: Email, and SAS 360 Discover)   Reactivate a Non-Responsive Segment Map or On-Premises Direct Marketing Task In some circumstances, such as when the direct marketing agent is down or there are errors in a custom stored process, a segment map or an on-premises direct marketing task might have the Running status for an indefinite amount of time.   To address this issue, administrators can click the Activate the Non-Responsive Item button to move the status of the item from Running to Active with an error. When this button is clicked, the initial execution of the item might continue in the background and the error message is cleared only on the next republish of the item.   Activate a Non-Responsive Item     This feature enables you to edit the segment map or direct marketing task and re-execute.   (Available in SAS 360 Engage: Direct)   View Information about the Execution of Bulk Push Notification Tasks In a Bulk Push Notification task, you can now view information about each task occurrence, including the Occurrence Start Date, Occurrence End Date, Occurrence Type, Started By (User), and Status. To see this information, in a Bulk Push Notification task, navigate to Orchestration => History, and then click Occurrence.   This feature enables designers of Bulk Push Notification tasks to get an update on the success or failure of a specific task occurrence more easily.   Note: The values for tasks that were published prior to this release are blank.   (Available in SAS 360 Engage: Digital)   Support for New Android 11 and iOS 14 Operating System Updates Beginning with this release, Android 5 and iOS 9 and 10 are no longer supported. Support is provided for Android 6 and later and iOS 11 and later.   (Available in SAS 360 Engage: Digital)   Ability to Override the Domain Value for Spots and Events When you define spots or events, web developers can now use a code snippet to override a page’s document.domain property with a specific value. By overriding the value for the default domain in the SAS tag, you can ensure that the domain for each page matches the configuration that you expect.   This feature is useful for websites that change domains between a top-level domain and a subdomain. For example, you can have issues locating a spot definition on a page when the domain’s value changes from what is defined in your configuration.   (Available in SAS 360 Engage: Digital and SAS 360 Discover) ... View more