This integration allows you to create advertising campaigns on Yahoo! Ads using a customized list of 1st party data from company websites and mission-critical systems related to Yahoo! Japan. Treasure Data helps you send your own user segment to Yahoo! Ads.

Yahoo! Ads supports the marketing activities of companies 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 the Treasure Data export, you can engage in:

  • Direct Targeting: Create a user segment on TreasureData using your own analysis. Then send it to Yahoo! Ads and set up a target campaign as a CustomList on Yahoo! Ads.
  • Custom Segment Targeting: Send user data with its attributions to analyze and create custom segments to Yahoo! Ads. Then set up a target campaign as a CustomList on Yahoo! Ads. 

The diagram describes the flow for Direct Targeting and Custom Segment Targeting.


  • Treasure Data account

  • Yahoo! Ads accounts


  • The connector only supports an upload of 1 GB of compressed records.
  • The integration just uploads files to Yahoo!. It could fail during importing and matching in Yahoo!. Hence, customers have to check the Yahoo! Ads console to verify if the parameters are valid.

About Identifying a User

With Treasure Data, you have the following ways to identify a user:


A 3rd party cookie provided by Treasure Data.

It allows you to identify users without implementing CookieSync on your end because the td_global_id is always synced on the Yahoo! Japan website.

hashed email

It allows you to identify users without Cookie. Emails sent to Yahoo! Ads create a user list by matching the same hashed email on Yahoo! Ads.

You must obtain the salt string from Yahoo! Japan in order to create a hash string.


Enables you to identify users with IDFA (Identifier for Advertisers) on iOS or ADID (AdvertisingId) on Android instead of using the cookie.

No longer recommended.

Exporting to Yahoo! Ads

 Create Audience List in Yahoo! Ads

  1. Log in to Yahoo! Business center, in the Display Ads tab, click on the Tools drop down list and open the Target Lists page. If you have difficulty navigating the Yahoo! Ads Campaign Management Tool layout, contact the Yahoo! Japan support team.

  2. Click on the Add Target List drop-down list and select the Create Custom List option.

  3. Check the Custom Audience ID / Target List ID.

  4. If the Audience List ID column is not shown, click on Display and select the Target List ID checkbox.

Get Brand ID on Yahoo! Ads for Treasure Integration

Please contact your Treasure Data Customer Success representative.

Use the TD Console to Create Your Connection

Create a New Connection

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

  1. Open TD Console.

  2. Navigate to Integrations HubCatalog.

  3. Search for and select Yahoo! Ads.

  4. The following dialog opens.

  5. Enter your Brand ID.

  6. Enter a name for your connection.

  7. Select Done.

Define your Query

  1. Complete the instructions in Creating a Destination Integration.
  2. Navigate to Data Workbench > Queries.

  3. Select a query for which you would like to export data.

  4. Run the query to validate the result set.

  5. Select Export Results.

  6. Select an existing integration authentication.
  7. Define any additional Export Results details. In your export integration content review the integration parameters.
    For example, your Export Results screen might be different, or you might not have additional details to fill out:
  8. Select Done.

  9. Run your query.

  10. Validate that your data moved to the destination you specified.

Integration Parameters for Yahoo! Ads

Set the following parameters:



user_list_type (required)

User list type:

  • direct_targeting

  • custom_segment_targeting

user_id_type (required)

User ID type:

  • cookie

  • email: the first column, uid, is an email or hashed email SHA256

  • IDFA: the first column, uid, is a UUID

  • AAID: the first column, uid, is a UUID

ignore_invalid_records (optional)

Ignore the invalid records.

custom_audience_id (optional)

Custom audience id (site retargeting id), required when user_list_type is direct_targeting

target_list_id (optional)

Audience list id, required when user_list_type is direct_targeting

client_id (optional)

Client id, required when user_list_type is custom_segment_targeting

data_source_number (optional)

Data source number, required when user_list_type is custom_segment_targeting

Here is a sample configuration:

  type: yahoo_dmp
  brand_id: brand_id
  user_list_type: direct_targeting
  user_id_type: hashed_email
  custom_audience_id: custom_audience_id
  target_list_id: target_list_id
  client_id: client_id
  data_source_number: data_source_number
  ignore_invalid_records: false

Example Query for Yahoo! Ads

For direct_targeting, Treasure Data supports one column with the format string or number. For example:

SELECT '' as uid;

For custom_segment_targeting, the first column is the UID and has a string or number format.

SELECT '' as uid,
       '012345' as sms,
       '123' as sid,
       'My Name' as name,
       'Mar 11' as dob; 

Or, write an SQL query to extract user data with attributes to analyze and create custom segments on Yahoo! Ads. The User ID must be the first column. For example, extract td_global_id with attributes:

td_global_id AS td_global_id,
MAX(td_os) AS type,
COUNT(td_global_id) AS price
GROUP BY td_global_id

Or for the raw email, you can hash by SQL before sending those to Yahoo! Ads. 

The data is compressed by gzip when it’s sent to Yahoo! Ads. If the compressed data exceeds 1GB, you have to split the data before sending.

  LOWER(TO_HEX(SHA256(TO_UTF8(CONCAT({Salt string}, email)))))

Optionally Schedule the Query Export Jobs

You can use Scheduled Jobs with Result Export to periodically write the output result to a specified target destination.

1. Navigate to Data Workbench > Queries.
2. Create a new query or select an existing query.
3. Next to Schedule, select None.

4. In the drop-down, select one of the following schedule options:

Drop-down ValueDescription
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.
NoneNo schedule.

Custom cron... Details

Cron Value


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 ValueExampleExample 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.
5.  (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 imported to the specified container destination.

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

Optionally Configure Export Results in Workflow

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

Learn more at Using Workflows to Export Data with the TD Toolbelt.

Extract the User List to Send to Yahoo! Ads

  1. Using your favourite text editor or the Treasure Data Workflow editor, open your Yahoo! Ads workflow file.
  2. Write a SQL query to extract the user list you want to send to Yahoo! Ads. See Creating and Deleting Files.

Run the Workflow to Send the User List to Yahoo! Ads

If you have just created a new custom target list Yahoo! Ads, wait for approximately an hour to run the workflow, because it can take time for the new list to be processed.

  1. Open TD Console.

  2. Navigate to Data Workbench > Workflows.

  3. Highlight your Yahoo! Ads workflow.
  4. Select the New Run button or define a schedule that runs the workflow repeatedly.

  5. Review your workflow results to make sure they were successful.

  6. Validate that the Reach number is correct after the workflow is done processing (which typically takes 3 - 4 hours).

Validate the Processing Status on Yahoo! Ads

If the Reach number remains at zero and is not updated after the 3-4 hour processing period, you can check the processing status in Yahoo! Ads.

  1. Validate the GUID value in the Workflow log for exporting to Yahoo! Ads API.

  2. Use an HTTP GET inquiry for the Yahoo! Ads API. For example:

    $ curl --location --request GET '<guid_value>' --header 'x-api-key: <x-api-key>'
  3. Replace the empty values with the relevant information.




GUID from workflow


x-API-key string that you used to set the workflow secrets. (Please contact TD for the api-key)







If you receive "status":"CREATED" as an HTTP result, the process has been completed in Yahoo! Ads successfully.

  • No labels