Integration Specifications

This article will help you learn about how Daasity replicates data from Retention Science, limitations to the data we can extract and where the data is stored in the Retention Science schema

Integration Overview

Retention Science is an A.I.-driven email and SMS e-commerce platform for email marketing automation. It applies a combination of detailed analytics, revenue reporting, visualizations and data mining tools to give merchants visibility from top-level reporting all the way down to individual prospect behaviors.

This document provides context on what kind of data is being gathered through this extractor, which endpoints that data is coming from, and how the extracted tables relate to each other.

Integration Availability

This integration is available for:

• Enterprise

SFTP Server

The Daasity Retention Science extractor is built based on this Retention Science API Documentation. Daasity uses the SFTP Server to extract files and replicate data from Retention Science:

• Events

In order to connect to the SFTP server and extract data, please contact your Retention Science representative to obtain a username and password.

Entity Relationship Diagram (ERD)

Click here to view the ERD for the Daasity Retention Science integration illustrating the different tables and keys to join across tables.

Retention Science Schema

The Daasity Retention Science extractor creates these tables using the SFTP Server and replication methods listed. The data is mapped from SFTP files to the table based on the mapping logic outlined in each table.

• Events

Events

• Endpoint: Events

• Update Method: UPSERT

• Table Name: [retention_science.events]

JSON Element	Database Column
event::event_id	event_id
event::campaign_id	campaign_id
event::campaign_name	campaign_name
event::campaign_type	campaign_type
event::email_id	email_id
event::email	email
event::send_id	send_id
event::event_type	event_type
event::event_at	event_at
event::click_url	click_url
event::item_id	item_id
Daasity: source_id	__source_id
Daasity: account_id	_account_id
Daasity: MD5(event::event_id + event::click_url)	__sync_key
Daasity: timestamp when loaded into DB	__synced_at