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

    CONNECTIONS / MongoDB / MongoDB to Meta Offline CAPI

    From MongoDB collections to Meta's offline optimization.

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

    mongodb -> meta-offline-capi :: live

    1. ● mongodb → meta.capi :: live
    2. > read closed_deals rows=24,931
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 21,191 matched

    WHAT THIS ENABLES

    MongoDB to Meta Offline CAPI

    MongoDB to Meta Offline CAPI: Signals reads your MongoDB collections 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 MongoDB collections each time the read runs.
    • Campaign learning fed by real-world purchases, with no export step out of your MongoDB collections.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

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

    Application teams running MongoDB who need in-store and phone revenue joining Meta's optimization loop out of MongoDB collections.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

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

    What Offline CAPI actually receives.

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

    1. ● signals :: event payload
    2. > POST /offline_conversions source=mongodb.closed_deals
    3. event_name "Purchase" · event_time 2026-07-14T12:59:35
    4. value 35434.00 · currency SAR
    5. em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-41975"
    6. ✓ accepted match=85%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from MongoDB

    MongoDB to Google OCI

    MongoDB to Google Offline Conversions: Signals reads your MongoDB collections and…

    Learn more

    from MongoDB

    MongoDB to Google Store Sales

    MongoDB to Google Store Sales: Signals reads your MongoDB collections 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 MongoDB Meta Offline CAPI sync run?

    The pace follows your MongoDB collections: Signals sends changes from MongoDB 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 application teams running MongoDB keep Meta's 62-day event window in view. Delivery needs no export and no manual upload.

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

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

    NEXT STEP

    MongoDB to Meta Offline CAPI, in production this week.

    Talk to our team All MongoDB use cases