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

    CONNECTIONS / Microsoft SQL Server / SQL Server to Meta Offline CAPI

    Your SQL Server tables, wired to Meta's offline optimization.

    Connect SQL Server and point Signals at your SQL Server 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

    microsoft-sql-server -> meta-offline-capi :: live

    1. ● sql server → meta.capi :: live
    2. > read closed_deals rows=25,730
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 22,128 matched

    WHAT THIS ENABLES

    SQL Server to Meta Offline CAPI

    SQL Server to Meta Offline CAPI: Signals reads your SQL Server 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 SQL Server 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 SQL Server tables by data teams running SQL Server.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

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

    Data teams running SQL Server activating Meta's offline optimization straight from SQL Server tables.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    What Offline CAPI actually receives.

    signals :: microsoft-sql-server.meta-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversions source=microsoft-sql-server.closed_deals
    3. event_name "Purchase" · event_time 2026-07-19T01:46:36
    4. value 41399.00 · currency AED
    5. em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-50596"
    6. ✓ accepted match=86%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Microsoft SQL Server

    SQL Server to Google OCI

    SQL Server to Google Offline Conversions: Signals reads your SQL Server tables and…

    Learn more

    from Microsoft SQL Server

    SQL Server to Google Store Sales

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

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

    Match rate follows identifier coverage in your SQL Server tables, which data teams running SQL Server control, not SQL Server itself. A record with a current hashed email or phone matches for Meta; one missing both cannot. First-run feedback from Offline Conversions API pinpoints Meta's 62-day event window, the number data teams running SQL Server tune against.

    NEXT STEP

    SQL Server to Meta Offline CAPI, in production this week.

    Talk to our team All Microsoft SQL Server use cases