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

    CONNECTIONS / Close / Close to Snap Offline CAPI

    Close smart-view opportunities into Snapchat, built for Snapchat in-store conversions.

    Signals reads your Close smart-view opportunities through scoped OAuth access to Close, reading only your Close smart-view opportunities, then reports in-store purchases against the Snapchat campaigns that reached the buyer so Snapchat sees offline conversions without an export.

    Talk to our team Explore the setup

    close -> snap-offline-capi :: live

    1. ● close → snap.capi :: live
    2. > read closed_deals rows=43,061
    3. hash sha256(email,phone) consent=filtered
    4. route snap deliver
    5. ✓ delivered · 34,449 matched

    WHAT THIS ENABLES

    Close to Snapchat Offline CAPI

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

    • Signals reports in-store purchases against the Snapchat campaigns that reached the buyer, reading your Close smart-view opportunities as records change.
    • In-person conversions Snapchat can bid on, with no export step out of your Close smart-view opportunities.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Snap credits the campaign that sourced the conversion conversion happens off-platform Ad click on Snap CRM record sync recorded in Close 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, working out of Close leads, calls, and smart-view opportunities.

    Inside-sales teams running Close who need physical-world sales counted inside Snapchat performance out of Close smart-view opportunities.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped OAuth access to Close, reading only your Close smart-view opportunities, mapped to Snapchat's Conversions API and tuned for offline event timing.

    2. Map

      Columns from your Close smart-view opportunities align to Snapchat's Conversions API in the visual mapper, hashed as the sync runs and checked for offline event timing.

    3. Deliver

      As records change, Signals reads your Close smart-view opportunities and reports in-store purchases against the Snapchat campaigns that reached the buyer, sends only the records that changed, with offline event timing 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 Close records the event.
    ON THE WIRE

    What Offline CAPI actually receives.

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

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

    Adjacent moves on the same stack.

    from Close

    Close to Google OCI

    Close to Google Offline Conversions: your Close smart-view opportunities, hashed and…

    Learn more

    from Close

    Close to Google Store Sales

    Close to Google Store Sales: your Close smart-view opportunities, hashed and…

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

    The pace follows your Close smart-view opportunities: Signals sends changes from Close to Snapchat as records change. Because it sends only the records that changed, physical-world sales counted inside Snapchat performance stays current while inside-sales teams running Close keep offline event timing in view. Delivery needs no export and no manual upload.

    What match rate should a Close-sourced Snap Offline CAPI batch expect?

    In Close, match rate tracks the email and phone quality your Close smart-view opportunities carry. Clean identifiers land for Snapchat; blank ones never will. The first Conversions API report shows inside-sales teams running Close where offline event timing needs work, a data-quality task handled in Close.

    NEXT STEP

    Close to Snap Offline CAPI, in production this week.

    Talk to our team All Close use cases