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

    CONNECTIONS / Databricks / Databricks to Meta Offline CAPI

    Your Databricks lakehouse, wired to Meta's offline optimization.

    Signals reads the Delta table through a Unity Catalog grant and credits dealer, branch, and phone sales to the Meta campaigns behind them, hashed on the way out and governed like any other lakehouse job.

    Talk to our team Explore the setup

    databricks -> meta-offline-capi :: live

    1. ● databricks → meta.capi :: live
    2. > read main.sales.pos_ledger rows=49,363
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 38,997 matched

    WHAT THIS ENABLES

    Databricks to Meta Offline CAPI

    Databricks to Meta Offline CAPI: A notebook job reads the offline and in-store sales in your Databricks Delta tables, and Signals credits dealer, branch, and phone sales to the Meta campaigns behind them, hashed and consent-checked each time the model rebuilds.

    • Signals credits dealer, branch, and phone sales to the Meta campaigns behind them, reading your Databricks Delta tables each time the model rebuilds.
    • In-store and phone revenue joining Meta's optimization loop, fed by data engineers modeling in Databricks notebooks.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Meta credits the campaign that sourced the conversion conversion happens off-platform Ad click on Meta D Delta table sync recorded in Databricks 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 numbers already modeled in Databricks Delta tables governed by Unity Catalog.

    Data engineers modeling in Databricks notebooks who need in-store and phone revenue joining Meta's optimization loop.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A Unity Catalog-scoped service principal on the single Delta table in play to feed Meta's Offline Conversions API, sized for Meta's 62-day event window.

    2. Map

      A notebook job reads your Databricks Delta 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

      Each time the model rebuilds, Signals credits dealer, branch, and phone sales to the Meta campaigns behind them, reads only the rows the model rebuilt, 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 Databricks records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

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

    1. ● signals :: event payload
    2. > POST /offline_conversions source=databricks.main.sales.pos_ledger
    3. event_name "Purchase" · event_time 2026-07-17T14:28:17
    4. value 42600.00 · currency USD
    5. em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-68497"
    6. ✓ accepted match=79%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Databricks

    Databricks to Google OCI

    Databricks to Google Offline Conversions: A notebook job reads the offline and in-store…

    Learn more

    from Databricks

    Databricks to Google Store Sales

    Databricks to Google Store Sales: A notebook job reads the offline and in-store sales in…

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

    Cadence follows the job that rebuilds the table: a nightly model gives Meta a nightly feed, an hourly one an hourly feed. Because a run picks up only the rows the model rebuilt, in-store and phone revenue joining Meta's optimization loop keeps pace on Meta's 62-day event window and job-cluster time stays modest.

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

    Identifier quality in the Delta table drives it, not the cluster size. Rows carrying a live hashed email or phone land; rows with neither will not, and no rebuild changes that. The opening run's feedback from Meta's Offline Conversions API flags the gap for considered-purchase brands closing revenue far from the browser tracking Meta's 62-day event window.

    NEXT STEP

    Databricks to Meta Offline CAPI, in production this week.

    Talk to our team All Databricks use cases