Jump to a popular page, or start typing.
    Talk to our team

    CONNECTIONS / Zithara / Zithara to Google OCI

    From Zithara customer records to Google Ads offline conversion import.

    Connect Zithara and point Signals at your Zithara customer records; it reconciles closed-won revenue to the Google Ads click through GCLID as records change, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    zithara -> google-oci :: live

    1. ● zithara → google.oci :: live
    2. > read closed_deals rows=45,483
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 35,477 matched

    WHAT THIS ENABLES

    Zithara to Google Offline Conversions

    Zithara to Google Offline Conversions: your Zithara customer records, hashed and consent-checked, feed Google Ads as Signals reconciles closed-won revenue to the Google Ads click through GCLID as records change.

    • Offline and in-store sales from your Zithara customer records activated for Google Ads, as Signals reconciles closed-won revenue to the Google Ads click through GCLID.
    • Smart Bidding trained on booked revenue instead of a mid-funnel proxy, drawn from your Zithara customer records by retail CRM teams running Zithara.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

    The conversion happens off Google, away from any pixel. Here is how Zithara closes the loop.

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google CRM record sync recorded in Zithara S Signals hash · dedupe Offline Conversion Impo… delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Advertisers whose Google-sourced deals close days after the click, with the records already in Zithara customer and loyalty records.

    Retail CRM teams running Zithara activating Google Ads offline conversion import straight from Zithara customer records.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Zithara, reading only your Zithara customer records to feed Google Ads' Offline Conversion Import (Google Ads API), sized for GCLID coverage.

    2. Map

      Signals reads your Zithara customer records, and its columns map to Google Ads' Offline Conversion Import (Google Ads API) in the visual mapper, hashed and checked for GCLID coverage.

    3. Deliver

      On each run, Signals pulls your Zithara customer records, reconciles closed-won revenue to the Google Ads click through GCLID, and sends only the records that changed, with GCLID coverage in the debugger.

    WHAT YOU GET

    What changes when the CSV goes away.

    Capability Manual CSV upload Datahash
    Reporting Offline sales sit in a separate export, reconciled by hand. Revenue counted in the same OCI reporting as web conversions.
    Deduplication A re-uploaded file risks counting the same conversion twice. Deduped delivery, so a resent record never counts as a second conversion.
    Match visibility Match quality is a guess until the numbers look off. Match rate reported per upload, tied to the source event set that produced it.
    Effort and latency An analyst exports and uploads on a manual cadence. Server-side and automatic the moment Zithara records the event.
    ON THE WIRE

    What OCI actually receives.

    signals :: zithara.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=zithara.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-21T10:16:52"
    5. conversion_value 13326 · currency_code AED
    6. ✓ accepted · batch=nightly
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Zithara

    Zithara to Google Store Sales

    Zithara to Google Store Sales: your Zithara customer records, hashed and consent-checked,…

    Learn more

    from Zithara

    Zithara to Meta Offline CAPI

    Zithara to Meta Offline CAPI: your Zithara customer records, hashed and consent-checked,…

    Learn more

    same use case

    ActiveCampaign to Google OCI

    ActiveCampaign to Google Offline Conversions: Signals reads your ActiveCampaign contacts…

    Learn more

    generic

    Google Offline Conversion Import

    Datahash automates GCLID-based OCI uploads to Google Ads so click-based offline conversions…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Zithara Google OCI sync run?

    You set the cadence, from near-real-time to a nightly Zithara sync of your Zithara customer records into Google Ads. Since Signals sends only the records that changed, Smart Bidding trained on booked revenue instead of a mid-funnel proxy keeps pace and retail CRM teams running Zithara watch GCLID coverage. One scoped connection sets it up, cadence adjustable later.

    What match rate should a Zithara-sourced Google OCI batch expect?

    In Zithara, match rate tracks the email and phone quality your Zithara customer records carry. Clean identifiers land for Google Ads; blank ones never will. The first Offline Conversion Import (Google Ads API) report shows retail CRM teams running Zithara where GCLID coverage needs work, a data-quality task handled in Zithara.

    NEXT STEP

    Zithara to Google OCI, in production this week.

    Talk to our team All Zithara use cases