Yahoo Export Integration

Copy

• Copy for LLM

  Copy page as Markdown for LLMs
• View as Markdown

  Open this page as Markdown
• Open in ChatGPT

  Get insights from ChatGPT
• Open in Claude

  Get insights from Claude
• Connect to Cursor

  Install MCP server on Cursor
• Connect to VS Code

  Install MCP server on VS Code

The Yahoo! integration exports customer segments for advertising purposes.

• You can upload user id through Partnermatch API
• You can upload User and Audience Attribute to Yahoo!

Consumers expect a seamless online experience, whether they’re shopping, banking, reading the news, gaming, or watching videos, no matter where they are or what device they’re using. Yahoo! content delivery network (CDN) is trusted by some of the world's largest brands for online banking, e-commerce, and media distribution because it offers high quality, performance, reliability, and scale that improve the customer experience and increase loyalty.

Yahoo! helps you:

• Captivate audiences at scale.
• Serve the right ad at the right time.
• Unify Disney and ABC digital broadband messaging.

This topic contains:

What can you do with this Integration?

• Match your customer base with the fan base of Yahoo! to deliver the best personalized experience.
• Synchronize the segments created on TD with Yahoo!, including custom attributes to provide better categorization and build performant campaigns.
• Upload or remove audiences to or from Yahoo! segment for Yahoo! DMP ads targeting.

Prerequisites

• Basic Knowledge of Treasure Data.
• Basic knowledge of Yahoo! DataX API
• MDM ID provided by Yahoo! support

Requirements and Limitations

The DataX API performs in an asynchronous manner. All operations from the connector take effect ranging from 30 minutes to more than a day. If you need to download the job result, contact TD support.

Yahoo! and Provider limitations:

• 100 API calls per hour
• 5GB zipped file upload limitation

TD does not support watching the status of the upload segments. You can watch the status by reviewing the TD log.

Obtain Your MDM ID

Contact Yahoo! Support for your MDM ID.

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 Yahoo!.
   
4. Select Create Authentication.
   
5. Type your MDM ID. For example, OH224.
   
6. Type a name for your connection.
7. Select Done.

Define your Query

Integration Parameters for Yahoo!

Supported columns for each Mode

Pattern Match:

Query example

select  'abc@tese.com' as email, 'abc' as pxid
UNION ALL SELECT 'abc123@tese.com' as email, 'a12bc' as pxid
UNION ALL SELECT 'abcadcc@tese.com' as email, 'ab1231c' as pxid
select  'abc@tese.com' as email, 'abc' as pxid, '+112345678' as phone
UNION ALL SELECT 'abc123@tese.com' as email, 'a12bc' as pxid, '+134567182' as phone
UNION ALL SELECT 'abcadcc@tese.com' as email, 'ab1231c' as pxid, '+1456104632' as phone

Audience:

Query example

SELECT urn, CT01, GEN, seg_ts, seg_exp, att_ts, att_exp
FROM audiences

Taxonomy

Opt-out

Taxonomy

Taxonomy helps Yahoo import the hierarchical (or flat) organization of its partners’ data and its associated metadata. Uploading taxonomy is a prerequisite for uploading user/audience data.

General concept

• TD Root: All accounts will be created under single root name "Private" (default ID: TD0001). All client sub trees must be appended under this root.
• Each account (represent by MDM ID) will have only one tree (Account tree) with single root E.g Account A.
• The ID of each tree node is unique across all accounts.
• Each node type only accept SEGMENT or ATTRIBUTE

Example of an Treasure Data Taxonomy tree with client subtrees:

+ Private (TD0001)   
  ├-- Account A
  |  ├── seg1 name(seg1)
  |  │   ├── seg1.1 name(seg1.1)
  |  │   └── seg1.2 name(seg1.2)
  |  └── root attribute name 100(root attribute 100)
  |      └── att1 name(att1)
  ├-- Account B
      ├--- Seg AB

The connector supports 4 modes for Taxonomy tree structure upload:

• Whole Structure
• Append Node
• Replace Node
• Delete Node

Whole Structure: This is default mode for Taxonomy. Upload whole tree structure and keep new nodes only. The old nodes from current account tree will be deleted and replaced with new nodes from new tree. Validation:

• The Account Root node have ID = null (in database parent_id = null), the ID column is required.
• Orphan nodes which have no parent are not allowed.
• Only leaf nodes can be deleted each run.
• If the account Node doesn’t exist, it will append to the TD Root or Private (TD0001).

Only one root (with parent_id = null) is allowed.

Append Node

Append single node or a sub tree into an existing parentId node. If the company tree not created then new tree will be create with input root and it will be appended under TD Root.

Validation:

• If account tree doesn't exist then new account tree is created with one input root and it will be appended to Private (default ID: TD0001).
• If account tree doesn't exist then maximum 1 root node is allowed in query result.
• If account tree exists then root node is not allowed. in the query result.
• Parent Id of each node must be existed when company root is not null.
• Append node must not be in used if company tree not null.

E.g:

Current account tree

root segment name 200 (root segment 200)
├── SEG Child 6 (seg6)
├── SEG Child 2 (seg2)
├── SEG Child 5 (seg5)
│   ├── SEG Child 5.1 (seg5.1)
│   └── SEG Child 5.2 (seg5.2)
├── SEG Child 4(seg4)
│   ├── SEG Child 4.3 (seg4.3)
│   └── SEG Child 4.1 (seg4.1)
└── SEG Child 3 (seg3)
    ├── SEG Child 3.1 (seg3.1)
    └── SEG Child 3.2 (seg3.2)

Input data

SELECT parent_id, id, name, type
FROM 
(
   VALUES 
   ('TD0008','seg8.1','SEG 8.1','SEGMENT')
) tbl (parent_id,id,name,type);

The expected tree will be look like below:

root segment name 200 (root segment 200)
├── SEG Child 6 (seg6)
│   ├── SEG Child 6.1 (seg6.1)
│   └── SEG Child 6.2 (seg6.2)
├── SEG Child 2 (seg2)
├── SEG Child 5 (seg5)
│   ├── SEG Child 5.1 (seg5.1)
│   └── SEG Child 5.2 (seg5.2)
├── SEG Child 4 (seg4)
│   ├── SEG Child 4.3 (seg4.3)
│   └── SEG Child 4.1 (seg4.1)
├── SEG Child 3 (seg3)
│   ├── SEG Child 3.1 (seg3.1)
│   └── SEG Child 3.2 (seg3.2)
├── SEG 8 (seg8)
│   └── SEG Child 8.1 (seg8.1)
└── SEG 7 (seg7)

Replace NodeReplace existing taxonomy node and its sub-tree with a new taxonomy data. Do not allow to replace Company roots or TD root. Only sub trees of company root are allowed to replace.

Validation:

• Account tree must exist to do this operation.
• Input subtree roots must not be empty.
• Replacing account root is not allowed.
• Replacing TD root (Private) is not allowed.
• Input tree root node must be under account tree.

E.g

We have an account tree as below

Sample TD Segment(TD0002)
├── Child 1(TD0003)
│   └── Child 1.1(TD0007)
│       └── Child 1.1.1(TD0008)
│           └── SEG 8.1(seg8.1)
└── Child 2(TD0004)
    ├── Child 2.1(TD005)
    │   └── Child 2.1.1(TD005_1)
    └── Child 2.2(TD0006)
        └── Child 2.2.2(TD0006_1)

We expect to build this hierarchy from the SQL data

SELECT parent_id, id, name, type
FROM 
(
   VALUES 
   ('','TD0007','Child 1.1','SEGMENT'),
   ('TD0007','TD0008','Child 1.1.1','SEGMENT'),
   ('TD0007','TD0009','Child 1.1.2','SEGMENT'),
   ('TD0007','TD0010','Child 1.1.3','SEGMENT')
) tbl (parent_id,id,name,type);

Then the expected tree will become like this

Sample TD Segment(TD0002)
├── Child 1(TD0003)
│   └── Child 1.1(TD0007)
│       ├── Child 1.1.2(TD0009)
│       ├── Child 1.1.1(TD0008)
│       └── Child 1.1.3(TD0010)
└── Child 2(TD0004)
    ├── Child 2.1(TD005)
    │   └── Child 2.1.1(TD005_1)
    └── Child 2.2(TD0006)
        └── Child 2.2.2(TD0006_1)

Replace NodeDelete existing taxonomy node along with its sub-tree.

Validation:

• Do not allow to delete any tree roots (Account Root or TD Root).
• Node must not be null & exists in account tree.
• Company tree must exist to do this operation.

E.g:

We have an account tree as below

Sample TD Segment(TD0002)
├── Child 1(TD0003)
│   └── Child 1.1(TD0007)
│       └── Child 1.1.1(TD0008)
└── Child 2(TD0004)
    ├── Child 2.1(TD005)
    │   └── Child 2.1.1(TD005_1)
    └── Child 2.2(TD0006)
        └── Child 2.2.2(TD0006_1)

We expect to build this hierarchy from the SQL data

SELECT parent_id,id,name,type
FROM 
(
   VALUES 
   ('','TD005_1','Child 2.1.1','SEGMENT')
)tbl (parent_id,id,name,type);

Then the expected tree will become like this

Sample TD Segment(TD0002)
├── Child 1(TD0003)
│   └── Child 1.1(TD0007)
│       └── Child 1.1.1(TD0008)
└── Child 2(TD0004)
    ├── Child 2.1(TD005)
    └── Child 2.2(TD0006)
        └── Child 2.2.2(TD0006_1)

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

4. 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.

Custom cron... Details

 *    *    *    *    *
 -    -    -    -    -
 |    |    |    |    |
 |    |    |    |    +----- 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:

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.

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

• 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.

6. Set a Schedule.

• Select the values to define your schedule and optionally include email notifications.

7. Select Create.

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

Yahoo! Configuration Keys

Example Workflow for Yahoo!

_export:
  td:
  database: td.database
 
+verizon_media_export_task:
  td>: export_verizon_media.sql
  database: ${td.database}
  result_connection: verizon_media
  result_settings:
    type: verizon_media
    upload_mode: audience
    urn_type: Email

(Optional) Export Integration Using the CLI

You can also use the CLI provided by TD Toolbelt to export query results to Yahoo!.

Using the td query command, you would specify the LINE conversion server URL with the --result RESULT_URL option.  See td query for more information.

The format of the option is JSON and the general structure is as follows.

{
  "type": "verizon_media",
  "mdm_id": "100",
  "upload_mode": "taxonomy",
  "taxonomy_mode": "append_node"
}

Parameters

Example for Usage

td query \
  --result '{
    "type": "verizon_media",
    "upload_mode": "taxonomy",
    "taxonomy_mode": "append_node",
    "mdm_id": "100"
  }' \
  -d sample_datasets \
  "SELECT * FROM verizon_media_tbl" \
  -T presto