Google Offline Conversion Import
Offline Conversion Import, done in the background.
Datahash automates GCLID-based OCI uploads to Google Ads so click-based offline conversions land in campaign optimization loops.
- ● google.oci :: live
- > conversion closed_deal value=54,000 AED
- match gclid "Cj0K…" reconciled
- upload → google_ads_api received
- ✓ imported · smart bidding fed
WHAT THIS ENABLES
Google Offline Conversion Import
Google Offline Conversion Import is the automated upload of GCLID-matched offline conversions to Google Ads, so sales that close in a CRM, call centre, or branch after the click feed Smart Bidding.
- Offline sales credited to the exact click that started them through the stored GCLID.
- The bid algorithm optimizing on closed revenue, not the form fill that preceded it.
- A scheduled, monitored import in place of the OCI spreadsheet someone maintains by hand.
Built for the teams that own the number.
Teams currently maintaining OCI spreadsheets by hand.
From kickoff to verified events.
-
Capture
GCLID captured on click and persisted through to CRM or POS.
-
Reconcile
Click IDs reconciled with the offline conversion event.
-
Upload
Delivery via the Google Ads API on a schedule.
WHAT FLOWS WHERE
One use case, every source.
A deal closes in your backend and is reconciled with the click that produced it, Signals attaches the stored GCLID and the conversion value, then uploads it to Google Ads as an offline conversion import.
A deal closes in your backend and is reconciled with the click that produced it, Signals attaches the stored GCLID and the conversion value, then uploads it to Google Ads as an offline conversion import.
What ships with this offering.
Offline outcomes feeding Smart Bidding automatically.
Scheduled, monitored uploads with retry handling.
An audit trail per conversion batch.
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 :: conversion payload
- > POST customers/{id}:uploadClickConversions
- conversion_action "closed_deal" · gclid "Cj0KCQjw…"
- conversion_date_time "2026-07-14 16:20:05+04:00"
- conversion_value 54000 · currency_code AED
- ✓ received · partial_failure=none
Adjacent moves on the same stack.
Google Store Sales
Datahash automates Store Sales Direct and Store Sales Customer Match uploads from your POS or warehouse into Google Ads.
Learn moreGoogle Enhanced Conversions for Leads
Datahash pushes hashed user data from your CRM back to Google Ads so lead-based campaigns optimize on qualified leads.
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
tiktok
TikTok Offline eAPI
Move your in-store and call-centre conversions to TikTok server-side, so TikTok can optimize campaigns on the outcomes that matter.
Learn moreBring 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.
What if the GCLID is lost between click and conversion?
Those conversions cannot be imported via OCI, which matches on click ID alone. We fix loss at the source by persisting GCLID into your CRM at capture, and for the remainder we typically pair OCI with Enhanced Conversions for Leads, which matches on hashed user data instead.
How quickly do conversions appear in Google Ads?
Uploads run on your chosen schedule, from hourly to daily, matched against the conversion window Google allows for OCI. Google processes imports within a few hours of receipt, so a conversion closed today is usually visible in reporting by tomorrow, in time to influence the next day's Smart Bidding decisions rather than lagging a full cycle behind.
How is consent handled for imported conversions?
Consent status is carried per record in line with Google's EU user consent policy, tagged alongside the GCLID and conversion value at the point Signals builds the batch. Records lacking the required consent signal are filtered out automatically before upload, so nothing ships to Google Ads without the correct consent state attached.
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.