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

    CONNECTIONS / BigCommerce / BigCommerce to X CAPI

    Your BigCommerce orders, wired to the X Conversions API.

    Connect BigCommerce and point Signals at your BigCommerce 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

    bigcommerce -> x-capi :: live

    1. ● bigcommerce → x.capi :: live
    2. > read web_orders rows=44,191
    3. hash sha256(email,phone) consent=filtered
    4. route x deliver
    5. ✓ delivered · 32,701 matched

    WHAT THIS ENABLES

    BigCommerce to X Conversions API

    X Conversions API for BigCommerce: Signals reports online sales to X server-side so campaigns keep measuring conversions straight from your BigCommerce orders, hashed and consent-screened as orders complete.

    • On-site purchase and checkout events from your BigCommerce 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 BigCommerce orders by merchants running BigCommerce.

    WHAT FLOWS WHERE

    BigCommerce to X CAPI, mapped.

    Signals reads the on-site purchase and checkout events from your BigCommerce 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 BigCommerce 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 BigCommerce orders, customers, and catalog.

    Merchants running BigCommerce activating the X Conversions API straight from BigCommerce orders.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      Scoped API access to BigCommerce, reading only your BigCommerce orders to feed X's Conversions API, sized for hashed-email matching.

    2. Map

      Signals reads your BigCommerce 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 BigCommerce 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 BigCommerce orders and sends only the orders that changed.

    Online sales still counted on X from your BigCommerce 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 BigCommerce orders.

    ON THE WIRE

    What X CAPI actually receives.

    signals :: bigcommerce.x-capi :: wire

    1. ● signals :: event payload
    2. > POST /conversion source=bigcommerce.web_orders
    3. conversion_time 1784099639000
    4. identifiers [{ hashed_email: "9c04ef…" }]
    5. conversion_value 1502.00 · conversion_currency SAR
    6. ✓ accepted · match=true
    RELATED USE CASES

    Adjacent moves on the same stack.

    from BigCommerce

    BigCommerce to Meta CAPI

    Meta Conversions API for BigCommerce: Signals sends every browser checkout to Meta…

    Learn more

    from BigCommerce

    BigCommerce to Meta CTM

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

    Learn more

    same use case

    GA4 to X CAPI

    X Conversions API for GA4: Signals reports online sales to X server-side so campaigns keep…

    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 BigCommerce X CAPI sync run?

    The pace follows your BigCommerce orders: Signals sends changes from BigCommerce 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 merchants running BigCommerce keep hashed-email matching in view. Delivery needs no export and no manual upload.

    What match rate should a BigCommerce-sourced X CAPI batch expect?

    Coverage of hashed identifiers across your BigCommerce orders decides it, and merchants running BigCommerce own that inside BigCommerce. A live email or phone matches into X; neither, and it will not. First-run feedback flags hashed-email matching, which merchants running BigCommerce then raise inside your BigCommerce orders.

    NEXT STEP

    BigCommerce to X CAPI, in production this week.

    Talk to our team All BigCommerce use cases