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

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

    Your SQL Server tables, wired to Snapchat in-store conversions.

    Connect SQL Server and point Signals at your SQL Server tables; it reports in-store purchases against the Snapchat campaigns that reached the buyer each time the read runs, hashed and consent-checked for Snapchat.

    Talk to our team Explore the setup

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

    1. ● sql server → snap.capi :: live
    2. > read closed_deals rows=9,109
    3. hash sha256(email,phone) consent=filtered
    4. route snap deliver
    5. ✓ delivered · 7,743 matched

    WHAT THIS ENABLES

    SQL Server to Snapchat Offline CAPI

    SQL Server to Snapchat Offline CAPI: Signals reads your SQL Server tables and reports in-store purchases against the Snapchat campaigns that reached the buyer, hashed and consent-checked each time the read runs.

    • Offline and in-store sales from your SQL Server tables activated for Snapchat, as Signals reports in-store purchases against the Snapchat campaigns that reached the buyer.
    • Physical-world sales counted inside Snapchat performance, 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 Snap, away from any pixel. Here is how Microsoft SQL Server closes the loop.

    Snap credits the campaign that sourced the conversion conversion happens off-platform Ad click on Snap Scheduled read sync recorded in Microsoft SQL… S Signals hash · dedupe Conversions API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Retail and QSR advertisers whose Snapchat audience buys in person, with the records already in SQL Server tables, views, and indexed views.

    Data teams running SQL Server activating Snapchat in-store conversions 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 Snapchat's Conversions API, sized for offline event timing.

    2. Map

      A scheduled read pulls your SQL Server tables, and its columns map to Snapchat's Conversions API in the visual mapper, hashed and checked for offline event timing.

    3. Deliver

      On each run, Signals pulls your SQL Server tables, reports in-store purchases against the Snapchat campaigns that reached the buyer, and reads only the records changed since the last run, with offline event timing 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.snap-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /v2/conversion source=microsoft-sql-server.closed_deals
    3. event_type "PURCHASE" · event_conversion_type "OFFLINE"
    4. hashed_email "5d8b22…" · hashed_phone_number "a179fe…"
    5. timestamp 1784297087 · price 35835 · currency SAR
    6. ✓ accepted · match=true
    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 Snap Offline CAPI

    ActiveCampaign to Snapchat Offline CAPI: Signals reads your ActiveCampaign contacts and…

    Learn more

    generic

    Snap Offline CAPI

    Deliver offline conversions to Snap on a schedule that fits your operations.

    Learn more
    FAQ

    Asked on almost every call.

    How often does the SQL Server Snap 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 Snapchat on that cadence. Each run reads only the records changed since the last run, so in-person conversions Snapchat can bid on holds up on offline event timing. The live debugger confirms every delivery inline.

    What match rate should a SQL Server-sourced Snap 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 Snapchat; one missing both cannot. First-run feedback from Conversions API pinpoints offline event timing, the number data teams running SQL Server tune against.

    NEXT STEP

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

    Talk to our team All Microsoft SQL Server use cases