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

    CONNECTIONS / Salesforce Commerce Cloud / Commerce Cloud to Meta CTM

    Your Commerce Cloud orders, wired to Meta click-to-message conversions.

    Connect Commerce Cloud and point Signals at your Commerce Cloud orders; it credits orders that began in a WhatsApp or Messenger chat to the ad that started it as orders complete, hashed and consent-checked for Meta.

    Talk to our team Explore the setup

    sfcc -> meta-click-to-message :: live

    1. ● commerce cloud → meta.ctm :: live
    2. > read web_orders rows=62,226
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 51,025 matched

    WHAT THIS ENABLES

    Commerce Cloud to Meta Click-to-Message

    Commerce Cloud to Meta Click-to-Message: Signals reads your Commerce Cloud orders and credits orders that began in a WhatsApp or Messenger chat to the ad that started it, hashed and consent-checked as orders complete.

    • On-site purchase and checkout events from your Commerce Cloud orders activated for Meta, as Signals credits orders that began in a WhatsApp or Messenger chat to the ad that started it.
    • Conversation-led sales tied back to the click-to-message ad, drawn from your Commerce Cloud orders by enterprise retailers on Salesforce Commerce Cloud.

    WHAT FLOWS WHERE

    Salesforce Commerce Cloud to Click-to-Message, mapped.

    Signals reads the on-site purchase and checkout events from your Commerce Cloud orders; Signals hashes and consent-screens each record before Meta's Conversions API accepts the web conversions for the ctwa_clid conversation match.

    Signals reads the on-site purchase and checkout events from your Commerce Cloud orders; Signals hashes and consent-screens each record before Meta's Conversions API accepts the web conversions for the ctwa_clid conversation match.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Brands closing sales over chat after a click-to-message ad, with the records already in Salesforce Commerce Cloud orders and customer profiles.

    Enterprise retailers on Salesforce Commerce Cloud activating Meta click-to-message 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 Meta's Conversions API, sized for the ctwa_clid conversation match.

    2. Map

      Signals reads your Commerce Cloud orders, and its columns map to Meta's Conversions API in the visual mapper, hashed and checked for the ctwa_clid conversation match.

    3. Deliver

      On each run, Signals pulls your Commerce Cloud orders, credits orders that began in a WhatsApp or Messenger chat to the ad that started it, and sends only the orders that changed, with the ctwa_clid conversation match in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Conversation-led sales tied back to the click-to-message ad on every run, as Signals reads your Commerce Cloud orders and sends only the orders that changed.

    Chat-started orders credited to the ad from your Commerce Cloud orders, with API call volume steady because Signals sends only the orders that changed.

    A per-run match report from Meta's Conversions API on the ctwa_clid conversation match, straight out of your Commerce Cloud orders.

    ON THE WIRE

    What Click-to-Message actually receives.

    signals :: sfcc.meta-click-to-message :: wire

    1. ● signals :: event payload
    2. > POST /events source=sfcc.web_orders ctwa_clid=carried
    3. event_name "Purchase" · event_time 1784109745
    4. ph sha256 "9e21ab…"
    5. value 2078.00 · currency USD
    6. ✓ accepted · conversation matched
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Salesforce Commerce Cloud

    Commerce Cloud to Meta CAPI

    Commerce Cloud to Meta Conversions API: Signals reads your Commerce Cloud orders and sends…

    Learn more

    from Salesforce Commerce Cloud

    Commerce Cloud to Google EC Web

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

    Learn more

    same use case

    BigCommerce to Meta CTM

    Meta Click-to-Message for BigCommerce: Signals credits orders that began in a WhatsApp or…

    Learn more

    generic

    Meta Click-to-Message Ads

    Meta's click-to-WhatsApp, click-to-Instagram, and click-to-Messenger ads start…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Commerce Cloud Meta CTM sync run?

    The pace follows your Commerce Cloud orders: Signals sends changes from Commerce Cloud to Meta as orders complete. Because it sends only the orders that changed, conversation-led sales tied back to the click-to-message ad stays current while enterprise retailers on Salesforce Commerce Cloud keep the ctwa_clid conversation match in view. Delivery needs no export and no manual upload.

    What match rate should a Commerce Cloud-sourced Meta CTM 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 Meta; neither, and it will not. First-run feedback flags the ctwa_clid conversation match, which enterprise retailers on Salesforce Commerce Cloud then raise inside your Commerce Cloud orders.

    NEXT STEP

    Commerce Cloud to Meta CTM, in production this week.

    Talk to our team All Salesforce Commerce Cloud use cases