Jump to a popular page, or start typing.

    CONNECTIONS / WooCommerce / WooCommerce to Meta Custom Audience

    From WooCommerce orders to Meta lookalike and suppression seeds.

    Signals reads your WooCommerce orders through scoped API access to WooCommerce, reading only your WooCommerce orders, then keeps Meta audiences synced as adds and removals so lists never drift so Meta sees match-ready audiences without an export.

    woocommerce -> meta-custom-audience :: live

    1. ● woocommerce → meta.audience :: live
    2. > read segments rows=23,019
    3. hash sha256(email,phone) consent=filtered
    4. route meta deliver
    5. ✓ delivered · 16,804 matched

    WHAT THIS ENABLES

    WooCommerce to Meta Custom Audience

    Meta Custom Audience for WooCommerce: Signals keeps Meta audiences synced as adds and removals so lists never drift straight from your WooCommerce orders, hashed and consent-screened as orders complete.

    • Signals keeps Meta audiences synced as adds and removals so lists never drift, reading your WooCommerce orders as orders complete.
    • Always-current lookalike seeds and exclusions, with no export step out of your WooCommerce orders.

    WHAT FLOWS WHERE

    WooCommerce to Custom Audience, mapped.

    Each sync hands the customer segments from your WooCommerce orders to Signals, which hashes and filters every record, then Meta's Custom Audiences API logs the match-ready audiences for audience refresh cadence.

    Each sync hands the customer segments from your WooCommerce orders to Signals, which hashes and filters every record, then Meta's Custom Audiences API logs 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, working out of WooCommerce orders, customers, and subscriptions.

    WordPress merchants running WooCommerce who need lookalike seeds and suppression lists that track your live customer base out of WooCommerce orders.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped API access to WooCommerce, reading only your WooCommerce orders, mapped to Meta's Custom Audiences API and tuned for audience refresh cadence.

    2. Map

      Columns from your WooCommerce orders align to Meta's Custom Audiences API in the visual mapper, hashed as each order syncs and checked for audience refresh cadence.

    3. Deliver

      As orders complete, Signals reads your WooCommerce orders and keeps Meta audiences synced as adds and removals so lists never drift, sends only the orders that changed, with audience refresh cadence watched in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Lookalike seeds and suppression lists that track your live customer base from your WooCommerce orders, delivered as orders complete.

    Always-current lookalike seeds and exclusions out of your WooCommerce orders, delivered as orders complete without API call volume climbing.

    Match feedback on audience refresh cadence from Meta's Custom Audiences API each run, tied back to your WooCommerce orders.

    ON THE WIRE

    What Custom Audience actually receives.

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

    1. ● signals :: audience upload
    2. > POST /customaudiences source=woocommerce.segments
    3. schema ["EMAIL_SHA256","PHONE_SHA256"]
    4. num_received 23,019 · num_invalid_entries 307
    5. audience_id "1695744" · session "upsert"
    6. ✓ accepted match=73%
    FAQ

    Asked on almost every call.

    How often does the WooCommerce Meta Custom Audience sync run?

    You set the cadence, from near-real-time to a nightly WooCommerce sync of your WooCommerce orders into Meta. Since Signals sends only the orders that changed, lookalike seeds and suppression lists that track your live customer base keeps pace and WordPress merchants running WooCommerce watch audience refresh cadence. One scoped connection sets it up, cadence adjustable later.

    What match rate should a WooCommerce-sourced Meta Custom Audience batch expect?

    Match rate follows identifier coverage in your WooCommerce orders, which WordPress merchants running WooCommerce control, not WooCommerce itself. A record with a current hashed email or phone matches for Meta; one missing both cannot. First-run feedback from Custom Audiences API pinpoints audience refresh cadence, the number WordPress merchants running WooCommerce tune against.

    NEXT STEP

    WooCommerce to Meta Custom Audience, in production this week.