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

    CONNECTIONS / Salesforce Commerce Cloud / Commerce Cloud to Meta Custom Audience

    Your Commerce Cloud orders, wired to Meta lookalike and suppression seeds.

    Connect Commerce Cloud and point Signals at your Commerce Cloud orders; it keeps Meta audiences synced as adds and removals so lists never drift as orders complete, hashed and consent-checked for Meta.

    Talk to our team Explore the setup

    sfcc -> meta-custom-audience :: live

    1. ● commerce cloud → meta.audience :: live
    2. > read segments rows=26,527
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 22,813 matched

    WHAT THIS ENABLES

    Commerce Cloud to Meta Custom Audience

    Commerce Cloud to Meta Custom Audience: Signals reads your Commerce Cloud orders and keeps Meta audiences synced as adds and removals so lists never drift, hashed and consent-checked as orders complete.

    • Customer segments from your Commerce Cloud orders activated for Meta, as Signals keeps Meta audiences synced as adds and removals so lists never drift.
    • Lookalike seeds and suppression lists that track your live customer base, drawn from your Commerce Cloud orders by enterprise retailers on Salesforce Commerce Cloud.

    WHAT FLOWS WHERE

    Salesforce Commerce Cloud to Custom Audience, mapped.

    Signals reads the customer segments from your Commerce Cloud orders; Signals hashes and consent-screens each record before Meta's Custom Audiences API accepts the match-ready audiences for audience refresh cadence.

    Signals reads the customer segments from your Commerce Cloud orders; Signals hashes and consent-screens each record before Meta's Custom Audiences API accepts the match-ready audiences for audience refresh cadence.

    WHO THIS IS FOR

    Built for the teams that own the number.

    Performance teams running first-party suppression and lookalike seeds, with the records already in Salesforce Commerce Cloud orders and customer profiles.

    Enterprise retailers on Salesforce Commerce Cloud activating Meta lookalike and suppression seeds 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 Custom Audiences API, sized for audience refresh cadence.

    2. Map

      Signals reads your Commerce Cloud orders, and its columns map to Meta's Custom Audiences API in the visual mapper, hashed and checked for audience refresh cadence.

    3. Deliver

      On each run, Signals pulls your Commerce Cloud orders, keeps Meta audiences synced as adds and removals so lists never drift, and sends only the orders that changed, with audience refresh cadence in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Lookalike seeds and suppression lists that track your live customer base on every run, as Signals reads your Commerce Cloud orders and sends only the orders that changed.

    Always-current lookalike seeds and exclusions 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 Custom Audiences API on audience refresh cadence, straight out of your Commerce Cloud orders.

    ON THE WIRE

    What Custom Audience actually receives.

    signals :: sfcc.meta-custom-audience :: wire

    1. ● signals :: audience upload
    2. > POST /customaudiences source=sfcc.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. num_received 26,527 · num_invalid_entries -328
    5. audience_id "1678303" · session "upsert"
    6. ✓ accepted match=86%
    RELATED USE CASES

    Adjacent moves on the same stack.

    from Salesforce Commerce Cloud

    Commerce Cloud to Google Customer Match

    Commerce Cloud to Google Customer Match: Signals reads your Commerce Cloud orders and…

    Learn more

    from Salesforce Commerce Cloud

    Commerce Cloud to TikTok Custom Audience

    Commerce Cloud to TikTok Custom Audience: Signals reads your Commerce Cloud orders and…

    Learn more

    same use case

    ActiveCampaign to Meta Custom Audience

    ActiveCampaign to Meta Custom Audience: Signals reads your ActiveCampaign contacts and deal…

    Learn more

    generic

    Meta Custom Audience

    Build and refresh Meta Custom Audiences from your CRM, warehouse, or SingleView, with…

    Learn more
    FAQ

    Asked on almost every call.

    How often does the Commerce Cloud Meta Custom Audience 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, lookalike seeds and suppression lists that track your live customer base stays current while enterprise retailers on Salesforce Commerce Cloud keep audience refresh cadence in view. Delivery needs no export and no manual upload.

    What match rate should a Commerce Cloud-sourced Meta Custom Audience 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 audience refresh cadence, which enterprise retailers on Salesforce Commerce Cloud then raise inside your Commerce Cloud orders.

    NEXT STEP

    Commerce Cloud to Meta Custom Audience, in production this week.

    Talk to our team All Salesforce Commerce Cloud use cases