Plan, execute, measure and optimize customer experiences

What's New in the 17.10 Release of CI360

SAS Employee
Posts: 16

What's New in the 17.10 Release of CI360

Here's what's new in the 17.10 release of SAS Customer Intelligence 360:


Release 17.10


SAS 360 Engage New Features and Enhancements


Design Center


Numeric data type for event standard attributes


The event standard attributes listed here are now supported in a numeric data type rather than a string data type:


  • Product Attributes
    • Product Unit Price
    • Product Quantity Added to Cart/Product Quantity
  • Cart/Checkout/Purchase Attributes
    • Cart Total/Checkout Total/Purchase Total
    • Tax
    • Shipping Cost

You now have more flexibility in defining targeting criteria with relational operators. The numeric data type enables you to use relational operators (for example, <,>) with these attributes in areas such as targeting expressions. For example, you might want to target users who have viewed a product with a product unit price > USD 25.00. When you create a product view event, the Product Unit Price attribute is a numeric data type. You can then create a task and add the product view event in the targeting criteria with the condition of Product Unit Price > 25.




Support for multiple paths from a node


Use an activity to create a multi-channel experience for your customers by using multiple paths that originate from the same node. Starting multiple paths from one node enables people who start from a single point such as a web interaction to proceed through multiple paths and across multiple channels simultaneously. For example, you can now make an offer to new customers in an activity, and then make three follow-up offers after they meet the primary metric for the first task, where all three offers are made available on different channels at the same time.




Stream events to and from SAS Customer Intelligence 360


Although SAS Customer Intelligence 360 can track customer interactions on websites, mobile, and email, many interactions occur in non-digital channels, CMS, CRM, transactional systems, and other SAS solutions such as SAS Real-Time Decision Manager. Access to these interactions can provide SAS Customer Intelligence 360 with more insights for targeting and segmentation.


Likewise, events in SAS Customer intelligence 360 identify how customers interact with content. These events are valuable for targeting and segmentation within SAS Customer Intelligence 360. They are also useful in other systems, such as CRM, transactional systems, traditional marketing systems, and other SAS solutions such as SAS Real-Time Decision Manager and SAS Event Stream Processing.


SAS Customer Intelligence 360 now provides an interface to stream events between SAS Customer Intelligence 360 and external systems that are on premises or in a private cloud. The interface is accessed using plug-ins that are created with a software development kit (agent SDK) that can be customized for specific integrations. Many plug-ins can be configured, allowing for integration with many external systems.


Security of the connection between the plug-in and SAS Customer Intelligence 360 is ensured with the use of HTTPS and token-based authentication. Further security is ensured by supporting GET requests from the agent. A GET request is a read-only request made from a client for a specific resource. In the case of the plug-in, it is a request to SAS Customer Intelligence 360 for events. Because these requests are made from within the firewall, there is greater security when compared with external systems pushing data.

Low latency of the connection between the plug-in and SAS Customer Intelligence 360 is addressed with the use of WebSockets. Using WebSockets, the connection that is established between the agent and SAS Customer Intelligence 360 remains active. All requests for customer data are sent using the connection, so an individual connection does not have to be made for each request. The connection has less latency and can handle continuous access of customer data.


When the integration is configured, interactions with a plug-in can be managed from within SAS Customer Intelligence 360. For outbound events, this includes specifying which events are sent to a plug-in and what customer identifier is associated with the events. For inbound events, this includes events that are received from external systems for targeting and segmentation.




Handling of push notifications for multiple users on a shared mobile device


If you use an app on a shared device that is eligible to receive push notifications, mobile app developers can now disassociate or associate users from that device based on their logged-out or logged-in status, respectively. This ensures that users receive the correct push notifications when they are the logged in to the app on a shared device.


Planner (Operations


New budget and expense columns in plan tables


Budget and expense information is displayed automatically in plan tables so that you always know how much money is committed and if you have money to spend. You can view your budget by planning level. You can also see if money is set aside for an individual planning item. Total expenses are summarized from an item’s commitment and invoice information and the available budget shows the difference between your budget and expenses. These new columns are available from the plan table view, a planning items relationship tab, and a planning items rolled-up-budget table in the budget area of the Financials tab.


Record vendor and plan currency in commitments and invoices


Commitments and invoices track marketing expenses within planning items in addition to tasks and activities. Because some vendors bill in a different currency than the currency that is used in your plan, you might want to convert the amount to your plan currency. When you enter a commitment or invoice for a vendor with a different billing currency, SAS Customer Intelligence 360 displays an additional amount column for the vendor currency amount so that you can record both the vendor currency amount and the planning currency amount.

Ask a Question
Discussion stats
  • 0 replies
  • 1 in conversation