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

    CONNECTIONS / MariaDB / MariaDB to Meta Offline CAPI

    MariaDB tables into Meta, built for Meta's offline optimization.

    Signals reads your MariaDB tables through a read-only database user scoped to the MariaDB tables you name, then credits dealer, branch, and phone sales to the Meta campaigns behind them so Meta sees offline conversions without an export.

    Talk to our team Explore the setup

    mariadb -> meta-offline-capi :: live

    1. ● mariadb → meta.capi :: live
    2. > read closed_deals rows=32,287
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 25,507 matched

    WHAT THIS ENABLES

    MariaDB to Meta Offline CAPI

    Meta Offline CAPI for MariaDB: Signals credits dealer, branch, and phone sales to the Meta campaigns behind them straight from your MariaDB tables, hashed and consent-screened each time the read runs.

    • Signals credits dealer, branch, and phone sales to the Meta campaigns behind them, reading your MariaDB tables each time the read runs.
    • Campaign learning fed by real-world purchases, with no export step out of your MariaDB tables.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Meta credits the campaign that sourced the conversion conversion happens off-platform Ad click on Meta Scheduled read sync recorded in MariaDB S Signals hash · dedupe Offline Conversions API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Considered-purchase brands closing revenue far from the browser, working out of MariaDB tables and views.

    Engineering teams running MariaDB who need in-store and phone revenue joining Meta's optimization loop 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 Meta's Offline Conversions API and tuned for Meta's 62-day event window.

    2. Map

      Columns from your MariaDB tables align to Meta's Offline Conversions API in the visual mapper, hashed as the read runs and checked for Meta's 62-day event window.

    3. Deliver

      Each time the read runs, Signals reads your MariaDB tables and credits dealer, branch, and phone sales to the Meta campaigns behind them, reads only the records changed since the last run, with Meta's 62-day event window 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 Offline CAPI 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 Offline CAPI actually receives.

    signals :: mariadb.meta-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversions source=mariadb.closed_deals
    3. event_name "Purchase" · event_time 2026-07-16T10:48:41
    4. value 31853.00 · currency USD
    5. em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-48921"
    6. ✓ accepted match=79%
    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 Google Store Sales

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

    Learn more

    same use case

    ActiveCampaign to Meta Offline CAPI

    ActiveCampaign to Meta Offline CAPI: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Meta Offline CAPI

    Datahash ingests offline transactions from your POS, CRM, or warehouse and routes them to…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the MariaDB Meta Offline CAPI sync run?

    You set the cadence, from near-real-time to a nightly MariaDB sync of your MariaDB tables into Meta. Since Signals reads only the records changed since the last run, in-store and phone revenue joining Meta's optimization loop keeps pace and engineering teams running MariaDB watch Meta's 62-day event window. One scoped connection sets it up, cadence adjustable later.

    What match rate should a MariaDB-sourced Meta Offline CAPI 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 Meta; one missing both cannot. First-run feedback from Offline Conversions API pinpoints Meta's 62-day event window, the number engineering teams running MariaDB tune against.

    NEXT STEP

    MariaDB to Meta Offline CAPI, in production this week.

    Talk to our team All MariaDB use cases