Yahoo Japan Ads
Datafly Signal sends conversions to LY Ads (Yahoo! JAPAN) Display Ads server-to-server through the Conversion API.
Prerequisites
Issue an Application ID
On the Yahoo! Developer Network issue an Application ID (Client ID). “No ID linkage” is fine.
Copy the request parameters
In the ad manager open the conversion setting and copy yahoo_ydn_conv_io and yahoo_ydn_conv_label from Conversion API request parameters. Each label is one conversion: install one integration per conversion you measure.
Configure in Signal
Configuration Fields
| Field | Required | Description |
|---|---|---|
app_id | Yes | Your Yahoo! JAPAN Developer Network Application ID (Client ID). Sent as the User-Agent value ‘Yahoo AppID: <AppID>’. Create one at the Yahoo! Developer Network and link it to the ad account. |
yahoo_ydn_conv_io | Yes | Account-specific conversion identifier from your Display Ads conversion measurement tag. Found in the Yahoo! JAPAN Ads UI under Conversion Measurement > tag details. |
yahoo_ydn_conv_label | Yes | The conversion tag label that identifies which conversion this event counts toward. Found alongside the Conversion IO in the conversion tag details. |
Management UI Setup
- Go to Integrations > Add Integration > Yahoo Japan Ads.
- Choose a preset: Default (
default), Retail (ecommerce), Lead Generation (lead_gen), Insurance (insurance). - Fill in the fields above and click Save.
Request format
POST https://ads-cv.yahooapis.jp/v1/
{
"event_time": 1758500000,
"hashed_email": "86e0b9e56c17cc4d12387e1949b85053fbe73bc3ce5a1188713a9d300cc6133d",
"hashed_phone_number": "9e1919ad78a34fd67a84bfbcf2fea14074065517bea32e92924771c3f92e5462",
"ip": "203.0.113.9",
"referrer": "https://www.example.com/",
"url": "https://shop.example.co.uk/checkout/done?x=1",
"user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7)",
"yahoo_ydn_conv_io": "1EALEzSJBNabcdEFGBE1",
"yahoo_ydn_conv_label": "AB0ABCDEFGHIJKLMNOP123456",
"yahoo_ydn_conv_transaction_id": "ORD-1001",
"yahoo_ydn_conv_value": 259.99,
"yclid": "YJAD.1234567890.1EALEzSJBNabcdEFGBE1"
}One conversion per request: event_time (Unix seconds, within 90 days), yahoo_ydn_conv_io, yahoo_ydn_conv_label, at least one match key, and optionally yahoo_ydn_conv_transaction_id (de-duplication, up to 64 bytes), yahoo_ydn_conv_value, ip, user_agent, url and referrer. The API answers 201 even when it excludes an invalid or duplicate conversion. 500 requests per second per Application ID.
Event Mapping
| Signal event | Vendor event | Presets |
|---|---|---|
purchase | conversion | Default, Retail |
generate_lead | conversion | Lead Generation |
lead_submitted | conversion | Lead Generation |
quote_completed | conversion | Insurance |
Signal forwards properties the preset does not map unless the integration’s strict output contract is on. Turn on strict_output_contract for this integration so only the documented fields are sent.
Identity
Match keys: yclid, hashed_email and hashed_phone_number (normalised SHA-256; phone in E.164, national numbers fall back to Japan) and ifa (mobile advertising ID). Events with none are not sent.
Consent
LY Ads is an advertising destination and requires marketing consent by default.
Troubleshooting
| Problem | Solution |
|---|---|
| 401 / 403 | The Application ID is missing or invalid. |
Blueprint
The Yahoo Japan Ads blueprint version is 0.5.0. It was last reviewed against the vendor’s documentation on 2026-09-22.