# Line Via Crescendo Lab Export Integration

LINE is in Asia what Facebook Messaging and Instagram are to US mobile users—a fast and easy way to communicate with friends and to discover new promotions about your favorite products and services. LINE is the number one mobile messaging platform in Taiwan. It is also one of the largest mobile messaging platforms in Japan and Thailand. Through Crescendo Labs MAAC API, we are developing an out-of-the-box integration to activate LINE. This integration allows you to authenticate using the API token, upload members with tags, and create and update segments with Line UIDs.

## Prerequisites

- Basic Knowledge of Treasure Data.
- Basic knowledge of MAAC Crescendo Experience Account


## Requirements and Limitations

The Connector implements minimal data validation, you must make sure your data is valid Line/Crescendo Lab spec to avoid job fail. For example, line_uid, email, mobile must be valid Line's data, birthday must be valid ISO format e.g. 1985-04-06.

## Use the TD Console to Create Your Connection

### Create a New Connection

In Treasure Data, you must create and configure the data connection prior to running your query. As part of the data connection, you provide authentication to access the integration.

1. Open **TD Console**.
2. Navigate to **Integrations Hub** > **Catalog**.
3. Search for and select Line via Crescendo.


![](/assets/image2021-7-28_8-55-18.337b50ff7e09c9ae0516e69cc2fd58853171c183ef0c9889e3345129cf10e220.46fd29ef.png)

1. Select Create Authentication.
2. Type the credentials to authenticate.
3. Type a name for your connection.
4. Select **Done**.


### Define your Query

Depending on the Data Object you've chosen, the supporting columns will be different.

### Data Object: Members

| Column | Data Type | Required | Description |
|  --- | --- | --- | --- |
| line_uid | string | Yes (if import key is line_uid) | The unique user ID of the member in the LINE official account |
| line_display_name | string | No | The name defined by the member in the official LINE account |
| email | string | Yes (if import key is email) | Member email address |
| mobile | string | Yes (if import key is mobile) | Member phone number |
| customer_id | string | Yes (if import key is customer_id) | User ID of the third-party system |
| gender | string | No | The gender of the member (default is predicted by MAAC AI) male: male female: female |
| birthday | string | No | Member's birthday (ISO Format) E.g. 2000-02-23 |
| tags | comma-separated strings | No | tags to tag to individual members |


### Data Object: Segments

| Column | Data Type | Required | Description |
|  --- | --- | --- | --- |
| line_uid | string | Yes | Line UID to be imported |


### Integration Parameters for Line via Crescendo Lab

![](/assets/image2021-11-17_12-48-0.35a1539a819eaf13048bd8c536d9651e55fbddde3273d79042f37c0efcdc188f.46fd29ef.png)

| Parameter | type | Required | Description |
|  --- | --- | --- | --- |
| Access Token (api_token) | String | Yes | Access token |
| Data Object (data_object)  `  ` | String | Yes | Members (members) or Segments (segments) |
| Import Key (import_key) | String | Yes (if Data Object is Members) | Value: line_uid, customer_id, email, or mobile |
| Tags (tags) | String | Yes | Comma-separated strings of tags |
| Segment Name (segment_name) | String | Yes (if Data Object is Segments) | Segment name |
| Description (segment_description) | String | No | Segment description |
| Skip Invalid Records (skip_invalid_records) | Boolean | No | Skip invalid records and continue the job (default: true) |
| All the existing records will be replaced when you update the segment (update_segment) | Boolean | No | Update existing segment |


### Example Query


```sql
SELECT
  line_uid,
  customer_id,
  display_name,
  gender,
  email,
  tags,
  birthday
FROM
  line_members
```

### (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).

## Optionally Configure Export Results in Workflow

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](https://api-docs.treasuredata.com/en/tools/cli/api/#workflow-commands).

### Example Workflow for Line via Crescendo


```yaml
timezone: UTC

_export:
  td:
    database: sample_datasets

+td-result-into-line:
  td>: queries/sample.sql
  result_connection: your_connection_name
  result_settings:
    api_token: ###
    data_object: members
    import_key: line_uid
    tags: import210707, apple product interested
```