---
title: Yahoo Pixel
slug: yahoo-pixel
docTags: 
createdAt: 2026-02-04T22:59:00.424Z
---

**Yahoo Pixel** (Yahoo Dot Tag) is Yahoo's conversion tracking and audience pixel for Yahoo Advertising campaigns. This destination loads the Yahoo Dot Tag JavaScript SDK in the browser and forwards ecommerce events to Yahoo for conversion measurement and audience building. User emails and phone numbers are hashed before sending. There is no server-side component.

# Getting Started

This is a device-mode destination. The Yahoo Dot Tag SDK is loaded automatically — no manual script installation is required. You will need:

- **Pixel ID** — your Yahoo pixel ID, found in your Yahoo Advertising account.
- **Project ID** — your Yahoo project ID, found in your Yahoo Advertising account.

# Connecting to the Yahoo Pixel CDP Destination

:::BlockQuote
**Warning:** Before connecting destinations in the Chord CDP, please verify with all Destination owners that all **non-Chord CDP** configured destinations are **disabled**. Running external destinations alongside configured Chord CDP destinations **can result in duplicate events downstream.**
:::

1. Log into the Chord data platform.
2. Navigate to the CDP.
3. Click the **"Add"** button next to Destinations.
4. Select **Yahoo Pixel** from the destination catalog.
5. Enter the destination name, **Pixel ID**, and **Project ID**.
6. Click **"Create"** to connect.

# Events

All Yahoo Pixel events include SHA-256 hashed user data when available:

| Yahoo Attribute | Chord Source (Priority Order)                                | Notes                                  |
| --------------- | ------------------------------------------------------------ | -------------------------------------- |
| `he`            | `properties.email` > `context.traits.email` > `traits.email` | SHA-256 hashed, lowercased and trimmed |
| `hph`           | `properties.phone` > `context.traits.phone` > `traits.phone` | SHA-256 hashed, lowercased and trimmed |

# Event Mapping

| Chord Event        | Yahoo Event Action (`ea`)               |
| ------------------ | --------------------------------------- |
| `page`             | *(auto page view on init)*              |
| `identify`         | Re-pushes config with updated user data |
| `Product Viewed`   | `ViewProduct`                           |
| `Product Added`    | `AddToCart`                             |
| `Checkout Started` | `BeginCheckOut`                         |
| `Order Completed`  | `Purchase`                              |

All other track events are silently skipped.

# Page Events

Page views are tracked automatically during pixel initialization. Subsequent page events do not fire additional calls to avoid double-counting.

# Identify Events

Re-pushes the pixel configuration with updated hashed user data (email and phone) for enhanced matching.

**Yahoo SDK call:** `dotq.push({ projectId, properties: { pixelId, he, hph } })`

# Product Viewed

**Yahoo SDK call:** `dotq.push({ projectId, properties: { pixelId, he, hph, qstrings } })`

| Yahoo Attribute (`qstrings`) | Chord Source (Priority Order)                                                                      | Notes                |
| ---------------------------- | -------------------------------------------------------------------------------------------------- | -------------------- |
| `et`                         | *(hardcoded)* `"custom"`                                                                           |                      |
| `ea`                         | *(hardcoded)* `"ViewProduct"`                                                                      |                      |
| `product_id`                 | `properties.product_id` > `properties.sku` > `properties.id` > `properties.products[0].product_id` | Omitted if not found |

# Product Added

Same payload structure as **Product Viewed**, with `ea` set to `"AddToCart"`.

# Checkout Started

Same payload structure as **Product Viewed**, with `ea` set to `"BeginCheckOut"`.

# Order Completed

**Yahoo SDK call:** `dotq.push({ projectId, properties: { pixelId, he, hph, qstrings } })`

| Yahoo Attribute (`qstrings`) | Chord Source (Priority Order)                                  | Notes                                        |
| ---------------------------- | -------------------------------------------------------------- | -------------------------------------------- |
| `et`                         | *(hardcoded)* `"custom"`                                       |                                              |
| `ea`                         | *(hardcoded)* `"Purchase"`                                     |                                              |
| `product_id`                 | Same as Product Viewed above                                   | Omitted if not found                         |
| `gv`                         | `properties.total` > `properties.revenue` > `properties.value` | Conversion value; omitted if not found       |
| `el`                         | `properties.order_id`                                          | Event label (order ID); omitted if not found |

# Initialization

The plugin initializes the `window.dotq` queue with the pixel configuration, then loads `https://s.yimg.com/wi/ytc.js`. After the script loads, it wires up the Yahoo beacon function to process queued events and handle future pushes.

The plugin manages SDK loading state (`fresh` → `loading` → `loaded`/`failed`) to prevent duplicate script loads. If the script fails to load, subsequent events are silently dropped.

# CSP Requirements

If your site uses a Content Security Policy, allow the following domains:

| Directive     | Domain               |
| ------------- | -------------------- |
| `script-src`  | `https://s.yimg.com` |
| `connect-src` | `https://s.yimg.com` |

***

**Updated 6 Apr 2026**