OpenAI Offline Conversions API
OpenAI Offline Conversions API, from CRM to campaign performance.
Datahash uploads offline and in-store conversions to OpenAI with hashed identifiers, so revenue that closes outside the browser still attributes to the campaign that drove it. Conversion values and currencies pass through for value-based bidding, with a delivery status on every row.
- ● openai.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 the same CRM or warehouse source.
From kickoff to verified events.
-
Connect
Connect the OpenAI ad account with scoped access, then point Datahash at the offline conversion source: CRM, warehouse, or files.
-
Map
Map rows to conversion events and identifiers in the visual mapper.
-
Deliver
Verify sample conversions in the live debugger, then go live with a delivery status on every row.
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 delivers the conversion to OpenAI with the original timestamp preserved.
A sale closes in your POS or CRM, Signals hashes the customer identifiers on a scheduled batch, matches them, then delivers the conversion to OpenAI with the original timestamp preserved.
What ships with this offering.
Offline purchases from CRM, warehouse, POS, and file sources delivered to OpenAI.
Conversion values and currencies passed through for value-based bidding.
A delivery status on every row, so rejected records are visible and fixable.
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 /events destination=openai source=offline
- event "purchase" · conversion_id "pos-48112"
- hashed_email "a2c9…" · hashed_phone "6d41…"
- value 249 · currency AED
- ✓ accepted · pending_match
Bring it from where the data lives.
Every source that supports this use case. Pick a platform to see the exact setup.
CRM
Databases
Files / storage
Data warehouses
Datahash API
Custom
Questions your team will ask.
How far back can offline conversions reach OpenAI?
Offline conversions can be uploaded within the attribution window OpenAI's advertising platform allows, generally matching its click lookback period. Datahash preserves the original conversion timestamp rather than the upload time, so late-arriving offline revenue still attributes to the ad click that drove it.
Does Datahash store customer PII to send offline conversions to OpenAI?
No. Identifiers are hashed with SHA-256 at ingestion and no PII is stored on host servers in Datahash Cloud. A self-hosted Core deployment is available if offline data cannot leave your own environment, and the same hashing approach applies whether the conversion arrives from a CRM, a warehouse, or a file upload.
What happens to offline conversion rows OpenAI rejects?
Every row gets a delivery status in the live debugger, so rejected or unmatched offline conversions stay visible instead of being silently dropped. Teams can correct the identifier or event mapping and resend the row without rebuilding the whole upload.
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.