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

    CONNECTIONS / MariaDB / MariaDB to Google Store Sales

    MariaDB tables into Google Ads, built for Google Store Sales matching.

    Signals reads your MariaDB tables through a read-only database user scoped to the MariaDB tables you name, then matches in-person transactions to Google accounts as store-sales conversions so Google Ads sees offline conversions without an export.

    Talk to our team Explore the setup

    mariadb -> google-store-sales :: live

    1. ● mariadb → google.sales :: live
    2. > read closed_deals rows=58,128
    3. hash sha256(email,phone) consent=filtered
    4. route google deliver
    5. ✓ delivered · 48,828 matched

    WHAT THIS ENABLES

    MariaDB to Google Store Sales

    Google Store Sales for MariaDB: Signals matches in-person transactions to Google accounts as store-sales conversions straight from your MariaDB tables, hashed and consent-screened each time the read runs.

    • Signals matches in-person transactions to Google accounts as store-sales conversions, reading your MariaDB tables each time the read runs.
    • Store visits reconciled to campaign spend, 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 Store Sales Direct API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Omnichannel retailers reconciling point-of-sale against Google spend, working out of MariaDB tables and views.

    Engineering teams running MariaDB who need counter and showroom revenue inside the same ROAS view as online orders 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' Store Sales Direct API and tuned for the store-sales match rate.

    2. Map

      Columns from your MariaDB tables align to Google Ads' Store Sales Direct API in the visual mapper, hashed as the read runs and checked for the store-sales match rate.

    3. Deliver

      Each time the read runs, Signals reads your MariaDB tables and matches in-person transactions to Google accounts as store-sales conversions, reads only the records changed since the last run, with the store-sales match rate 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 Store Sales 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 Store Sales actually receives.

    signals :: mariadb.google-store-sales :: wire

    1. ● signals :: store sales upload
    2. > POST /offline_user_data_jobs source=mariadb.closed_deals
    3. transaction_time 2026-07-19T04:42:46 · transaction_amount_micros 19920000000
    4. currency_code GBP
    5. hashed_email sha256 "6d2e91…" · hashed_last_name sha256 "cc410a…"
    6. ✓ accepted match=84%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from MariaDB

    MariaDB to Google OCI

    Google Offline Conversions for MariaDB: Signals reconciles closed-won revenue to the Google…

    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 Store Sales

    ActiveCampaign to Google Store Sales: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Google Store Sales

    Datahash automates Store Sales Direct and Store Sales Customer Match uploads from your POS…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the MariaDB Google Store Sales 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, counter and showroom revenue inside the same ROAS view as online orders keeps pace and engineering teams running MariaDB watch the store-sales match rate. One scoped connection sets it up, cadence adjustable later.

    What match rate should a MariaDB-sourced Google Store Sales 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 Store Sales Direct API pinpoints the store-sales match rate, the number engineering teams running MariaDB tune against.

    NEXT STEP

    MariaDB to Google Store Sales, in production this week.

    Talk to our team All MariaDB use cases