Selligent feature snapshot

A high-level look at Stitch's Selligent integration, including release status, useful links, and the features supported in Stitch.

STITCH
Release Status

Released

Supported By

Singer Community

Stitch Plan

Free

Singer GitHub Repository

Selligent Repository

DATA SELECTION
Table Selection

Unsupported

Column Selection

Unsupported

REPLICATION SETTINGS
Anchor Scheduling

Supported

Advanced Scheduling

Unsupported

Table-level Reset

Unsupported

Configurable Replication Methods

Unsupported

TRANSPARENCY
Extraction Logs

Supported

Loading Reports

Supported

Connecting Selligent

Selligent setup requirements

To set up Selligent in Stitch, you need:

  • Personal Selligent API Key. This is required to connect Selligent to Stitch.

Step 1: Obtain Selligent API Key

Contact your Selligent account manager to obtain the API key for your organization.

After you receive your API key, you can proceed with the setup in Stitch.

Step 2: Add Selligent as a Stitch data source

  1. Sign into your Stitch account.
  2. On the Stitch Dashboard page, click the Add Integration button.

  3. Click the Selligent icon.

  4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

    For example, the name “Stitch Selligent” would create a schema called stitch_selligent in the destination. Note: Schema names cannot be changed after you save the integration.

  5. In the Base URL field, enter the base URL for your Selligent installation. It will be similar to https://organization.some-host.com:443
  6. In the API Key field, paste the API key you obtained in Step 1.

Step 3: Define the historical sync

The Sync Historical Data setting will define the starting date for your Selligent integration. This means that:

  • For tables using Incremental Replication, data equal to or newer than this date will be replicated to your data warehouse.
  • For tables using Full Table Replication, all data - including records that are older, equal to, or newer than this date - will be replicated to your data warehouse.

Change this setting if you want to replicate data beyond Selligent’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.

Step 4: Create a replication schedule

In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Selligent integrations support the following replication scheduling methods:

To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.

Step 5: Set tables to replicate

To complete the setup, you’ll need to select the tables you want to replicate to your data warehouse.

Check out the Schema section to learn more about the available tables in Selligent and how they replicate.

  1. In the list of tables that displays - or in the Tables to Replicate tab, if you skipped this step during setup - locate a table you want to replicate.
  2. To track a table, click the checkbox next to the table’s name. A green checkmark means the table is set to replicate.

  3. Repeat this process for all the tables you want to replicate.
  4. When finished, click the Finalize Your Selections button at the bottom of the screen to save your selections.

Note: If you change these settings while a replication job is still in progress, they will not be used until the next job starts.

Initial and historical replication jobs

After you finish setting up Selligent, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.


Selligent table schemas

Replication Method :

Full Table

Primary Key :

asset_id

This table contains campaign data.

asset_id
INTEGER

modified_time
STRING

asset_name
STRING

version_number
STRING


internal_datasource

Replication Method :

Full Table

Primary Key :

id

This table contains internal data source data.

id
INTEGER

The asset_id of this mailing.

modified_time
STRING

asset_name
STRING

asset_url
STRING

cloud_sync
BOOLEAN

data_source_stat
OBJECT

num_total_rec
INTEGER

internal_datasource (table), data_source_stat (attribute)

version_number
STRING


Replication Method :

Full Table

Primary Key :

asset_id

This table contains owner data.

asset_id
INTEGER

modified_time
STRING

first_name
STRING

last_name
STRING


Replication Method :

Full Table

Primary Key :

id

This table contains program data.

id
INTEGER

The asset_id of this mailing.

modified_time
STRING

asset_name
STRING

asset_url
STRING

status
STRING

type
STRING


Replication Method :

Full Table

Primary Key :

asset_id

This table contains source data.

asset_id
INTEGER

modified_time
STRING

asset_name
STRING

data_source_type
STRING

version_number
STRING


transactional_mailing

Replication Method :

Full Table

Primary Key :

id

This table contains transactional mailing data.

id
INTEGER

The asset_id of this mailing.

modified_time
STRING

approved
BOOLEAN

asset_name
STRING

channel
STRING

compliance
BOOLEAN

mailing_priority
STRING

mailing_server_group
STRING

mailing_status
STRING

target
OBJECT

asset_id
INTEGER

asset_name
STRING

transactional_mailing (table), target (attribute)

version_number
STRING



Questions? Feedback?

Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.