Jump to a popular page, or start typing.

    Bing Web CAPI

    Server-side conversion tracking for Microsoft Advertising.

    Datahash sends web conversions to Microsoft Advertising server-side, with dedupe against the UET tag and hashed identifiers.

    microsoft.bing-web-capi :: live

    1. ● microsoft.web_capi :: live
    2. > event purchase value=214.00 AED
    3. hash sha256(em) msclkid=captured
    4. dedupe event_id vs uet matched
    5. ✓ delivered · conversion accepted
    WHO THIS IS FOR

    Built for the teams that own the number.

    Advertisers running Microsoft Advertising alongside Google and Meta.

    Teams that want the same server-side coverage on Bing as everywhere else.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Audit

      UET tag coverage and event map baseline.

    2. Configure

      Server-side conversion delivery to Microsoft Advertising, deduped against the UET tag.

    3. Verify

      Events confirmed in Microsoft Advertising before go-live.

    WHAT FLOWS WHERE

    One use case, every source.

    A purchase fires on your website, Signals hashes the identifiers and deduplicates against the UET tag on the shared event ID, then posts the event to Microsoft Advertising server-side.

    A purchase fires on your website, Signals hashes the identifiers and deduplicates against the UET tag on the shared event ID, then posts the event to Microsoft Advertising server-side.

    WHAT YOU GET

    What ships with this offering.

    Deduped UET tag plus server-side conversions.

    Hashed identifier support for better matching.

    The same integration discipline you already have on other channels.

    ON THE WIRE

    What the platform actually receives.

    Identifiers are hashed with SHA-256 at source. The payload the destination sees never contains raw PII.

    signals :: bing-web-capi :: wire

    1. ● signals :: event payload
    2. > POST /conversions/track source=web
    3. event "purchase" · transaction_id "e2f9c1…"
    4. hashed_email "9b1a4d…" · msclkid "ms.1…"
    5. value 214 · currency AED
    6. ✓ accepted · 1 conversion
    FAQ

    Questions your team will ask.

    Do we keep the UET tag?

    Yes. The UET tag stays live and runs alongside the server-side connection, rather than being replaced by it. Both feed Microsoft Advertising, and Datahash dedupes them on a shared event identifier so each conversion counts once, giving you the browser signal you already have plus the server-side coverage that survives tracking loss.

    What identifiers does Microsoft Advertising match on?

    Microsoft Advertising matches primarily on hashed email plus the click identifier carried from the ad itself. Datahash hashes every identifier before it leaves your environment, then sends the strongest key set your site is able to capture on each event, which improves match rates without ever exposing raw customer data to Microsoft.

    NEXT STEP

    Live in fifteen minutes. Measurable in a week.

    Talk to our team of solutions engineers. We map your source data, propose an integration plan, and give you a live setup in the same call where possible.