Already have an account? Sign in

Selligent (v1)

Selligent feature snapshot

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

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 theAdd Integration button.

3. Click theSelligent 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 calledstitch_selligent in the destination.Note: Schema names cannot be changed after you save the integration.

5. In theBase URL field, enter the base URL for your Selligent installation. It will be similar tohttps://organization.some-host.com:443
6. In theAPI Key field, paste the API key you obtained inStep 1.

Step 3: Define the historical replication start date

The Sync Historical Data setting defines the starting date for your Selligent integration. This means that dataequal 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 of1 year. For a detailed look at historical replication jobs, check out theSyncing Historical SaaS Data guide.

Step 4: Create a replication schedule

In theReplication Frequency section, you’ll create the integration’sreplication 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:

• Replication Frequency

• Anchor Scheduling

• Advanced Scheduling using Cron (Advanced or Premium plans only)

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

Step 5: Set objects to replicate

The last step is to select the tables you want to replicate.Learn about the available tables for this integration.

Note: If a replication job is currently in progress, new selections won’t be used until the next job starts.

1. In the integration’sTables to Replicate tab, locate a table you want to replicate.

2. To track a table, click thecheckbox next to the table’s name. A blue checkmark means the table is set to replicate.

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

Initial and historical replication jobs

After you finish setting up Selligent, itsSync Status may show asPending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, aPending 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 reference

campaign.asset_id = internal_datasource.id

campaign.asset_id = owner.asset_id

campaign.asset_id = source.asset_id

campaign.asset_id = transactional_mailing.id

campaign.asset_id = program.id

internal_datasource.id = campaign.asset_id

internal_datasource.id = owner.asset_id

internal_datasource.id = source.asset_id

internal_datasource.id = transactional_mailing.id

internal_datasource.id = program.id

owner.asset_id = campaign.asset_id

owner.asset_id = internal_datasource.id

owner.asset_id = source.asset_id

owner.asset_id = transactional_mailing.id

owner.asset_id = program.id

program.id = campaign.asset_id

program.id = internal_datasource.id

program.id = owner.asset_id

program.id = source.asset_id

program.id = transactional_mailing.id

source.asset_id = campaign.asset_id

source.asset_id = internal_datasource.id

source.asset_id = owner.asset_id

source.asset_id = transactional_mailing.id

source.asset_id = program.id

transactional_mailing.id = campaign.asset_id

transactional_mailing.id = internal_datasource.id

transactional_mailing.id = owner.asset_id

transactional_mailing.id = source.asset_id

transactional_mailing.id = program.id

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