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

    CONNECTIONS / Salesforce / Salesforce to Google OCI

    Salesforce closed-won, uploaded to Google as a click conversion.

    A GCLID captured at the lead form is only useful if it survives the sales cycle. Signals writes it to the Salesforce record at creation and uploads the matching offline conversion the moment the opportunity closes.

    Talk to our team Explore the setup

    salesforce -> google-oci :: live

    1. ● salesforce → google.oci :: live
    2. > event Lead created gclid=Cj0KCQjw…
    3. > event Opportunity closed-won value=22,900 USD
    4. hash sha256(email,phone) gclid=carried
    5. route google.oci upload batch=nightly
    6. ✓ delivered · click conversion recorded

    WHAT THIS ENABLES

    Salesforce to Google Offline Conversion Import

    Salesforce to Google Offline Conversion Import is the pipeline that persists the GCLID captured on a Salesforce lead through to the opportunity that closes it, then uploads the click-based conversion to Google Ads so Smart Bidding sees revenue that closed away from the browser.

    • Closed-won Salesforce revenue attributed back to the exact click that started the deal.
    • Smart Bidding trained on real offline outcomes instead of lead form submissions alone.
    • A scheduled upload that replaces a manually maintained OCI spreadsheet.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

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

    Built for the teams that own the number.

    Google Ads advertisers whose leads qualify and close inside Salesforce, not on a landing page.

    Teams still exporting closed-won reports to format an OCI upload file by hand.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Connected App access to the Salesforce Lead and Opportunity objects, scoped to the fields the upload needs.

    2. Map

      GCLID field and the Opportunity stage that counts as the conversion event agreed in the visual mapper.

    3. Deliver

      Scheduled upload through the Google Ads API, with an accepted count per batch.

    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 Salesforce records the event.
    ON THE WIRE

    What OCI actually receives.

    signals :: salesforce.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=salesforce.opportunity
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-15 09:41:00+04:00"
    5. conversion_value 22900 · currency_code USD
    6. ✓ accepted · batch=nightly
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Salesforce

    Salesforce to Google Store Sales

    Salesforce to Google Store Sales is the pipeline that hashes contact and closed-won…

    Learn more

    from Salesforce

    Salesforce to Meta Offline CAPI

    Salesforce to Meta Offline Conversions API is the pipeline that routes closed-won…

    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.

    What happens to a Salesforce lead that never captured a GCLID?

    It cannot be imported through OCI, which matches on the click ID alone and has nothing else to go on. We fix the loss at the source by writing GCLID to the Salesforce lead the moment it is created, and for records that still arrive without one, we typically pair OCI with Enhanced Conversions for Leads, which matches on hashed data instead.

    How long after an Opportunity closes does the conversion show up in Google Ads?

    Uploads run on whatever schedule you set, from hourly to nightly, and Google generally processes an OCI batch within a few hours of receiving it. An Opportunity marked closed-won today is usually visible in Google Ads reporting by the next business day, which is fast enough for Smart Bidding to act on it within the week.

    NEXT STEP

    Salesforce to Google OCI, in production this week.

    Talk to our team All Salesforce use cases