X Offline CAPI
X Offline CAPI, from source system to Ads Manager.
Datahash routes offline transactions from your POS, CRM, or warehouse to X with hashed identifiers and event dedupe.
- ● x.offline_capi :: live
- > batch offline_sales rows=8,940
- hash sha256(em,ph) pii=cleared
- 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 X's matching spec.
-
Deliver
Offline conversions routed to X, deduped and monitored.
WHAT FLOWS WHERE
One use case, every source.
A sale closes in your POS or CRM, Signals hashes the customer identifiers on a scheduled batch, matches them, then routes the conversion to X's Conversions API.
A sale closes in your POS or CRM, Signals hashes the customer identifiers on a scheduled batch, matches them, then routes the conversion to X's Conversions API.
What ships with this offering.
Offline outcomes inside X 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 /12/measurement/conversions/{pixel}
- event "Purchase" · conversion_id "pos-48112"
- identifiers hashed_email "a2c9…" · hashed_phone "6d41…"
- conversion_time 1789002233 · value 249 · AED
- ✓ accepted · 1 conversion
Adjacent moves on the same stack.
x
X CAPI
Datahash implements X (Twitter) Conversions API with dedupe against the X Pixel and hashed identifier support.
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
Reddit Offline CAPI
Datahash routes offline transactions from your POS, CRM, or warehouse to Reddit 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 X?
Any conversion your source systems record can be sent, most commonly in-store purchases and CRM-closed deals, mapped to X's event taxonomy during setup. Call center bookings, service completions, or franchise-reported sales work the same way, provided each record carries a timestamp and a hashed identifier that traces back to the ad that drove the click.
How do you match offline sales back to X ads?
Through hashed customer identifiers such as email and phone, matched against X's own identity graph after upload. Raw PII never leaves your environment unhashed; the hashing step runs inside your infrastructure before anything is transmitted. This mirrors the identifier handling used for X's online CAPI, so offline and online sales reconcile against the same customer record.
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.