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.
This topic contains the following sections:
- Prerequisites
- Installation
- List of Extensions
- Getting Started
- Contributing
- License
- Additional Resources
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 8 or newer for 23.07 release or earlier, Java 11 or newer for 23.08 release or later
- Python 3.7 or newer
Installation instructions for every extension are included in the project specific sub-folder README file. Installation and deployment instructions are platform specific.
This is a list of connectors, agents and other related content and utilities 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
- 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
- SMS (via Twilio): Twilio connector, enables SMS through Twilio, no-code integration using CI360 custom task types
- 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)
- 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
- 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
- CI360 Debug Agent: CI360 Debug agent streams events into log files, console output, local database or Elastic search API
- CI360 Event to DB Agent: Stream CI360 events to DB Table
- AWS S3: Upload customer data to AWS S3 bucket
- Google BigQuery Streaming Agent: Google BigQuery agent enables streaming of CI360 events into Google BigQuery table
- Kafka CI360 Connector: Send events from Kafka to CI360
- CI360 Braze Bulk User Import Connector: Send customer audiences and attributes generated in CI360 from various sources to Braze
- MailChimp List Upload: Send customer lists and attributes from CI360 to MailChimp for use in email campaign activation
- Azure Eventhub CI360 Connector: Stream events from Azure Event Hub to CI360
- Azure Blob Storage: Upload CI360 generated customer data to Azure Blob storage
- CI360 Match: Sync CI360 targeted audiences to CI360 Match
- Google Tag Manager: Employ the use of Google Tag Manager's Community Templates in order to easily deploy javascript actions for Customer Intelligence 360
- 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
- API Helper for CI360: Interact with CI360 APIs using easy to use web based UI
- CI360 API DS2 Utilities: Utilities package for CI360 API interaction using DS2
- Customer Data Upload for CI360: Upload customer data to CI360 cloud datahub table
- CI360 GDPR Delete: GDPR remove customer cloud data from CI360
- CI360 Identity Uploader: Upload new identities to CI360
- CI360 Audience from Viya (custom step): Upload analytically defined customer audience from Viya into CI360 using Viya Custom Step
- CI Modernization Preparation Tool: Customer-facing tool intended to support the modernization from CI 6.6 to SAS CI 360
- CI360 Direct SQL Extraction Utility: Utility for extracting generated SQL statements from CI360 Direct logs
- CI360 Direct Data Item Extraction Utility: Utility for creating a report on used data items in CI360 Direct Marketing tasks and segment maps
- CI360 Tenant Promotion Utility: Tenant Promotion utility helps in copying objects from one tenant to another
- CI360 Audit Data Download: Download the Audit data from CI360 in parquet and CSV formats
- CI360 Custom Task Connector Integration with On-prem SAS STP: Integrate a CI360 Custom Task Type using a connector with an onprem SAS stored process (STP)
- CI360 Audience Management Utility: Create, manage and populate CI360 audiences using Python scripts
- CI360 Custom Code Nodes: Stored process that extracts SAS code from a specific location and makes them available to run in CI360 as part of a stored process
- JavaScript Event API Support: Code snippets for for SPA applications, delivering a spot/creative using SAS CI360
To set up and use the provided extension code you need to perform the following steps :
-
Download a
ci360-extensionsproject 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 -
The project will be downloaded on your local machine in your specified file format. You need to unzip/untar the downloaded project.
-
You can see the folder
ci360-extensionsafter unzip/untar the project. -
Open the
ci360-extensionsfolder. It will contain multiple sub-folders for various connector and agent integration resources.
Build and deployment instructions are included for each of the integration assets in their respoective sub-folders.
Please refer Set up a Custom Connector section in SAS Customer Intelligence 360 admin guide.
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.
For CI360 agent development, agent SDK needs to be downloaded and installed into the local Maven repository. See Download the General Agent in SAS Customer Intelligence 360 admin guide. General Agent includes the SDK.
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.
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.
We welcome your contributions! Please read CONTRIBUTING.md for details on how to submit contributions to this project.
This project is licensed under the Apache 2.0 License.
For more information, see External Data Integration with Connectors.