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

    CONNECTIONS / PostgreSQL / PostgreSQL to Meta Offline CAPI

    Your PostgreSQL tables, wired to Meta's offline optimization.

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

    postgresql -> meta-offline-capi :: live

    1. ● postgresql → meta.capi :: live
    2. > read closed_deals rows=52,294
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 41,312 matched

    WHAT THIS ENABLES

    PostgreSQL to Meta Offline CAPI

    Meta Offline CAPI for PostgreSQL: Signals credits dealer, branch, and phone sales to the Meta campaigns behind them straight from your PostgreSQL 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 PostgreSQL tables each time the read runs.
    • Campaign learning fed by real-world purchases, with no export step out of your PostgreSQL tables.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

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

    Engineering teams running PostgreSQL who need in-store and phone revenue joining Meta's optimization loop out of PostgreSQL tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

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

    What Offline CAPI actually receives.

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

    1. ● signals :: event payload
    2. > POST /offline_conversions source=postgresql.closed_deals
    3. event_name "Purchase" · event_time 2026-07-17T04:51:05
    4. value 12183.00 · currency USD
    5. em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-61865"
    6. ✓ accepted match=79%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from PostgreSQL

    PostgreSQL to Google OCI

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

    Learn more

    from PostgreSQL

    PostgreSQL to Google Store Sales

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

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

    Delivery tracks PostgreSQL, run by engineering teams running PostgreSQL: a near-real-time or scheduled sync of your PostgreSQL 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 PostgreSQL-sourced Meta Offline CAPI batch expect?

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

    NEXT STEP

    PostgreSQL to Meta Offline CAPI, in production this week.

    Talk to our team All PostgreSQL use cases