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

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

    Your Commerce Cloud orders, wired to Meta's offline optimization.

    Connect Commerce Cloud and point Signals at your Commerce Cloud orders; it credits dealer, branch, and phone sales to the Meta campaigns behind them as orders complete, hashed and consent-checked for Meta.

    Talk to our team Explore the setup

    sfcc -> meta-offline-capi :: live

    1. ● commerce cloud → meta.capi :: live
    2. > read closed_deals rows=60,847
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 49,895 matched

    WHAT THIS ENABLES

    Commerce Cloud to Meta Offline CAPI

    Commerce Cloud to Meta Offline CAPI: Signals reads your Commerce Cloud orders and credits dealer, branch, and phone sales to the Meta campaigns behind them, hashed and consent-checked as orders complete.

    • Offline and in-store sales from your Commerce Cloud orders activated for Meta, as Signals credits dealer, branch, and phone sales to the Meta campaigns behind them.
    • In-store and phone revenue joining Meta's optimization loop, 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 Meta, away from any pixel. Here is how Salesforce Commerce Cloud closes the loop.

    Meta credits the campaign that sourced the conversion conversion happens off-platform Ad click on Meta S Order sync recorded in Salesforce Co… S Signals hash · dedupe Offline Conversions API delivered · credited
    WHO THIS IS FOR

    Built for the teams that own the number.

    Considered-purchase brands closing revenue far from the browser, with the records already in Salesforce Commerce Cloud orders and customer profiles.

    Enterprise retailers on Salesforce Commerce Cloud activating Meta's offline optimization 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 Offline Conversions API, sized for Meta's 62-day event window.

    2. Map

      Signals reads your Commerce Cloud orders, and its columns map to Meta's Offline Conversions API in the visual mapper, hashed and checked for Meta's 62-day event window.

    3. Deliver

      On each run, Signals pulls your Commerce Cloud orders, credits dealer, branch, and phone sales to the Meta campaigns behind them, and sends only the orders that changed, with Meta's 62-day event window 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.meta-offline-capi :: wire

    1. ● signals :: event payload
    2. > POST /offline_conversions source=sfcc.closed_deals
    3. event_name "Purchase" · event_time 2026-07-22T11:43:32
    4. value 30264.00 · currency AED
    5. em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-57612"
    6. ✓ accepted match=82%
    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 Meta Offline CAPI

    ActiveCampaign to Meta Offline CAPI: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Meta Offline CAPI

    Datahash ingests offline transactions from your POS, CRM, or warehouse and routes them to…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Commerce Cloud Meta Offline CAPI 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, in-store and phone revenue joining Meta's optimization loop stays current while enterprise retailers on Salesforce Commerce Cloud keep Meta's 62-day event window in view. Delivery needs no export and no manual upload.

    What match rate should a Commerce Cloud-sourced Meta 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 Meta; neither, and it will not. First-run feedback flags Meta's 62-day event window, which enterprise retailers on Salesforce Commerce Cloud then raise inside your Commerce Cloud orders.

    NEXT STEP

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

    Talk to our team All Salesforce Commerce Cloud use cases