Yahoo Pixel

Datafly Signal sends conversions to Yahoo DSP server-to-server through the Standard Yahoo Conversion API.

Prerequisites

Request credentials

Generate a key pair, send the public key to your Yahoo account team and decrypt the credentials file they return (client ID and client secret).

Create a Conversion API pixel

Under Advertiser > Tracking create a new pixel for the API. Do not reuse a pixel that fires on the website.

Create rules

Build conversion rules on the event name (Event Type Action) and product category.

Configure in Signal

Configuration Fields

Field	Required	Description
`pixel_id`	Yes	A pixel ID created for the Conversion API under Advertiser > Tracking in Yahoo DSP. Do not reuse a pixel that fires on the website (double counting).
`client_id`	Yes	The Conversion API client ID from the encrypted credentials file Yahoo sends after you share a public key with your Yahoo account team.
`client_secret`	Yes	The client secret from the same credentials file; it signs the JWT used to request an access token.

Management UI Setup

Go to Integrations > Add Integration > Yahoo Pixel.
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://batch.datax.yahoo.com/v1/events/10157549

[
  {
    "actionSource": "web",
    "actionSourceUrl": "https://shop.example.co.uk/checkout/done?x=1",
    "eventData": {
      "price": 259.99,
      "products": [
        {
          "category": "Jackets"
        },
        {
          "category": "Accessories"
        }
      ]
    },
    "eventId": "ORD-1001",
    "eventName": "purchase",
    "eventTs": 1758500000,
    "userData": {
      "email": [
        "86e0b9e56c17cc4d12387e1949b85053fbe73bc3ce5a1188713a9d300cc6133d"
      ],
      "ip_address": "203.0.113.9",
      "phone": [
        "9e1919ad78a34fd67a84bfbcf2fea14074065517bea32e92924771c3f92e5462"
      ],
      "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7)"
    }
  }
]

A JSON array of events with eventTs, eventId, actionSource, actionSourceUrl, eventName, userData, eventData and, when marketing consent is denied, privacy.privacy_type: OPTOUT. 200 requests per second.

Event Mapping

Signal event	Vendor event	Presets
`page`	`page_view`	Default, Retail, Lead Generation, Insurance
`view_item`	`view_item`	Default, Retail
`add_to_cart`	`add_to_cart`	Default, Retail
`begin_checkout`	`begin_checkout`	Default, Retail
`purchase`	`purchase`	Default, Retail, Insurance
`generate_lead`	`generate_lead`	Default, Retail, Lead Generation
`sign_up`	`sign_up`	Default, Retail, Lead Generation
`add_to_wishlist`	`add_to_wishlist`	Retail
`add_payment_info`	`add_payment_info`	Retail
`lead_submitted`	`lead_submitted`	Lead Generation
`quote_requested`	`quote_requested`	Insurance
`quote_completed`	`quote_completed`	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

userData carries email and phone (normalised SHA-256 arrays), ip_address and userAgent. Yahoo requires an email, phone, device ID or partner ID. Signal cannot yet send the mobile advertising ID, which Yahoo takes as idfa on iOS and gpsaid on Android, so events without an email or phone are not sent.

Yahoo DSP is an advertising destination and requires marketing consent by default.

Troubleshooting

Problem	Solution
Token request fails	Yahoo’s token service needs a signed JWT client assertion, which Signal cannot build yet (#1451). This integration cannot deliver until then.

Blueprint

The Yahoo Pixel blueprint version is 0.5.1. It was last reviewed against the vendor’s documentation on 2026-09-22.