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

    CONNECTIONS / Cockroach / Cockroach to Meta Offline CAPI

    From Cockroach tables to Meta's offline optimization.

    Connect Cockroach and point Signals at your Cockroach tables; it credits dealer, branch, and phone sales to the Meta campaigns behind them each time the read runs, hashed and consent-checked for Meta.

    Talk to our team Explore the setup

    cockroach -> meta-offline-capi :: live

    1. ● cockroach → meta.capi :: live
    2. > read closed_deals rows=10,851
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 8,464 matched

    WHAT THIS ENABLES

    Cockroach to Meta Offline CAPI

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

    • Offline and in-store sales from your Cockroach tables activated for Meta, as Signals credits dealer, branch, and phone sales to the Meta campaigns behind them.
    • In-store and phone revenue joining Meta's optimization loop, drawn from your Cockroach tables by platform teams running CockroachDB.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Meta credits the campaign that sourced the conversion conversion happens off-platform Ad click on Meta Scheduled read sync recorded in Cockroach 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, with the records already in Cockroach tables and secondary indexes.

    Platform teams running CockroachDB activating Meta's offline optimization straight from Cockroach tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the Cockroach tables you name to feed Meta's Offline Conversions API, sized for Meta's 62-day event window.

    2. Map

      A scheduled read pulls your Cockroach tables, and its columns map to Meta's Offline Conversions API in the visual mapper, hashed and checked for Meta's 62-day event window.

    3. Deliver

      On each run, Signals pulls your Cockroach tables, credits dealer, branch, and phone sales to the Meta campaigns behind them, and reads only the records changed since the last run, with Meta's 62-day event window 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 Cockroach records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

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

    1. ● signals :: event payload
    2. > POST /offline_conversions source=cockroach.closed_deals
    3. event_name "Purchase" · event_time 2026-07-15T19:10:40
    4. value 28918.00 · currency AED
    5. em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-65640"
    6. ✓ accepted match=78%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Cockroach

    Cockroach to Google OCI

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

    Learn more

    from Cockroach

    Cockroach to Google Store Sales

    Google Store Sales for Cockroach: 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 Cockroach Meta Offline CAPI sync run?

    The pace follows your Cockroach tables: Signals sends changes from Cockroach to Meta each time the read runs. Because it reads only the records changed since the last run, in-store and phone revenue joining Meta's optimization loop stays current while platform teams running CockroachDB keep Meta's 62-day event window in view. Delivery needs no export and no manual upload.

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

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

    NEXT STEP

    Cockroach to Meta Offline CAPI, in production this week.

    Talk to our team All Cockroach use cases