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

    CONNECTIONS / MySQL / MySQL to Meta Offline CAPI

    From MySQL tables to Meta's offline optimization.

    Signals reads your MySQL tables through a read-only database user scoped to the MySQL 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

    mysql -> meta-offline-capi :: live

    1. ● mysql → meta.capi :: live
    2. > read closed_deals rows=61,335
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 49,681 matched

    WHAT THIS ENABLES

    MySQL to Meta Offline CAPI

    MySQL to Meta Offline CAPI: Signals reads your MySQL tables and credits dealer, branch, and phone sales to the Meta campaigns behind them, hashed and consent-checked each time the read runs.

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

    The click, the conversion, and the credit.

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

    Meta credits the campaign that sourced the conversion conversion happens off-platform Ad click on Meta Scheduled read sync recorded in MySQL 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 MySQL tables and views.

    Application teams on MySQL who need in-store and phone revenue joining Meta's optimization loop out of MySQL tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the MySQL tables you name, mapped to Meta's Offline Conversions API and tuned for Meta's 62-day event window.

    2. Map

      Columns from your MySQL 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 MySQL 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 MySQL records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

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

    1. ● signals :: event payload
    2. > POST /offline_conversions source=mysql.closed_deals
    3. event_name "Purchase" · event_time 2026-07-14T07:21:55
    4. value 31902.00 · currency SAR
    5. em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-96715"
    6. ✓ accepted match=81%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from MySQL

    MySQL to Google OCI

    MySQL to Google Offline Conversions: Signals reads your MySQL tables and reconciles…

    Learn more

    from MySQL

    MySQL to Google Store Sales

    MySQL to Google Store Sales: Signals reads your MySQL tables and matches in-person…

    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 MySQL Meta Offline CAPI sync run?

    Delivery tracks MySQL, run by application teams on MySQL: a near-real-time or scheduled sync of your MySQL tables feeds Meta on that cadence. Each run reads only the records changed since the last run, so campaign learning fed by real-world purchases holds up on Meta's 62-day event window. The live debugger confirms every delivery inline.

    What match rate should a MySQL-sourced Meta Offline CAPI batch expect?

    Coverage of hashed identifiers across your MySQL tables decides it, and application teams on MySQL own that inside MySQL. A live email or phone matches into Meta; neither, and it will not. First-run feedback flags Meta's 62-day event window, which application teams on MySQL then raise inside your MySQL tables.

    NEXT STEP

    MySQL to Meta Offline CAPI, in production this week.

    Talk to our team All MySQL use cases