> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/activate/event-streaming/destinations/advertising/yahoo-dpa-pixel.md). # Yahoo DPA Pixel **Yahoo DPA 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 browser destination. Chord loads the Yahoo Dot Tag for you, so you don't install any script. You need your Yahoo pixel ID and project ID, both on the Dot page in the Yahoo DSP dashboard. ## Settings * **Destination Name** (required): a name to tell this destination apart. * **Pixel ID** (required) and **Project ID** (required): your Yahoo pixel ID and project ID, both on your Dot page in the Yahoo DSP dashboard. * **Consent Requirements** (optional): the consent categories a visitor must accept before Chord sends data to this destination. See [Consent](/activate/event-streaming/consent.md). ## Connect Add **Yahoo DPA Pixel** from the destination catalog, using the settings above. See [Connect a destination](/activate/event-streaming/connect-a-destination.md) for the full steps. ## Events All Yahoo DPA Pixel events include SHA-256 hashed user data when available: | Chord source (priority order) | Yahoo field | Notes | | ------------------------------------------------------------ | ----------- | -------------------------------------- | | `properties.email` > `context.traits.email` > `traits.email` | `he` | SHA-256 hashed, lowercased and trimmed | | `properties.phone` > `context.traits.phone` > `traits.phone` | `hph` | SHA-256 hashed, lowercased and trimmed | ## Event mapping | Chord event | Yahoo event | Notes | | --------------------------------------------------------------------- | --------------------------------------- | ----- | | `page` | *(auto page view on init)* | | | `identify` | Re-pushes config with updated user data | | | [`Product Viewed`](/collect-data/tracking-plan/product-viewed.md) | `ViewProduct` | | | [`Product Added`](/collect-data/tracking-plan/product-added.md) | `AddToCart` | | | [`Checkout Started`](/collect-data/tracking-plan/checkout-started.md) | `BeginCheckOut` | | | [`Order Completed`](/collect-data/tracking-plan/order-completed.md) | `Purchase` | | Chord skips all other track events and logs the skip in the browser console. An `Order Completed` with no products is also 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 } })` | Chord source (priority order) | Yahoo field | Notes | | --------------------------------------------------------------------------------------------------------------------------- | ------------ | -------------------- | | *(hardcoded)* `"custom"` | `et` | | | *(hardcoded)* `"ViewProduct"` | `ea` | | | `properties.product_id` > `properties.sku` > `properties.id` > `properties.productId` > `properties.products[0].product_id` | `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 } })` | Chord source (priority order) | Yahoo field | Notes | | ----------------------------------------------------------------------------------------------------------- | ------------ | ---------------------------------------------------------------------------------------- | | *(hardcoded)* `"custom"` | `et` | | | *(hardcoded)* `"Purchase"` | `ea` | | | Same as Product Viewed above | `product_id` | Omitted if not found | | `properties.total` > `properties.revenue` > `properties.value` | `gv` | Conversion value; omitted if not found | | `properties.cart_id` > `properties.cartId` > `properties.order_id` > `properties.orderId` > `properties.id` | `el` | Event label; omitted if not found. A cart ID wins over an order ID when both are present | ## Initialization Chord 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. Chord 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` | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.chord.co/activate/event-streaming/destinations/advertising/yahoo-dpa-pixel.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.