Jump to a popular page, or start typing.

    CONNECTIONS / BigCommerce / BigCommerce to TikTok Web eAPI

    Your BigCommerce orders, wired to TikTok's web Events API.

    Connect BigCommerce and point Signals at your BigCommerce orders; it sends checkout events to TikTok server-side, deduped against the pixel as orders complete, hashed and consent-checked for TikTok.

    bigcommerce -> tiktok-web-eapi :: live

    1. ● bigcommerce → tiktok.eapi :: live
    2. > read web_orders rows=67,948
    3. hash sha256(email,phone) consent=filtered
    4. route tiktok deliver
    5. ✓ delivered · 52,320 matched

    WHAT THIS ENABLES

    BigCommerce to TikTok Events API

    TikTok Events API for BigCommerce: Signals sends checkout events to TikTok server-side, deduped against the pixel straight from your BigCommerce orders, hashed and consent-screened as orders complete.

    • On-site purchase and checkout events from your BigCommerce orders activated for TikTok, as Signals sends checkout events to TikTok server-side, deduped against the pixel.
    • Purchase signal that holds up when the browser pixel drops, drawn from your BigCommerce orders by merchants running BigCommerce.

    WHAT FLOWS WHERE

    BigCommerce to Web eAPI, mapped.

    Signals reads the on-site purchase and checkout events from your BigCommerce orders; Signals hashes and consent-screens each record before TikTok's Events API accepts the web conversions for event_id deduplication.

    Signals reads the on-site purchase and checkout events from your BigCommerce orders; Signals hashes and consent-screens each record before TikTok's Events API accepts the web conversions for event_id deduplication.

    WHO THIS IS FOR

    Built for the teams that own the number.

    TikTok advertisers whose web conversions leak through the pixel, with the records already in BigCommerce orders, customers, and catalog.

    Merchants running BigCommerce activating TikTok's web Events 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 TikTok's Events API, sized for event_id deduplication.

    2. Map

      Signals reads your BigCommerce orders, and its columns map to TikTok's Events API in the visual mapper, hashed and checked for event_id deduplication.

    3. Deliver

      On each run, Signals pulls your BigCommerce orders, sends checkout events to TikTok server-side, deduped against the pixel, and sends only the orders that changed, with event_id deduplication in the debugger.

    WHAT YOU GET

    What ships with this use case.

    Purchase signal that holds up when the browser pixel drops on every run, as Signals reads your BigCommerce orders and sends only the orders that changed.

    Server-side purchases deduped against the pixel from your BigCommerce orders, with API call volume steady because Signals sends only the orders that changed.

    A per-run match report from TikTok's Events API on event_id deduplication, straight out of your BigCommerce orders.

    ON THE WIRE

    What Web eAPI actually receives.

    signals :: bigcommerce.tiktok-web-eapi :: wire

    1. ● signals :: event payload
    2. > POST /event/track source=bigcommerce.web_orders
    3. event "CompletePayment" · event_time 1784772572
    4. user.email sha256 "64af2c…" · user.phone sha256 "0d93b7…"
    5. properties.value 3659.00 · properties.currency AED
    6. ✓ accepted · dedupe=event_id
    FAQ

    Asked on almost every call.

    How often does the BigCommerce TikTok Web eAPI sync run?

    The pace follows your BigCommerce orders: Signals sends changes from BigCommerce to TikTok as orders complete. Because it sends only the orders that changed, purchase signal that holds up when the browser pixel drops stays current while merchants running BigCommerce keep event_id deduplication in view. Delivery needs no export and no manual upload.

    What match rate should a BigCommerce-sourced TikTok Web eAPI 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 TikTok; neither, and it will not. First-run feedback flags event_id deduplication, which merchants running BigCommerce then raise inside your BigCommerce orders.

    NEXT STEP

    BigCommerce to TikTok Web eAPI, in production this week.