Selligent Export Integration

This integration enables uploading data from Treasure AI directly to Selligent static segments. Selligent, is an omnichannel marketing automation platform for audience segmentation and campaign activation.

The Selligent export integration loads records into a Selligent master List and then assigns those records to one or more static Segments. The target Segment is determined for each row by the selligent_segment column, or by another column that you configure.

• Basic knowledge of Treasure AI.
• Basic knowledge of Selligent Lists, static Segments, and API names.
• A Selligent API key and API secret.
• Your Selligent base URL, for example https://customer.slgnt.eu for the EU region or https://customer.slgnt.us for the US region.
• Your Selligent organization identifier.
• A target List API name. If you want Treasure AI to create the List, enable create_list_if_not_exists.
• A key field, such as CUSTOMER_IDENTIFIER or EMAIL, that uniquely identifies records for deduplication.

If your security policy requires IP whitelisting, you must add Treasure Data's IP addresses to your allowlist to ensure a successful connection.

Please find the complete list of static IP addresses, organized by region, at the following document

• This integration supports Selligent static Segments only.
• The integration always loads records into the master List first, then loads records into the target Segment.
• One export run can write to multiple Segments when the query result contains multiple values in the configured Segment routing column.
• The Segment routing column is not sent as a Selligent field.
• When you export to an existing List, all input fields must already exist in that List. If a field is missing, the export fails with a configuration error.
• The integration does not delete records from the master List. In replace mode, it clears Segment membership before loading the new Segment data.
• Selligent rate limit responses and server errors are retried. Other 4xx responses fail fast because they usually indicate an authentication or configuration issue.

In Treasure AI, you must create and configure the data connection before running your query. As part of the data connection, you provide authentication to access Selligent.

1. Open TD Console.
2. Navigate to Integrations Hub > Catalog.
3. Click the search icon on the far right of the Catalog screen and enter Selligent.
4. Hover over the Selligent connector and select Create Authentication.

The New Authentication dialog opens.

1. Enter the Selligent Base URL.

• EU region: https://customer.slgnt.eu
• US region: https://customer.slgnt.us

6. Enter your Selligent API Key.
7. Enter your Selligent API Secret.
8. Enter a name for your connection.
9. Select Continue.

To configure the integration:

1. Open TD Console.
2. Navigate to Data Workbench > Queries.
3. Click New Query to create a query, or open a saved query that you want to export.
4. At the top of the query editor, select Export Results.
5. Select the Selligent authentication that you created.
6. Configure the export parameters.

The integration uses a two-step load process:

1. List load: The integration upserts all valid records in the batch into the Selligent List by using key_fields for deduplication.
2. Segment load: The integration groups records by the configured Segment routing column, then loads each group into the matching static Segment.

The Segment routing column is required. Each value in that column must match the target Segment api_name. Rows with a null or blank Segment value are skipped when skip_invalid_records is true.

When create_list_if_not_exists is true, the integration creates Selligent fields from the Treasure AI query result schema, excluding the Segment routing column.

This example exports active customers to a single Selligent Segment named active_customers.

SELECT
  'active_customers' AS selligent_segment,
  customer_id AS customer_identifier,
  email AS email,
  first_name AS first_name,
  last_name AS last_name
FROM customers
WHERE status = 'active'
  AND email IS NOT NULL

Sample query result

Required configuration

In Selligent, the integration sends the fields as CUSTOMER_IDENTIFIER, EMAIL, FIRST_NAME, and LAST_NAME.

This example routes customers to different Selligent Segments based on business logic. VIP customers are sent to vip_customers, dormant customers are sent to re_engagement, and other customers are sent to standard_customers.

SELECT
  CASE
    WHEN lifetime_value >= 1000 THEN 'vip_customers'
    WHEN last_purchase_at < CURRENT_TIMESTAMP - INTERVAL '180' DAY THEN 're_engagement'
    ELSE 'standard_customers'
  END AS selligent_segment,
  customer_id AS customer_identifier,
  email AS email,
  first_name AS first_name,
  lifetime_value AS lifetime_value,
  last_purchase_at AS last_purchase_at
FROM customer_profile
WHERE email IS NOT NULL
  AND opt_in_email = true

Sample query result

Required configuration

The integration loads all valid rows into master_contacts first. It then performs one Segment load for each unique Segment value in the batch: vip_customers, re_engagement, and standard_customers.

You can use Scheduled Jobs with Result Export to periodically write the output result to Selligent.

Treasure AI's scheduler feature supports periodic query execution to achieve high availability.

You can use Scheduled Jobs with Result Export to periodically write the output result to a target destination that you specify.

Treasure Data's scheduler feature supports periodic query execution to achieve high availability.

When two specifications provide conflicting schedule specifications, the specification requesting to execute more often is followed while the other schedule specification is ignored.

For example, if the cron schedule is '0 0 1 * 1', then the 'day of month' specification and 'day of week' are discordant because the former specification requires it to run every first day of each month at midnight (00:00), while the latter specification requires it to run every Monday at midnight (00:00). The latter specification is followed.

1. Navigate to Data Workbench > Queries

2. Create a new query or select an existing query.

3. Next to Schedule, select None.

4. In the drop-down, select one of the following schedule options:

   Drop-down Value	Description
   Custom cron...	Review Custom cron... details.
   @daily (midnight)	Run once a day at midnight (00:00 am) in the specified time zone.
   @hourly (:00)	Run every hour at 00 minutes.
   None	No schedule.

 *    *    *    *    *
 -    -    -    -    -
 |    |    |    |    |
 |    |    |    |    +----- day of week (0 - 6) (Sunday=0)
 |    |    |    +---------- month (1 - 12)
 |    |    +--------------- day of month (1 - 31)
 |    +-------------------- hour (0 - 23)
 +------------------------- min (0 - 59)

The following named entries can be used:

• Day of Week: sun, mon, tue, wed, thu, fri, sat.
• Month: jan, feb, mar, apr, may, jun, jul, aug, sep, oct, nov, dec.

A single space is required between each field. The values for each field can be composed of:

1. (Optional) You can delay the start time of a query by enabling the Delay execution.

Save the query with a name and run, or just run the query. Upon successful completion of the query, the query result is automatically exported to the specified destination.

(Optional) You can delay the start time of a query by enabling the Delay execution.

You can also send segment data to the target platform by creating an activation in the Audience Studio.

1. Navigate to Audience Studio.
2. Select a parent segment.
3. Open the target segment, right-mouse click, and then select Create Activation.
4. In the Details panel, enter an Activation name and configure the activation according to the previous section on Configuration Parameters.
5. Customize the activation output in the Output Mapping panel.

• Attribute Columns
  • Select Export All Columns to export all columns without making any changes.
  • Select + Add Columns to add specific columns for the export. The Output Column Name pre-populates with the same Source column name. You can update the Output Column Name. Continue to select + Add Columnsto add new columns for your activation output.
• String Builder
  • + Add string to create strings for export. Select from the following values:
    • String: Choose any value; use text to create a custom value.
    • Timestamp: The date and time of the export.
    • Segment Id: The segment ID number.
    • Segment Name: The segment name.
    • Audience Id: The parent segment number.

6. Set a Schedule.

• Select the values to define your schedule and optionally include email notifications.

7. Select Create.

Within Treasure Workflow, you can specify the use of a data connector to export data.

Learn more at Using Workflows to Export Data with the TD Toolbelt.

Sample Workflow Configuration

timezone: UTC

_export:
  td:
    database: sample_datasets

+td-result-into-selligent:
  td>: queries/selligent_export.sql
  result_connection: selligent
  result_settings:
    organization: my_org
    list_api_name: master_contacts
    create_list_if_not_exists: false
    list_data_import_option: InsertAndUpdate
    segment_column: selligent_segment
    create_segment_if_not_exists: true
    segment_data_import_option: append
    key_fields: CUSTOMER_IDENTIFIER
    deduplication: ImportLastMatch
    error_handling: ContinueOnError
    mode: Sync
    skip_invalid_records: true

• Selligent SMC V1 API documentation