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

    CONNECTIONS / Kommo / Kommo to Snap Offline CAPI

    Your Kommo messenger pipelines, wired to Snapchat in-store conversions.

    Connect Kommo and point Signals at your Kommo messenger pipelines; it reports in-store purchases against the Snapchat campaigns that reached the buyer as records change, hashed and consent-checked for Snapchat.

    Talk to our team Explore the setup

    kommo -> snap-offline-capi :: live

    1. ● kommo → snap.capi :: live
    2. > read closed_deals rows=26,387
    3. hash sha256(email,phone) consent=filtered
    4. route snap deliver
    5. ✓ delivered · 23,484 matched

    WHAT THIS ENABLES

    Kommo to Snapchat Offline CAPI

    Kommo to Snapchat Offline CAPI: your Kommo messenger pipelines, hashed and consent-checked, feed Snapchat as Signals reports in-store purchases against the Snapchat campaigns that reached the buyer as records change.

    • Offline and in-store sales from your Kommo messenger pipelines 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 Kommo messenger pipelines by conversational-sales teams on Kommo.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Snap credits the campaign that sourced the conversion conversion happens off-platform Ad click on Snap CRM record sync recorded in Kommo 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 Kommo leads and messenger-driven pipelines.

    Conversational-sales teams on Kommo activating Snapchat in-store conversions straight from Kommo messenger pipelines.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Kommo, reading only your Kommo messenger pipelines to feed Snapchat's Conversions API, sized for offline event timing.

    2. Map

      Signals reads your Kommo messenger pipelines, 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 Kommo messenger pipelines, reports in-store purchases against the Snapchat campaigns that reached the buyer, and sends only the records that changed, 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 Kommo records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

    signals :: kommo.snap-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /v2/conversion source=kommo.closed_deals
    3. event_type "PURCHASE" · event_conversion_type "OFFLINE"
    4. hashed_email "5d8b22…" · hashed_phone_number "a179fe…"
    5. timestamp 1784357367 · price 43358 · currency SAR
    6. ✓ accepted · match=true
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Kommo

    Kommo to Google OCI

    Kommo to Google Offline Conversions: your Kommo messenger pipelines, hashed and…

    Learn more

    from Kommo

    Kommo to Google Store Sales

    Kommo to Google Store Sales: your Kommo messenger pipelines, hashed and consent-checked,…

    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 Kommo Snap Offline CAPI sync run?

    Delivery tracks Kommo, run by conversational-sales teams on Kommo: a near-real-time or scheduled sync of your Kommo messenger pipelines feeds Snapchat on that cadence. Each run sends only the records that changed, 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 Kommo-sourced Snap Offline CAPI batch expect?

    Match rate follows identifier coverage in your Kommo messenger pipelines, which conversational-sales teams on Kommo control, not Kommo 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 conversational-sales teams on Kommo tune against.

    NEXT STEP

    Kommo to Snap Offline CAPI, in production this week.

    Talk to our team All Kommo use cases