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.

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 asynchrony 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! & 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.

Open TD Console.

Navigate to Integrations Hub > Catalog.

Search for and select Yahoo!.

Select Create Authentication.

Integrations > Yahoo! Export Integration > image2021-7-1_11-48-51.png

Type your MDM ID. For example, OH224.

Integrations > Yahoo! Export Integration > image2021-7-1_12-6-10.png

Type a name for your connection.

Select Done.

Define your Query

Integration Parameters for Yahoo!

Integrations > Yahoo! Export Integration > image2021-7-1_13-5-9.png

Parameter	Values	Description
Mode	Values are: Partner Match Audience Taxonomy Opt-out	Choose the upload mode Partner Match: upload user id/email through Partner Match API Audience: upload audience records Taxonomy: create/modify the taxonomy hierarchy Opt-out: remove audiences from the entire taxonomy hierarchy
URN Type	Values differ depending on the mode you have selected. Example types are: PXID GPADVID email DXID ZIP4 YAHID	Values differ depending on the mode you have selected. Uniform Resource Name (URN) identifies a resource or unit of information independent of its location. URNs are globally unique, persistent, and accessible over the network. Yahoo! syntax for an urn: "urn":{string}, "seg":[{"id":{string},"ts":{number},"exp":{number}}] For example, {"urn" : "99ff2333f3fe7659c38b3674bc927f32", "seg" : [{"id":"OH224"}]}
Target Segment ID	if Audience mode is selected.	ID of the target Segment. This combines with optional fields in the query result: seg_exp, seg_ts
GDPR	if Audience mode is selected.	General Data Protection Regulation (EU GDPR)
Dry Run	if Taxonomy is selected	Enable to verify if the synchronization is expected without updating the current Taxonomy.

Supported columns for each Mode

Pattern Match:

Column name	Type	Required	Description
Email	String	Yes	this column accepts plain text emails or SHA256 Hashed emails. Plain text email will be hashed before sending to Yahoo! server
PXID	String	Yes

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

Audience:

Column name	Type	Required	Description
urn	String	Yes	Values match your selected URN Type. Plain text email will be hashed before sending
<attribute_id>	Any type		Any attribute id defined in your Taxonomy. E.g. Age, Country, G123... You can have multiple attribute ID selected in your query
seg_ts	Long		Timestamp associated with the urn
seg_exp	Long		Expiration time associated with the urn
att_ts	Long		Timestamp associated with the attribute
att_exp	Long		Expiration time associated with the attribute

Query example

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

Taxonomy

Column name	Type	Required	Description
parent_id	String	Yes	Null value indicates Root taxonomy
id	String	Yes	Required value and must be unique across the entire company.
name	String	Yes	A human friendly equivalent of "id"
type	String	Yes	Current supported types are: SEGMENT, ATTRIBUTE
description	String
att_type	String		Attribute type. Current possible values are: ENUM, DATETIME, ZIPCODE, NUMBER, STRING. For more detail, refer to this external reference: https://developer.yahooinc.com/datax/guide/taxonomy/taxonomy-rep/.
att_values	String		Attribute values. Mandatory for ENUM and NUMBER types. Examples: For enums: [ “Loyal”, “Occasional”, “Rare” ] For numbers: [ “1\|25”, “56\|99”]
gdpr_mode	String

Opt-out

Column name	Type	Required	Description
urn	String	Yes	Values match your selected URN Type. Plain text email will be hashed before sending

Optionally Schedule the Query Export Jobs

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

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.

Yahoo! Configuration Keys

Name	Type	Required	Description
type	String	Yes	verizon_media
mdm_id	String	Yes	Your company MDM ID
upload_mode	String	Yes	PARTNER_MATCH, TAXONOMY, AUDIENCE_UPLOAD, OPT_OUT
urn_type	String	Yes	Apply for Audience upload only
partner_match_urn_type	String	Yes	Apply for Partner Match mode only
opt_out_urn_type	String	Yes	Apply for Opt-out mode only
target_segment_id	String		Upload audiences to this segment
gdpr	Boolean		Default true
taxonomy_dry_run	Boolean		Verify the Taxonomy upload job run only (without changing actual data). Default false

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