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

    CONNECTIONS / Salesforce Commerce Cloud / Commerce Cloud to Snap Offline CAPI

    Your Commerce Cloud orders, wired to Snapchat in-store conversions.

    Connect Commerce Cloud and point Signals at your Commerce Cloud orders; it reports in-store purchases against the Snapchat campaigns that reached the buyer as orders complete, hashed and consent-checked for Snapchat.

    Talk to our team Explore the setup

    sfcc -> snap-offline-capi :: live

    1. ● commerce cloud → snap.capi :: live
    2. > read closed_deals rows=65,236
    3. hash sha256(email,phone) consent=filtered
    4. route snap deliver
    5. ✓ delivered · 55,451 matched

    WHAT THIS ENABLES

    Commerce Cloud to Snapchat Offline CAPI

    Commerce Cloud to Snapchat Offline CAPI: Signals reads your Commerce Cloud orders and reports in-store purchases against the Snapchat campaigns that reached the buyer, hashed and consent-checked as orders complete.

    • Offline and in-store sales from your Commerce Cloud orders 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 Commerce Cloud orders by enterprise retailers on Salesforce Commerce Cloud.
    WHAT FLOWS WHERE

    The click, the conversion, and the credit.

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

    Snap credits the campaign that sourced the conversion conversion happens off-platform Ad click on Snap S Order sync recorded in Salesforce Co… 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 Salesforce Commerce Cloud orders and customer profiles.

    Enterprise retailers on Salesforce Commerce Cloud activating Snapchat in-store conversions straight from Commerce Cloud orders.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped API access to Commerce Cloud, reading only your Commerce Cloud orders to feed Snapchat's Conversions API, sized for offline event timing.

    2. Map

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

    What Offline CAPI actually receives.

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

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

    Adjacent moves on the same stack.

    from Salesforce Commerce Cloud

    Commerce Cloud to Google OCI

    Commerce Cloud to Google Offline Conversions: Signals reads your Commerce Cloud orders and…

    Learn more

    from Salesforce Commerce Cloud

    Commerce Cloud to Google Store Sales

    Commerce Cloud to Google Store Sales: Signals reads your Commerce Cloud orders 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 Commerce Cloud Snap Offline CAPI sync run?

    The pace follows your Commerce Cloud orders: Signals sends changes from Commerce Cloud to Snapchat as orders complete. Because it sends only the orders that changed, physical-world sales counted inside Snapchat performance stays current while enterprise retailers on Salesforce Commerce Cloud keep offline event timing in view. Delivery needs no export and no manual upload.

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

    Coverage of hashed identifiers across your Commerce Cloud orders decides it, and enterprise retailers on Salesforce Commerce Cloud own that inside Commerce Cloud. A live email or phone matches into Snapchat; neither, and it will not. First-run feedback flags offline event timing, which enterprise retailers on Salesforce Commerce Cloud then raise inside your Commerce Cloud orders.

    NEXT STEP

    Commerce Cloud to Snap Offline CAPI, in production this week.

    Talk to our team All Salesforce Commerce Cloud use cases