/ci360-extensions

SAS CI360 connectors, agents and other assets that are ready to be used to enhance the capabilities of SAS CI360 and connect to 3rd party services.

Primary LanguageJavaScriptApache License 2.0Apache-2.0

SAS Customer Intelligence 360 - Extensions

Overview

SAS CI360 Connector Framework and Agent SDK provide infrastructure to integrate SAS Customer Intelligence 360 (CI360) with other applications. This repository contains a number of connectors and agents that are ready to be used to enhance the capabilities of CI360 and connect to 3rd party services. In addition, there are other integration assets included as well. All integration assets included in this repository are listed below, with short description. Details about each are included within specific sub-folders.

Table of Contents

This topic contains the following sections:

Prerequisites

Prerequisites vary between integration assets included here, and are listed in detail for each in the respecitive sub-folders. But some of the prerequisites include:

  • Amazon Web Service account with access to Lambda and API Gateway service
  • Microsoft Azure account with access to Functions and other Azure services
  • Java 1.8 or newer
  • Python 3.7 or newer

Installation

Installation instructions for every extension are included in the project specific sub-folder README file. Installation and deployment instructions are platform specific.

List of Extensions

This is a list of connectors and agents included in this repository:

  • SMS/MMS (via Syniverse): Syniverse Communication Gateway (SCG) connector, enables SMS and MMS communication through Syniverse
  • WhatsApp (via Syniverse): Syniverse Communication Gateway (SCG) connector, enables WhatsApp communication through Syniverse
  • WeChat (via Syniverse): Syniverse Communication Gateway (SCG) connector, enables WeChat communication through Syniverse
  • SMS (via SFMC): Salesforce Marketing Cloud (SFMC) connector, enables SMS through Salesforce Marketing Cloud
  • Email (via SFMC): Salesforce Marketing Cloud (SFMC) connector, enables Email communication through Salesforce Marketing Cloud
  • SMS (via Twilio): Twilio connector, enables SMS through Twilio
  • Google Analytics: Implementation of connection with Google Analytics (GA)
  • Facebook Event Manager: Implementation of connection with Facebook Event Manager
  • Adobe Audience Manager: Implementation of connection with Adobe Audience Manager (AAM)
  • Google Tag Manager: Employ the use of Google Tag Manager's Community Templates in order to easily deploy javascript actions for Customer Intelligence 360
  • SAS Event Stream Processing: SAS Event Stream Processing (ESP) agent enables streaming of CI360 events into ESP
  • SAS ESP CI360 Adapter: SAS Event Stream Processing adapter that allows streaming of events from an ESP window to CI360
  • CI360 Debug Agent: CI360 Debug agent streams events into log files, console output, local database or Elastic search API
  • SAS Cloud Analytic Services: SAS Cloud Analyic Services (CAS) Agent streams CI360 events into a CAS table
  • Snowflake Streaming Agent: CI360 Snowflake Agent streams all received events to the configured Snowflake instance
  • Snowflake UDM Loader: CI360 UDM Loader for Snowflake automates the download of UDM data from Customer Intelligence 360 and then seemlessly loads this into Snowflake, utilizing SAS provided Python download client within a Docker container
  • CRM (via Salesforce): Salesforce CRM (SFDC) connector, enables creating contacts and cases in SFDC
  • Snowy CI360: Browser extension as an easy way to monitor the network traffic (POST) to SAS CI 360, with the ability to search the form data

Getting Started

To set up and use the provided extension code you need to perform the following steps :

Download sample code

  1. Download a ci360-extensions project source code into zip/tar.gz/tar.bz2/tar file format on your local machine.
    Note: You can also clone the project on your local machine

  2. The project will be downloaded on your local machine in your specified file format. You need to unzip/untar the downloaded project.

  3. You can see the folder ci360-extensions after unzip/untar the project.

  4. Open the ci360-extensions folder. It will contain multiple sub-folders for various connector and agent integration resources.

Build or Deploy

Build and deployment instructions are included for each of the integration assets in their respoective sub-folders.

Deploying CI360 Connectors

Please refer Set up a Custom Connector section in SAS Customer Intelligence 360 admin guide.

Register your connector into CI360

For most connector or agent integration assets, you need to register the connector and endpoint with these details into the CI360 system to use the connector. Details are included for each connector or agent in their sub-folders. Documentation sections are referenced below for eacy access.

Add and Register a Connector Please refer to Add and Register a Connector in SAS Customer Intelligence 360 admin guide.

Add an Endpoint Please refer to Add an Endpoint in SAS Customer Intelligence 360 admin guide.

Deploying CI360 Agents

For CI360 agent development, agent SDK needs to be downloaded and installed into the local Maven repository. See Download an Access Point SDK in SAS Customer Intelligence 360 admin guide.

To install SDK JAR into local Maven repository:

mvn install:install-file -Dfile=<path where CI360 agent was downloaded>/sdk/mkt-agent-sdk-jar-1.current release.jar -DpomFile=path where CI360 agent was downloaded/sdk/pom.xml

Create an Access Point Definition Please refer to Create an Access Point Definition in SAS Customer Intelligence 360 admin guide.

Extension Best Practices

Logging and PII

Many agents and connectors included here log information for debugging purposes, either in local log files or cloud based logging services. While connectors and agents generally won't explicitly log any PII data, some include mechanism for logging complete CI360 event objects, based on logging levels configured, usually controlled using logging specific configuration files. In order to avoid logging or storage of PII data, it is a best practice to either disable logging by setting the logging level, or exclude PII data from being sent by CI360.

Contributing

We welcome your contributions! Please read CONTRIBUTING.md for details on how to submit contributions to this project.

License

This project is licensed under the Apache 2.0 License.

Additional Resources

For more information, see External Data Integration with Connectors.