Microsoft UET bat.bing.com request
The Microsoft Advertising UET hit that reports page visits and custom events to Microsoft Advertising.
The request at a glance
- Request
GEThttps://bat.bing.com/action/0- Sent by
- Microsoft Advertising UET
- Typically triggered by
- A page load, and window.uetq.push('event', ...) calls
What this request is
Microsoft describes the request to bat.bing.com/action/0 as the most important UET request: it tells Microsoft Advertising about a page visit. Custom events and variable revenue send a similar request with different parameters.
The UET tag ID is in the ti parameter of every request.
What typically triggers it
- A page load when the UET tag initializes, and page views in single-page apps when automatic SPA tracking is on.
- Custom events pushed with window.uetq.push('event', ...), including variable revenue for conversions.
Important parameters
| Parameter | What it means | Source |
|---|---|---|
ti | The UET tag ID. | Vendor-documented |
evt | Hit type, for example pageLoad or custom. | Commonly observed, not documented by the vendor |
ea, ec, el, ev | Event action, category, label and value for custom events. | Commonly observed, not documented by the vendor |
gv, gc | Revenue value and currency for variable-revenue conversions. | Commonly observed, not documented by the vendor |
Microsoft documents the event fields as they are pushed in JavaScript (event action, category, label, value, revenue_value, currency) but not their short names in the request.
How to find it on a site
- Open the site in Chrome, open DevTools (F12, or Cmd+Option+I on a Mac) and go to the Network tab.
- Reload the page and type
bat.bing.com/actioninto the filter box. - Click a matching request and open Payload to read its parameters.
- Compare ti with the tag ID in your Microsoft Advertising account to confirm the right tag is firing.
Sources
The endpoint, the sender and the parameters marked vendor-documented were checked against the sources above on . Parameters marked commonly observed reflect how the request is widely read by practitioners; the vendor does not document them and can change them without notice. Browse all network requests.
Know when a tag stops firing
TagPipes Auditor checks with real browsers that your marketing pixels fire with the right parameters, and alerts you when tracking breaks. Pulse checks how marketing tags behave against your consent banner.
TagPipes monitors, configures and reports. It does not determine legal compliance and does not provide legal advice. Output is informational and reflects observed state at the time of observation. Rawsoft's expertise is technology, not law; please confirm any regulatory interpretation with your own counsel.