# Supership Export Integration

Treasure Data can send user list data to Supership’s DSP service. You can make a user list in Treasure Data that targets a segment and then send the list to Supership to use in your advertisement actions. Refer to [the Supership webpage](https://supership.jp/).

## Prerequisites

- Basic knowledge of Treasure Data
- A Supership account


### Get access permission from Supership

Treasure Data and Supership have collaborated to ensure a secure data exchange. You must request access to Supership’s TD account. Ask your Supership account administrator for the following information:

- TD API Key
- Database name


## Usage

To export data, you create or select an existing connection, create or reuse a query, and then run the query to export your user lists. You can use **td_global_id** lists as user lists.

### Create or reuse a query

- Go to [Query Editor](https://console.treasuredata.com/app/queries/editor). You can pick the query language and write your query.
- Select your database and table.
- Access the query that you plan to use to export data. Here is a sample query:



```sql
SELECT
  DISTINCT "td_global_id"
FROM
  "weblog"
WHERE
  td_url = "xxx"
```

### Create or select an existing Supership connection

| Option | Task Steps | Tip |
|  --- | --- | --- |
| Create a connector
 | - Go to [Connections](https://console.treasuredata.com/app/connections).
- Select the *Supership* icon from *Sources Catalog*.
- Complete the required fields on the first pane.
- In the *API Key* field, enter the API Key you get from Supership.

Next you complete the Configuration fields.
 | You don't have to modify *Endpoint* field.
 |
| Select a connector
 | - Go to [TD Console](https://console.treasuredata.com/users/sign_in).
- Go to [Query Editor](https://console.treasuredata.com/app/queries/editor).
- Access the query that you plan to use to export data.
- Select *Output results*. The *Choose Saved Connection* dialog opens.
- Type the connection name in the search box to filter and select the connection that you want.

Next, you complete the Configuration fields.
 | You can also create a new connection from here by selecting *Create New Connection*.
 |


Creating a new connection:

![](/assets/image-20191209-213856.66021323bf6e869a73a8c5674e71d912d8f0860327f11eb48b345f204fab460f.066019d2.png)

Selecting an existing connection:

![](/assets/image-20191209-213912.1158934303b449607aef805057e01884b5c0d0e9d6fc1897ff101b9c0fd8d38a.066019d2.png)

### Configure the connection by specifying the parameters

After you select your *Supership* connection, the *Configuration* dialog pane appears:

![](/assets/image-20191209-213926.0ec9d1cef97368c6aad76f44f2b48e1cfc5460d8eb1a7be798c4c9b38a1e1034.066019d2.png)

### Table Name

The table name will be the segment name in Supership.

### (Optional) Schedule Query Export Jobs

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.

#### Scheduling your Job Using TD Console

1. Navigate to **Data Workbench > Queries**
2. Create a new query or select an existing query.
3. Next to **Schedule**, select None.
![](/assets/image2021-1-15_17-28-51.f1b242f6ecc7666a0097fdf37edd1682786ec11ef80eff68c66f091bc405c371.0f87d8d4.png)
4. In the drop-down, select one of the following schedule options:
![](/assets/image2021-1-15_17-29-47.45289a1c99256f125f4d887e501e204ed61f02223fde0927af5f425a89ace0c0.0f87d8d4.png)
| Drop-down Value | Description |
|  --- | --- |
| Custom cron... | Review [Custom cron... details](#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. |


#### Custom cron... Details

![](/assets/image2021-1-15_17-30-23.0f94a8aa5f75ea03e3fec0c25b0640cd59ee48d1804a83701e5f2372deae466c.0f87d8d4.png)

| **Cron Value** | **Description** |
|  --- | --- |
| `0 * * * *` | Run once an hour. |
| `0 0 * * *` | Run once a day at midnight. |
| `0 0 1 * *` | Run once a month at midnight on the morning of the first day of the month. |
| "" | Create a job that has no scheduled run time. |



```
 *    *    *    *    *
 -    -    -    -    -
 |    |    |    |    |
 |    |    |    |    +----- 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:

| Field Value | Example | Example Description |
|  --- | --- | --- |
| A single value, within the limits displayed above for each field. |  |  |
| A wildcard `'*'` to indicate no restriction based on the field. | `'0 0 1 * *'` | Configures the schedule to run at midnight (00:00) on the first day of each month. |
| A range `'2-5'`, indicating the range of accepted values for the field. | `'0 0 1-10 * *'` | Configures the schedule to run at midnight (00:00) on the first 10 days of each month. |
| A list of comma-separated values `'2,3,4,5'`, indicating the list of accepted values for the field. | `0 0 1,11,21 * *'` | Configures the schedule to run at midnight (00:00) every 1st, 11th, and 21st day of each month. |
| A periodicity indicator `'*/5'` to express how often based on the field's valid range of values a schedule is allowed to run. | `'30 */2 1 * *'` | Configures the schedule to run on the 1st of every month, every 2 hours starting at 00:30. `'0 0 */5 * *'` configures the schedule to run at midnight (00:00) every 5 days starting on the 5th of each month. |
| A comma-separated list of any of the above except the `'*'` wildcard is also supported `'2,*/5,8-10'`. | `'0 0 5,*/10,25 * *'` | Configures the schedule to run at midnight (00:00) every 5th, 10th, 20th, and 25th day of each month. |


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


### Execute the Query

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.

Scheduled jobs that continuously fail due to configuration errors may be disabled on the system side after several notifications.

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

## Activate a Segment in Audience Studio

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.


![](/assets/ouput.b2c7f1d909c4f98ed10f5300df858a4b19f71a3b0834df952f5fb24018a5ea78.8ebdf569.png)

- 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 Columns**to 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.


1. Set a **Schedule**.


![](/assets/snippet-output-connector-on-audience-studio-2024-08-28.a99525173709da1eb537f839019fa7876ffae95045154c8f2941b030022f792c.8ebdf569.png)

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


1. Select **Create**.


If you need to create an activation for a batch journey, review [Creating a Batch Journey Activation](/products/customer-data-platform/journey-orchestration/batch/creating-a-batch-journey-activation).