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

    CONNECTIONS / MariaDB / MariaDB to Google OCI

    MariaDB tables into Google Ads, built for Google Ads offline conversion import.

    Signals reads your MariaDB tables through a read-only database user scoped to the MariaDB tables you name, then reconciles closed-won revenue to the Google Ads click through GCLID so Google Ads sees offline conversions without an export.

    Talk to our team Explore the setup

    mariadb -> google-oci :: live

    1. ● mariadb → google.oci :: live
    2. > read closed_deals rows=39,613
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 33,671 matched

    WHAT THIS ENABLES

    MariaDB to Google Offline Conversions

    Google Offline Conversions for MariaDB: Signals reconciles closed-won revenue to the Google Ads click through GCLID straight from your MariaDB tables, hashed and consent-screened each time the read runs.

    • Signals reconciles closed-won revenue to the Google Ads click through GCLID, reading your MariaDB tables each time the read runs.
    • A clean line from click to closed revenue, with no export step out of your MariaDB tables.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Google credits the campaign that sourced the conversion conversion happens off-platform Ad click on Google Scheduled read sync recorded in MariaDB 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, working out of MariaDB tables and views.

    Engineering teams running MariaDB who need Smart Bidding trained on booked revenue instead of a mid-funnel proxy out of MariaDB tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the MariaDB tables you name, mapped to Google Ads' Offline Conversion Import (Google Ads API) and tuned for GCLID coverage.

    2. Map

      Columns from your MariaDB tables align to Google Ads' Offline Conversion Import (Google Ads API) in the visual mapper, hashed as the read runs and checked for GCLID coverage.

    3. Deliver

      Each time the read runs, Signals reads your MariaDB tables and reconciles closed-won revenue to the Google Ads click through GCLID, reads only the records changed since the last run, with GCLID coverage watched 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 MariaDB records the event.
    ON THE WIRE

    What OCI actually receives.

    signals :: mariadb.google-oci :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversion_import source=mariadb.closed_deals
    3. gclid "Cj0KCQjw…" · conversion_action "closed_won"
    4. conversion_date_time "2026-07-20T14:42:47"
    5. conversion_value 19820 · currency_code SAR
    6. ✓ accepted · batch=hourly
    RELATED USE CASES

    Adjacent moves on the same stack.

    from MariaDB

    MariaDB to Google Store Sales

    Google Store Sales for MariaDB: Signals matches in-person transactions to Google accounts…

    Learn more

    from MariaDB

    MariaDB to Meta Offline CAPI

    Meta Offline CAPI for MariaDB: Signals credits dealer, branch, and phone sales to the Meta…

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

    You set the cadence, from near-real-time to a nightly MariaDB sync of your MariaDB tables into Google Ads. Since Signals reads only the records changed since the last run, Smart Bidding trained on booked revenue instead of a mid-funnel proxy keeps pace and engineering teams running MariaDB watch GCLID coverage. One scoped connection sets it up, cadence adjustable later.

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

    Match rate follows identifier coverage in your MariaDB tables, which engineering teams running MariaDB control, not MariaDB 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 engineering teams running MariaDB tune against.

    NEXT STEP

    MariaDB to Google OCI, in production this week.

    Talk to our team All MariaDB use cases