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

    CONNECTIONS / Apache Cassandra / Apache Cassandra to Meta Offline CAPI

    From Cassandra tables to Meta's offline optimization.

    Connect Apache Cassandra and point Signals at your Cassandra 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

    apache-cassandra -> meta-offline-capi :: live

    1. ● apache cassandra → meta.capi :: live
    2. > read closed_deals rows=16,574
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 13,259 matched

    WHAT THIS ENABLES

    Apache Cassandra to Meta Offline CAPI

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

    • Offline and in-store sales from your Cassandra 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 Cassandra tables by platform teams running Cassandra.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

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

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

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A read-only database user scoped to the Cassandra 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 Cassandra 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 Cassandra 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 Apache Cassandra records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

    signals :: apache-cassandra.meta-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversions source=apache-cassandra.closed_deals
    3. event_name "Purchase" · event_time 2026-07-23T04:37:42
    4. value 38670.00 · currency GBP
    5. em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-50462"
    6. ✓ accepted match=80%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Apache Cassandra

    Apache Cassandra to Google OCI

    Apache Cassandra to Google Offline Conversions: Signals reads your Cassandra tables and…

    Learn more

    from Apache Cassandra

    Apache Cassandra to Google Store Sales

    Apache Cassandra to Google Store Sales: Signals reads your Cassandra tables and matches…

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

    You set the cadence, from near-real-time to a nightly Apache Cassandra sync of your Cassandra 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 platform teams running Cassandra watch Meta's 62-day event window. One scoped connection sets it up, cadence adjustable later.

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

    In Apache Cassandra, match rate tracks the email and phone quality your Cassandra tables carry. Clean identifiers land for Meta; blank ones never will. The first Offline Conversions API report shows platform teams running Cassandra where Meta's 62-day event window needs work, a data-quality task handled in Apache Cassandra.

    NEXT STEP

    Apache Cassandra to Meta Offline CAPI, in production this week.

    Talk to our team All Apache Cassandra use cases