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

    CONNECTIONS / Salesforce Commerce Cloud / Commerce Cloud to X CAPI

    Your Commerce Cloud orders, wired to the X Conversions API.

    Connect Commerce Cloud and point Signals at your Commerce Cloud orders; it reports online sales to X server-side so campaigns keep measuring conversions as orders complete, hashed and consent-checked for X.

    Talk to our team Explore the setup

    sfcc -> x-capi :: live

    1. ● commerce cloud → x.capi :: live
    2. > read web_orders rows=23,885
    3. hash sha256(email,phone) consent=filtered
    4. route x deliver
    5. ✓ delivered · 20,063 matched

    WHAT THIS ENABLES

    Commerce Cloud to X Conversions API

    Commerce Cloud to X Conversions API: Signals reads your Commerce Cloud orders and reports online sales to X server-side so campaigns keep measuring conversions, hashed and consent-checked as orders complete.

    • On-site purchase and checkout events from your Commerce Cloud orders activated for X, as Signals reports online sales to X server-side so campaigns keep measuring conversions.
    • X conversions that persist after the browser signal fades, drawn from your Commerce Cloud orders by enterprise retailers on Salesforce Commerce Cloud.

    WHAT FLOWS WHERE

    Salesforce Commerce Cloud to X CAPI, mapped.

    Signals reads the on-site purchase and checkout events from your Commerce Cloud orders; Signals hashes and consent-screens each record before X's Conversions API accepts the web conversions for hashed-email matching.

    Signals reads the on-site purchase and checkout events from your Commerce Cloud orders; Signals hashes and consent-screens each record before X's Conversions API accepts the web conversions for hashed-email matching.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Advertisers keeping X conversion measurement alive post-cookie, with the records already in Salesforce Commerce Cloud orders and customer profiles.

    Enterprise retailers on Salesforce Commerce Cloud activating the X 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 X's Conversions API, sized for hashed-email matching.

    2. Map

      Signals reads your Commerce Cloud orders, and its columns map to X's Conversions API in the visual mapper, hashed and checked for hashed-email matching.

    3. Deliver

      On each run, Signals pulls your Commerce Cloud orders, reports online sales to X server-side so campaigns keep measuring conversions, and sends only the orders that changed, with hashed-email matching in the debugger.

    WHAT YOU GET

    What ships with this use case.

    X conversions that persist after the browser signal fades on every run, as Signals reads your Commerce Cloud orders and sends only the orders that changed.

    Online sales still counted on X from your Commerce Cloud orders, with API call volume steady because Signals sends only the orders that changed.

    A per-run match report from X's Conversions API on hashed-email matching, straight out of your Commerce Cloud orders.

    ON THE WIRE

    What X CAPI actually receives.

    signals :: sfcc.x-capi :: wire

    1. ● signals :: event payload
    2. > POST /conversion source=sfcc.web_orders
    3. conversion_time 1784191467000
    4. identifiers [{ hashed_email: "9c04ef…" }]
    5. conversion_value 4691.00 · conversion_currency SAR
    6. ✓ accepted · match=true
    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 Meta CTM

    Commerce Cloud to Meta Click-to-Message: Signals reads your Commerce Cloud orders and…

    Learn more

    same use case

    BigCommerce to X CAPI

    X Conversions API for BigCommerce: Signals reports online sales to X server-side so…

    Learn more

    generic

    X CAPI

    Datahash implements X (Twitter) Conversions API with dedupe against the X Pixel and hashed…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Commerce Cloud X CAPI sync run?

    The pace follows your Commerce Cloud orders: Signals sends changes from Commerce Cloud to X as orders complete. Because it sends only the orders that changed, X conversions that persist after the browser signal fades stays current while enterprise retailers on Salesforce Commerce Cloud keep hashed-email matching in view. Delivery needs no export and no manual upload.

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

    NEXT STEP

    Commerce Cloud to X CAPI, in production this week.

    Talk to our team All Salesforce Commerce Cloud use cases