Jump to a popular page, or start typing.

    CONNECTIONS / Salesforce Commerce Cloud / Commerce Cloud to Snap CAPI

    Your Commerce Cloud orders, wired to Snapchat's web Conversions API.

    Connect Commerce Cloud and point Signals at your Commerce Cloud orders; it posts checkout purchases to Snapchat server-side alongside the pixel as orders complete, hashed and consent-checked for Snapchat.

    sfcc -> snap-web-capi :: live

    1. ● commerce cloud → snap.capi :: live
    2. > read web_orders rows=22,143
    3. hash sha256(email,phone) consent=filtered
    4. route snap deliver
    5. ✓ delivered · 17,493 matched

    WHAT THIS ENABLES

    Commerce Cloud to Snap Conversions API

    Commerce Cloud to Snap Conversions API: Signals reads your Commerce Cloud orders and posts checkout purchases to Snapchat server-side alongside the pixel, hashed and consent-checked as orders complete.

    • On-site purchase and checkout events from your Commerce Cloud orders activated for Snapchat, as Signals posts checkout purchases to Snapchat server-side alongside the pixel.
    • Web conversions Snapchat can optimize on without pixel-only gaps, drawn from your Commerce Cloud orders by enterprise retailers on Salesforce Commerce Cloud.

    WHAT FLOWS WHERE

    Salesforce Commerce Cloud to Web CAPI, mapped.

    Signals reads the on-site purchase and checkout events from your Commerce Cloud orders; Signals hashes and consent-screens each record before Snapchat's Conversions API accepts the web conversions for server-and-pixel deduplication.

    Signals reads the on-site purchase and checkout events from your Commerce Cloud orders; Signals hashes and consent-screens each record before Snapchat's Conversions API accepts the web conversions for server-and-pixel deduplication.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Snapchat advertisers whose store conversions slip past the pixel, with the records already in Salesforce Commerce Cloud orders and customer profiles.

    Enterprise retailers on Salesforce Commerce Cloud activating Snapchat's web Conversions API 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 server-and-pixel deduplication.

    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 server-and-pixel deduplication.

    3. Deliver

      On each run, Signals pulls your Commerce Cloud orders, posts checkout purchases to Snapchat server-side alongside the pixel, and sends only the orders that changed, with server-and-pixel deduplication in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Web conversions Snapchat can optimize on without pixel-only gaps on every run, as Signals reads your Commerce Cloud orders and sends only the orders that changed.

    Checkout purchases counted server-side on Snap from your Commerce Cloud orders, with API call volume steady because Signals sends only the orders that changed.

    A per-run match report from Snapchat's Conversions API on server-and-pixel deduplication, straight out of your Commerce Cloud orders.

    ON THE WIRE

    What Web CAPI actually receives.

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

    1. ● signals :: event payload
    2. > POST /v2/conversion source=sfcc.web_orders
    3. event_type "PURCHASE" · timestamp 1784151052
    4. hashed_email "2ac910…" · hashed_phone_number "e04b7f…"
    5. price 1949.00 · currency AED
    6. ✓ accepted · match=true
    FAQ

    Asked on almost every call.

    How often does the Commerce Cloud Snap 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, web conversions Snapchat can optimize on without pixel-only gaps stays current while enterprise retailers on Salesforce Commerce Cloud keep server-and-pixel deduplication in view. Delivery needs no export and no manual upload.

    What match rate should a Commerce Cloud-sourced Snap 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 server-and-pixel deduplication, which enterprise retailers on Salesforce Commerce Cloud then raise inside your Commerce Cloud orders.

    NEXT STEP

    Commerce Cloud to Snap CAPI, in production this week.