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

    CONNECTIONS / Microsoft SQL Server / SQL Server to Google OCI

    Your SQL Server tables, wired to Google Ads offline conversion import.

    Connect SQL Server and point Signals at your SQL Server tables; it reconciles closed-won revenue to the Google Ads click through GCLID each time the read runs, hashed and consent-checked for Google Ads.

    Talk to our team Explore the setup

    microsoft-sql-server -> google-oci :: live

    1. ● sql server → google.oci :: live
    2. > read closed_deals rows=50,878
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 41,720 matched

    WHAT THIS ENABLES

    SQL Server to Google Offline Conversions

    SQL Server to Google Offline Conversions: Signals reads your SQL Server tables and reconciles closed-won revenue to the Google Ads click through GCLID, hashed and consent-checked each time the read runs.

    • Offline and in-store sales from your SQL Server tables 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 SQL Server tables by data teams running SQL Server.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google Scheduled read sync recorded in Microsoft SQL… 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 SQL Server tables, views, and indexed views.

    Data teams running SQL Server activating Google Ads offline conversion import straight from SQL Server tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the SQL Server tables you name to feed Google Ads' Offline Conversion Import (Google Ads API), sized for GCLID coverage.

    2. Map

      A scheduled read pulls your SQL Server tables, 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 SQL Server tables, reconciles closed-won revenue to the Google Ads click through GCLID, and reads only the records changed since the last run, 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 Microsoft SQL Server records the event.
    ON THE WIRE

    What OCI actually receives.

    signals :: microsoft-sql-server.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=microsoft-sql-server.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-19T14:41:20"
    5. conversion_value 39310 · currency_code AED
    6. ✓ accepted · batch=hourly
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Microsoft SQL Server

    SQL Server to Google Store Sales

    SQL Server to Google Store Sales: Signals reads your SQL Server tables and matches…

    Learn more

    from Microsoft SQL Server

    SQL Server to Meta Offline CAPI

    SQL Server to Meta Offline CAPI: Signals reads your SQL Server tables and credits dealer,…

    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 SQL Server Google OCI sync run?

    Delivery tracks SQL Server, run by data teams running SQL Server: a near-real-time or scheduled sync of your SQL Server tables feeds Google Ads on that cadence. Each run reads only the records changed since the last run, so a clean line from click to closed revenue holds up on GCLID coverage. The live debugger confirms every delivery inline.

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

    Match rate follows identifier coverage in your SQL Server tables, which data teams running SQL Server control, not SQL Server itself. A record with a current hashed email or phone matches for Google Ads; one missing both cannot. First-run feedback from Offline Conversion Import (Google Ads API) pinpoints GCLID coverage, the number data teams running SQL Server tune against.

    NEXT STEP

    SQL Server to Google OCI, in production this week.

    Talk to our team All Microsoft SQL Server use cases