Yahoo Pixel

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 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 log into the chord data platform navigate to the cdp click the "add" button next to destinations select yahoo pixel from the destination catalog enter the destination name, pixel id , and project id 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