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:
- Upload customer file contain ADID (Advertising Identifier - for both Android and Apple devices) data to Kakao Moment
- Basic knowledge of Treasure Data, including the TD Toolbelt.
- Kakao moment account.
- Query columns must be specified with exact column names (case insensitive) and data type.
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/
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.
Open TD Console.
Navigate to Integrations Hub > Catalog.
Search for Kakao Moment and select Kakao Moment.

Select the Click here link in New Authentication to connect to a new Kakao Moment Account.

You will be redirected to Kakao Moment to log in using OAuth. Provide the username and password.

Select Log In and it would redirect back to TD console.
Select Continue.
Type a name for your connection.
Select Done.
Navigate to Data Workbench > Queries.
Select New Query.
Run the query to validate the result set.

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;
- SelectExport Results.

- Select an existing integration authentication.

- Define any additional Export Results details. In your export integration content, review the integration parameters.
- 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}.
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.
Navigate to Data Workbench > Queries
Create a new query or select an existing query.
Next to Schedule, select None.

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.

| 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. |
- (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.
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.
You can also send segment data to the target platform by creating an activation in the Audience Studio.
- Navigate to Audience Studio.
- Select a parent segment.
- Open the target segment, right-mouse click, and then select Create Activation.
- In the Details panel, enter an Activation name and configure the activation according to the previous section on Configuration Parameters.
- 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.
- + Add string to create strings for export. Select from the following values:
- Set a Schedule.

- Select the values to define your schedule and optionally include email notifications.
- Select Create.
If you need to create an activation for a batch journey, review Creating a Batch Journey Activation.
Within Treasure Workflow, you can specify the use of this integration to export data.
Learn more about Exporting Data with Parameters.
_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_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