Bing Ads (UET Tag)

bing ads (uet tag) introduction bing ads , now called microsoft advertising , is a pay per click (ppc) advertising platform that allows businesses to display ads across microsoft's search network, including bing, yahoo, and aol it helps brands reach users through search results, partner websites, and native placements, offering targeting options based on keywords, location, demographics, and device type chord's cdp provides support for the bing ads uet (universal event tracking) tag the bing ads uet tag is a piece of code provided by microsoft advertising that you place on your website to track what visitors do after clicking on your ad specifically, it collects data on actions like purchases, form submissions, or page views, helping you measure ad performance, build remarketing lists, and enable automated bidding strategies in short, it connects your site behavior with your microsoft ads campaigns so you can optimize for better results getting started this is a device mode destination you will need the microsoft ads / bing universal event tracking tag id in order to connect this destination the relevant id can be found in your microsoft ads dashboard connecting to the bing ads (uet tag) cdp destination 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 bing ads (uet tag) from the destination catalog enter in the destination name and the universal event tracking tag id click "create" to connect enhanced conversions on every event (page and track), the plugin checks for email and phone to set enhanced conversions data via microsoft's uet sdk this enables microsoft to match conversions to signed in users for improved attribution uet sdk call uetq push("set", { pid }) uet enhanced conversion field chord source (in priority order) pid em properties email > context traits email pid ph properties phone > context traits phone enhanced conversion data is sent before both page and track events whenever email or phone is available events page fires a bing uet page load event uet sdk call uetq push("pageload") no additional attributes are sent with page events track all track events are forwarded as custom bing uet events using the modern event format there is no event name specific mapping — every track event uses the same format uet sdk call uetq push("event", eventaction, eventdata) uet attribute chord source (in priority order) notes (event action) event (the chord event name) second argument to uetq push("event", ) event category properties category omitted if not present revenue value properties revenue > properties total > properties value > calculated from products conversion revenue currency properties currency > properties meta i18n currency > "usd" (default) omitted if not present transaction id properties order id / properties orderid / properties id for deduplication; omitted if not present shipping properties shipping shipping cost; omitted if not present tax properties tax tax amount; omitted if not present identify events are not forwarded to bing ads initialization the plugin uses bing's standard inline initialization pattern it sets up the uetq queue array, creates a script element for //bat bing com/bat js , and on script load initializes the uet object with { ti tagid, enableautospatracking true } followed by an initial pageload call 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 //bat bing com connect src https //bat bing com