# Kakao Moment Export Integration

This feature is in BETA version. For more information, contact your Customer Success Representative.

Kakao Moment APIs allow you to retrieve and control the information related to ad accounts, campaigns, ad groups, and creatives configured on the Kakao Moment platform and to check metrics through reports. This Kakao Moment Export Integration enables you to upload job results from Treasure Data onto Kakao Customer Files directly.

This topic includes:

## What can you do with this Integration?

- Upload customer file contain ADID (Advertising Identifier - for both Android and Apple devices) data to Kakao Moment


## Prerequisites

- Basic knowledge of Treasure Data, including the [TD Toolbelt](https://toolbelt.treasuredata.com/).
- Kakao moment account.


## Requirements and Limitations

- Query columns must be specified with exact column names (case insensitive) and data type.


## Static IP Address of Treasure Data Integration

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 link:
[https://api-docs.treasuredata.com/en/overview/ip-addresses-integrations-result-workers/](https://api-docs.treasuredata.com/en/overview/ip-addresses-integrations-result-workers/)

## Use the TD Console to Create a Connection

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

## Create a New Authentication

1. Open **TD Console**.
2. Navigate to **Integrations Hub** > **Catalog**.
3. Search for Kakao Moment and select Kakao Moment.
![](/assets/image2023-7-21_18-37-11.26da296058a3d7eb1e48acd0b5bc07664e497ae8d64f39e4629cf70dd2426597.7a8868d5.png)
4. Select the **Click here** link in New Authentication to connect to a new Kakao Moment Account.
![](/assets/image2023-7-21_18-39-10.f99a11954ee1e202bc777d6173922402cccd34845138fbb02645e6395bed9ff8.7a8868d5.png)
5. You will be redirected to Kakao Moment to log in using OAuth. Provide the username and password.
![](/assets/image2023-7-21_18-42-5.59622f7142de8d40eb5b271971f20461cc06525714a9f2a652d064c0e7fd1ca1.7a8868d5.png)
6. Select **Log In** and it would redirect back to TD console.
7. Select **Continue**.
8. Type a name for your connection.
9. Select **Done**.


## Define your Query

1. Navigate to **Data Workbench > Queries**.
2. Select **New Query.**
3. Run the query to validate the result set.
![](/assets/image2021-9-7_15-1-38.a0ef34a3cfb6035eb6a53a758a755062decbb29fac046d1b24440a76d0662c7a.7a8868d5.png)
Export query only supports **adid** column (case insensitive). And, data type of **adid** column must be **string**.

```
select adid from table;
```
Alternatively, you can use alias to make your query columns name match with **adid** fields.
Sample query:

```
select column_a as adid from table;
```


## Specify the Result Export Target

1. Select**Export Results.**![](/assets/image2021-9-7_15-10-56.ee7ed43caab64adefafcc22595462fd8068c974c4f47b5959a7babd7d99972b8.7a8868d5.png)
2. Select an existing integration authentication.
![](/assets/image2020-12-18_13-44-6.09e8af43184e33e337bef7c546600eaaa5be9f010b690af1d591c7c2b4bb2df3.7a8868d5.png)
3. Define any additional Export Results details. In your export integration content, review the integration parameters.


## Register or Edit Customer File

1. Select **Register** or **Edit** mode.


| Parameter | Required | Description |
|  --- | --- | --- |
| Data Source | yes | `Customer File` |
| Ad Account ID | yes | Kakao moment Ad Account ID |
| Mode | yes | **Register**: Register customer file **Edit**: Edit customer file |
| Customer File Name | yes | `Customer file name upload` |
| When data size is greater than 200MB | yes, if mode is edit | **Stop**: Stop process data and throw error on current job.  **Send first 200MB only**: Only upload first 200MB data and ignore left over. |


In **Register** mode, if data size is larger than 200MB, split data to multiple files (200MB per file) and then upload each file to Kakao moment customer files. The second file and later should be named by file name config concat with **_{index}.**

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

## (Optional) Configure Export Results in Workflow

Within Treasure Workflow, you can specify the use of this integration to export data.

Learn more about [Exporting Data with Parameters](https://docs.treasuredata.com/smart/project-product-documentation/exporting-data-with-parameters).

### Example Workflow for register customer file


```
_export:
  td:
    database: kakao_db
 
+kakao_task:
  td>: upload.sql
  database: ${td.database}
  result_connection: new_kakao_auth
  result_settings:    
  	type: kakao_moment
  	data_source: customer_file
  	ad_account_id: ad_account_id
  	mode: register
  	file_name: test
```

### Example Workflow for edit customer file


```yaml
_export:
  td:
    database: kakao_db
 
+kakao_task:
  td>: delete.sql
  database: ${td.database}
  result_connection: new_kakao_auth
  result_settings:    
	type: kakao_moment
  	data_source: customer_file
  	ad_account_id: ad_account_id
  	mode: edit
  	file_name: test
	action: stop
```