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

    CONNECTIONS / WordPress / WordPress to X CAPI

    Your WordPress orders, wired to the X Conversions API.

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

    wordpress -> x-capi :: live

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

    WHAT THIS ENABLES

    WordPress to X Conversions API

    WordPress to X Conversions API: Signals reads your WordPress 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 WordPress 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 WordPress orders by content-led merchants on WordPress.

    WHAT FLOWS WHERE

    WordPress to X CAPI, mapped.

    Signals reads the on-site purchase and checkout events from your WordPress orders as orders complete, hashes and screens each record, and posts the web conversions to X's Conversions API, keeping hashed-email matching in view.

    Signals reads the on-site purchase and checkout events from your WordPress orders as orders complete, hashes and screens each record, and posts the web conversions to X's Conversions API, keeping hashed-email matching in view.

    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 WordPress orders, users, and form entries.

    Content-led merchants on WordPress activating the X Conversions API straight from WordPress orders.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

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

    2. Map

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

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

    ON THE WIRE

    What X CAPI actually receives.

    signals :: wordpress.x-capi :: wire

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

    Adjacent moves on the same stack.

    from WordPress

    WordPress to Meta CAPI

    WordPress to Meta Conversions API: Signals reads your WordPress orders and sends every…

    Learn more

    from WordPress

    WordPress to Meta CTM

    WordPress to Meta Click-to-Message: Signals reads your WordPress orders and credits orders…

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

    Delivery tracks WordPress, run by content-led merchants on WordPress: a near-real-time or scheduled sync of your WordPress orders feeds X on that cadence. Each run sends only the orders that changed, so online sales still counted on X holds up on hashed-email matching. The live debugger confirms every delivery inline.

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

    Match rate follows identifier coverage in your WordPress orders, which content-led merchants on WordPress control, not WordPress itself. A record with a current hashed email or phone matches for X; one missing both cannot. First-run feedback from Conversions API pinpoints hashed-email matching, the number content-led merchants on WordPress tune against.

    NEXT STEP

    WordPress to X CAPI, in production this week.

    Talk to our team All WordPress use cases