Skip to content
DestinationActivation

Microsoft Ads (UET CAPI)

The server-side path for Bing/Microsoft Ads. One detail decides match quality: Microsoft normalizes emails its own way (removing dots and +alias suffixes) before hashing — the platform applies exactly that rule, otherwise hashes would never match.

Data delivered

Data delivered

  • Free-form event names via the UET tag
  • Email (Microsoft's own normalization) and phone hashed; external id, IP and user agent in plain text
  • Value, currency and properties

What it is for

What you can do with it

  • Close the conversion loop for Bing campaigns
  • Reuse the same sale Delivery that feeds your other destinations

Why integrate

The business reason, not just the tech

Bing converts — and almost nobody measures it

Desktop audiences, decision-makers, less auction competition. UET CAPI closes the conversion loop on a channel most competitors never even instrument.

Microsoft's hash is different

Microsoft normalizes emails its own way (dots and +alias removed) before hashing. "Standard" hashes never match — and match rates go to zero with no error. We apply exactly their rule.

Same event, one more channel

The sale Delivery that feeds Meta and TikTok gains another destination with two credentials: tag id and token.

How to connect

Step by step

  1. Step 1

    Copy the UET tag id from your Microsoft Ads account.

  2. Step 2

    Create the destination with the tag id and access token.

  3. Step 3

    Create a Delivery with the conversion event.

Frequently asked questions

Is it the same email hash as other destinations?

No — Microsoft strips dots and the +alias suffix before hashing. The platform knows that and applies the right normalization per destination.

Start measuring what actually becomes revenue

Create a free account, connect your first source and see your first lead timeline today. No card required.