# Yahoo Japan Ads V2 Export Integration

Yahoo! JAPAN Ads supports companies' marketing activities with simple settings, various marketing channels, and flexible expandability. Strategic marketing communication is possible due to the various advertising distribution aspects unique to Yahoo! JAPAN.

With this integration, Treasure Data helps you send your user segment to Yahoo! JAPAN Ads by allowing you to create an audience list and upload first-party data into this list on Yahoo! JAPAN Ads.

## Prerequisites

- Treasure Data account
- Yahoo! JAPAN Ads accounts
- User needs to have access to their MCC account and have Tool administrator permission (Tool admin)


## Limitations

- The integration uploads files to Yahoo! JAPAN. The upload could fail, and customers are required to check the Yahoo! JAPAN Ads console to verify the result.


## Exporting to Yahoo! JAPAN Ads

### Get Base Account ID and Account ID in Yahoo! JAPAN Ads

1. Log in to [Yahoo! Business Center](https://business.yahoo.co.jp/).
![](/assets/yahoojapan.7229d785268ee3c9dc4f10ebd7f8768213092ec8193e9869c6144309d3111149.9657f1af.png)
2. Select **advertising management tools.**
3. Record the Base Account ID and the Account ID.
![](/assets/yahoo-japan-ads-v2-export-integration-2024-05-13-1.1600b09dcd16687fa5665ed4c0b5bbb2560b78d41744380555f998721e09d6bf.9657f1af.png)


### ​Check Upload Audience List status in Yahoo! JAPAN Ads

1. From Account ID dashboard choose **Tool > Library / Audience List**.
![](/assets/yahoo-japan-ads-v2-export-integration-2024-05-13-2.becab92595a552522e33098cf5926dd90a726850d8fbfa17bdbf9d13275122c8.9657f1af.png)
2. At column linked data click on detail to see upload status
![](/assets/yahoo-japan-ads-v2-export-integration-2024-05-13-3.2dae6f7856b697380b295011e333acca0d0a57ce90833610e1e0f455da594048.9657f1af.png)


## Use the TD Console to Create Your Connection

### Create a New Connection

In Treasure Data console, you must create and configure the data connection for export before running your query. As part of creating the data connection, you provide authentication credentials for the integration to use.

1. Open the **TD Console**.
2. Navigate to **Integrations Hub > Catalog**.
3. Search for and select **Yahoo! Ads V2**. **![](/assets/yahooadsoutputv2.d853f06d4922b86ccdb9b44412ab1a763a8340fef0c15fe07fb416dd91aa3cb5.9657f1af.png)**The New Authentication dialog opens.
4. Select the "**Click here** to connect a new account" link.
5. Login in to a Yahoo! JAPAN Ads Account.
The Yahoo! Japan site will redirect back to to the TD console with the OAuth credential.
![](/assets/yahoo-japan-ads-v2-export-integration-2024-05-10-5.20c696eff33f00f2b688b4171f9a04959e4d6e3a273abe63813d7f80c061c7a6.9657f1af.png)
6. Enter a name for your connection.
7. Select **Done.**


### Define your Query

1. Navigate to **Data Workbench > Queries**.
2. Select **New Query**.
3. Define and run the query to validate the result set.
![](/assets/yahoo-japan-ads-v2-export-integration-2024-05-16-2.a43059a4255b9a943a6f83ae0c4b5403c3dd0a32bc3fecba710a0cd6aaba370b.9657f1af.png)
**Upload type value is AAID or IDFA or MAIL_ADDRESS:**
The export query only supports one column, and the column data type must be string. Additionally, you can only specify one identifier type per query, and the identifier type must be either *MAIL_ADDRESS*, *IDFA*, or *AAID*, which is specified using the "Upload Type" parameter.



```sql
SELECT email AS any_column_nameFROM profile_table
```

**Upload type value is MAIL_ADDRESS_AND_PHONE_NUMBER:**The export query must specify column/alias with name email or phone or both of email and phone.


```sql
SELECT email, phoneFROM profile_table
```

### Specify the Result Export Target

1. Select**Export Results**.
![](/assets/yahoo-japan-ads-v2-export-integration-2024-05-16.c33c6509ee8ae6f1029accfc9aca627830cd12932ce0e2236470be88e41eade5.9657f1af.png)
2. Select an existing integration authentication.
![](/assets/image2020-12-18_13-44-6.09e8af43184e33e337bef7c546600eaaa5be9f010b690af1d591c7c2b4bb2df3.7a8868d5.png)
3. Define any additional Export Results details.


### Integration Parameters for Yahoo! JAPAN Ads V2

The Export Results page accepts the following parameters:

| Parameter | Description |
|  --- | --- |
| `base_account_id` (required) | Base Account ID |
| `account_id` (required) | Account ID |
| audience_list_name (required) | Audience list name. If the name does not exist, a new audience list will be created with this name. |
| upload_type (required) | Upload type:- MAIL_ADDRESS: email or hashed email (SHA256). If your hash contains any uppercase letters, convert them to lowercase.
- MAIL_ADDRESS_AND_PHONE_NUMBER: Upload email, phone number, or both with the corresponding column names email and phone. The email and phone number can be raw or hashed (SHA-256).
- IDFA
- AAID

 |


### (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 Uploading Type mail_addess**


```yaml
_export:
　td:
　　database: yahoo_ads_v2_db

+yahoo_ads_v2_task:
  td>: upload.sql
  database: ${td.database}
  result_connection: new_yahoo_ads_v2_auth
  result_settings:     
    type: yahoo_ads_v2,
    base_account_id: base_account_id,
    account_id: account_id,
    audience_list_name: audience_list_name,
    upload_type: mail_address
```