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

    CONNECTIONS / Website / Website to X CAPI

    From Website events to the X Conversions API.

    Connect Website and point Signals at your website events; it reports online sales to X server-side so campaigns keep measuring conversions as each event fires, hashed and consent-checked for X.

    Talk to our team Explore the setup

    website -> x-capi :: live

    1. ● website → x.capi :: live
    2. > read web_orders rows=31,288
    3. hash sha256(email,phone) consent=filtered
    4. route x deliver
    5. ✓ delivered · 23,153 matched

    WHAT THIS ENABLES

    Website to X Conversions API

    Website to X Conversions API: your website events, hashed and consent-checked, feed X as Signals reports online sales to X server-side so campaigns keep measuring conversions as each event fires.

    • On-site purchase and checkout events from your website events 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 website events by web teams instrumenting the site.

    WHAT FLOWS WHERE

    Website to X CAPI, mapped.

    Signals receives the on-site purchase and checkout events from your website events; Signals hashes and consent-screens each record before X's Conversions API accepts the web conversions for hashed-email matching.

    Signals receives the on-site purchase and checkout events from your website events; 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 on-site pixel and tag events.

    Web teams instrumenting the site activating the X Conversions API straight from website events.

    HOW DATAHASH SETS IT UP

    From kickoff to verified events.

    1. Connect

      A Signals tag or pixel on your site to feed X's Conversions API, sized for hashed-email matching.

    2. Map

      Signals receives your website events, 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 website events, reports online sales to X server-side so campaigns keep measuring conversions, and forwards each event as it arrives, 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 website events and forwards each event as it arrives.

    Online sales still counted on X from your website events, with event volume steady because Signals forwards each event as it arrives.

    A per-run match report from X's Conversions API on hashed-email matching, straight out of your website events.

    ON THE WIRE

    What X CAPI actually receives.

    signals :: website.x-capi :: wire

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

    Adjacent moves on the same stack.

    from Website

    Website to Meta CAPI

    Website to Meta Conversions API: your website events, hashed and consent-checked, feed Meta…

    Learn more

    from Website

    Website to Meta CTM

    Website to Meta Click-to-Message: your website events, hashed and consent-checked, feed…

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

    You set the cadence, from near-real-time to a nightly Website sync of your website events into X. Since Signals forwards each event as it arrives, X conversions that persist after the browser signal fades keeps pace and web teams instrumenting the site watch hashed-email matching. One scoped connection sets it up, cadence adjustable later.

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

    In Website, match rate tracks the email and phone quality your website events carry. Clean identifiers land for X; blank ones never will. The first Conversions API report shows web teams instrumenting the site where hashed-email matching needs work, a data-quality task handled in Website.

    NEXT STEP

    Website to X CAPI, in production this week.

    Talk to our team All Website use cases