Bing Offline CAPI
Offline conversions delivered to Microsoft Advertising.
Datahash routes offline transactions from your POS, CRM, or warehouse to Microsoft Advertising with hashed identifiers and event dedupe.
- ● microsoft.offline_capi :: live
- > batch offline_sales rows=8,940
- hash sha256(em) msclkid=matched
- match hashed identifiers 47%
- ✓ uploaded · offline conversions accepted
Built for the teams that own the number.
Teams already sending offline conversions to other ad platforms.
From kickoff to verified events.
-
Source
Ingest offline events from POS, CRM, warehouse, or file drop.
-
Match
Hashed email and phone prepared per Microsoft Advertising's matching spec.
-
Deliver
Offline conversions routed to Microsoft Advertising, deduped and monitored.
WHAT FLOWS WHERE
One use case, every source.
A sale closes in your POS or CRM, Signals hashes the identifiers on a scheduled batch and matches on the click ID, then routes the offline conversion to Microsoft Advertising.
A sale closes in your POS or CRM, Signals hashes the identifiers on a scheduled batch and matches on the click ID, then routes the offline conversion to Microsoft Advertising.
What ships with this offering.
Offline outcomes inside Microsoft Advertising campaign optimization.
Hashed, privacy-safe identifier handling end to end.
The same offline pipeline you already run for 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 :: offline payload
- > POST /conversions/offline source=offline
- event "purchase" · msclkid "ms.1…" · transaction_id "pos-48112"
- hashed_email "a2c9…" · hashed_phone "6d41…"
- value 249 · currency AED
- ✓ accepted · 1 conversion
Adjacent moves on the same stack.
microsoft
Bing Web CAPI
Datahash sends web conversions to Microsoft Advertising server-side, with dedupe against the UET tag and hashed identifiers.
Learn more
meta
Meta Offline CAPI
Datahash ingests offline transactions from your POS, CRM, or warehouse and routes them to Meta with hashed identifiers, event dedupe, and closed-loop match reporting.
Learn more
x
X Offline CAPI
Datahash routes offline transactions from your POS, CRM, or warehouse to X with hashed identifiers and event dedupe.
Learn more
LinkedIn Offline CAPI
Datahash routes offline outcomes, like closed deals from your CRM, to LinkedIn with hashed identifiers and event dedupe.
Learn moreQuestions your team will ask.
What offline events can be sent to Microsoft Advertising?
Any conversion your source systems record can be sent, most commonly in-store purchases from POS and CRM-closed deals from your sales team. During setup, Datahash maps each event type to Microsoft Advertising's conversion taxonomy, so purchases, leads, and other offline outcomes appear in campaign reporting the same way your online conversions do.
How do you match offline sales back to Microsoft Advertising?
Matching runs through hashed customer identifiers, primarily email and phone, prepared according to Microsoft Advertising's matching specification before delivery. Datahash hashes these values inside your own environment, so raw PII never leaves unhashed and Microsoft only ever receives identifiers it can match against its signed-in user records to connect the offline sale.
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.