Bing UET Tag: setup and help

Upload the module ZIP in Modules > Module Manager. Install it and open Configure for Bing UET Tag + Conversions API.

Obtain your numeric UET tag ID from your Microsoft Advertising account. The module does not create a tag or conversion goals in that account. Select the intended shop before saving settings.

Enter UET Tag ID, enable Enable Bing UET Tag, select your browser events and save. The ID must be a positive number. Browser tracking is disabled on a new installation until you configure it.

All of these fields are on the configuration screen.

The consent integration supports MPR consent modules and recognized consent-provider states. It does not display its own consent banner. With Respect marketing consent enabled, the absence of a supported consent decision is not permission to send.

The tracker also checks shop ownership and outbound tracking policy. Staff and opt-out signals can prevent delivery. Do not judge customer tracking from a browser that the module recognizes as internal.

These options are off on a new installation. Enable only the signals your shop supplies.

Engagement settings validate gallery, variant and detail thresholds from 1 to 20, dwell time from 5 to 600 seconds and option throttling from 250 to 60000 ms. Leave the JSON empty to use the defaults.

Browser UET and Conversions API have separate enablement. To use server purchases:

1. Keep Enable Bing UET Tag and Track purchase enabled.
2. Turn on Capture durable buyer evidence before you place your test order.
3. Enable Enable Conversions API and enter Conversions API token.
4. Save and review the readiness and queue panels.
5. Configure the module's generated cron entry in your hosting scheduler.
6. Accept cookies in a normal browser session, place an order as a customer or as a guest, then check that the purchase appears in the queue.

When an order is created, the module checks the buyer's checkout session and consent before it adds the purchase to the queue. A purchase without captured buyer data is held, so turning on CAPI does not send every order.

The endpoint pattern is:

https://capi.uet.microsoft.com/v1/{TAG_ID}/events

The installed task is send_bing_uet_conversions, scheduled every 300 seconds. Installation creates a cron entry through the shared cron package. Copy the actual token and command supplied by your installed module. A typical server command is:

* * * * * php /var/www/html/modules/mprbinguet/cron.php --token=YOUR_TOKEN --max-seconds=300

Replace the PHP path, shop path and token. The scheduler invokes the runner; due tasks use their own five-minute schedule.

The queue panel shows Pending, Sending, Sent, Failed, Held, Terminal and Suppressed. Use Retry failed events after you fix the reported error. Held and suppressed events wait for missing buyer data or were stopped by consent or policy; fix that cause rather than resending.

Send test event does not send anything at the moment: it only shows a message that Microsoft test mode is not available. To check tracking, place a test order, watch the queue and use the diagnostic tools in your Microsoft Advertising account.

This is an optional setup under Microsoft online refund and cancellation corrections.

Fill Microsoft customer ID, Microsoft account ID, Developer token, OAuth client ID, OAuth client secret, OAuth refresh token and Exact purchase conversion goal name. These fields start empty. Use Microsoft adjustments sandbox starts off.

The Enable online corrections switch appears only when Capture durable buyer evidence is on, all Microsoft credentials and the purchase goal name are filled in, and a stored link between your Microsoft account, UET tag and purchase goal exists for the shop. The settings screen has no field to create that link, so on a standard installation the switch stays hidden and refunds and cancellations are not sent to Microsoft.

Enable Track custom events and enter a JSON array in Custom event rules. Event names allow letters, numbers, underscores and hyphens, up to 64 characters. You can use up to 15 distinct names and up to 30 configured parameters per rule. The module sends only supported UET parameter names, including event_category, event_label, event_value, value, currency and ecommerce item fields.

A click rule:

[
  {"event":"GalleryBrowse","trigger":"click","selector":".product-images img, .images-container img","params":{"event_category":"Product","event_label":"Gallery browse"}}
]

A URL rule:

[
  {"event":"PromoPageView","trigger":"url","contains":["/promo/"],"params":{"event_category":"Campaign"}}
]

A controller rule:

[
  {"event":"CheckoutPageView","trigger":"controller","controllers":["order"],"params":{"event_category":"Checkout"}}
]

A DOM event rule:

[
  {"event":"QuoteRequest","trigger":"event","dom_event":"shop:quote-request","params":{"event_category":"Lead"}}
]

Your theme can dispatch the matching event:

document.dispatchEvent(new CustomEvent('shop:quote-request', {
  detail: {params: {event_label: 'Product page quote button'}}
}));

Use these configured rules for custom calls. The module does not provide the old window.mprbinguetTrack helper or read the old data-mprbinguet-param-* attributes. URL, controller and DOM rules default to firing once per page; click rules default to repeated firing. Set the rule's once value explicitly when needed.

Review the readiness panel after every configuration change. Check the tag ID, browser tracking, consent, custom rules and CAPI state.

Use a separate customer browser. Grant the required consent, open a product and inspect the browser network log for the Microsoft UET script at bat.bing.com/bat.js and the selected events. Refuse consent in a fresh test and confirm tracking is withheld while the consent guard is enabled.

Test a successful cart addition and wishlist addition. A failed action should not become a confirmed ecommerce event. If your theme or checkout uses custom events, confirm that it supplies the supported success signal.

For purchases, compare the transaction reference, purchase value policy, currency and items with the order. Check the server queue and logs as well as the browser requests. Microsoft decides which conversions it accepts and reports, so check the results in your Microsoft Advertising account too.

If no tag loads, check the main switch, a positive numeric ID, consent, employee exclusion, opt-out state and shop ownership policy. Then check script blockers and browser errors. If CAPI stays pending, check the cron runner. If it is held, check that the buyer gave consent and that their checkout data was captured. If it fails, check the token and the response before retrying.

Disable browser and server tracking if you only want to pause collection. Before uninstalling, save the settings and any delivery records you need. Uninstall removes the module menu, its scheduled task and configuration. The shared conversion queue table is dropped only when no other module uses the conversions package; queue data can remain when another user keeps the shared table.

Requires PrestaShop 1.6.0.0 or later and PHP 7.1 or later.