Yahoo Pixel

introduction yahoo pixel (also known as yahoo dot tag) is yahoo’s conversion and audience tracking tool when connected as a chord cdp destination, chord automatically forwards key customer and conversion events to yahoo pixel, enabling performance marketers to optimize campaigns, measure roi, and power retargeting strategies across yahoo’s advertising network getting started before connecting yahoo pixel as a cdp destination yahoo ads account – ensure your team has an active yahoo dsp or yahoo native ads account pixel id – create and retrieve your yahoo pixel (dot tag) id from the yahoo ads ui navigate to campaign manager → library → dot tags connecting to the yahoo pixel cdp destination log into the chord data platform go to cdp → destinations click add destination and select yahoo pixel fill in the configuration form destination name (e g , “yahoo pixel – retargeting”) pixel id paste your yahoo dot tag id event type mapping (optional) choose which chord events to send and how they map to yahoo standard events (see table below) click create to activate the destination events event mapping chord event yahoo event action ( ea ) product viewed viewproduct product added addtocart checkout started begincheckout order completed purchase page page views are tracked automatically during pixel initialization subsequent page events do not fire additional calls to avoid double counting identify re pushes the pixel configuration with updated user data (hashed email and phone) for enhanced matching yahoo sdk call dotq push({ projectid, properties { pixelid, he, hph } }) track product viewed fires a custom conversion event with the viewproduct action yahoo sdk call dotq push({ projectid, properties { pixelid, he, hph, qstrings } }) yahoo attribute ( qstrings ) chord source (in priority order) notes et (hardcoded) "custom" ea (hardcoded) "viewproduct" event action product id properties product id > properties sku > properties id > properties productid > properties products\[0] product id omitted if not found product added fires a custom conversion event with the addtocart action yahoo sdk call dotq push({ projectid, properties { pixelid, he, hph, qstrings } }) yahoo attribute ( qstrings ) chord source (in priority order) notes et (hardcoded) "custom" ea (hardcoded) "addtocart" event action product id same as product viewed above omitted if not found checkout started fires a custom conversion event with the begincheckout action yahoo sdk call dotq push({ projectid, properties { pixelid, he, hph, qstrings } }) yahoo attribute ( qstrings ) chord source (in priority order) notes et (hardcoded) "custom" ea (hardcoded) "begincheckout" event action product id same as product viewed above omitted if not found order completed fires a purchase conversion event with order value and order id yahoo sdk call dotq push({ projectid, properties { pixelid, he, hph, qstrings } }) yahoo attribute ( qstrings ) chord source (in priority order) notes et (hardcoded) "custom" ea (hardcoded) "purchase" event action 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 cart id / properties cartid / properties order id / properties orderid / properties id event label (order id); omitted if not found all other track events are silently skipped 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 ywa i13n firebeacon 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 event mapping notes page context yahoo recommends sending page type (e g , product, cart, confirmation) as part of every event to improve classification revenue & currency for purchase events, chord includes value and currency fields so campaign roas can be accurately measured product metadata where available, chord includes sku, product id, and category to support dynamic retargeting user identity yahoo pixel does not require email or phone for event matching it relies on cookie based or device level identifiers post‑connection considerations deduplication if you already have the yahoo dot tag implemented in gtm or directly on your storefront, we recommend disabling it to avoid duplicate events consent management ensure consent logic is configured in your workspace if yahoo tracking needs to be gated by marketing opt in or region testing you can use yahoo’s dot tag helper chrome extension to confirm that events are firing correctly on your storefront verification & troubleshooting in chord, go to cdp → destination events and filter by yahoo pixel to confirm delivery in yahoo ads navigate to campaign manager → library → dot tags select your dot tag and check event activity to view real time events if events aren’t registering confirm that your pixel id is correct use yahoo’s pixel helperto debug ensure your site or app allows third party script tracking where needed 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