The server-side request adscapi builds when you track() a purchase and X (Twitter) is configured. Secrets and hashed values show as placeholders.
https://ads-api.x.com/12/measurement/conversions/{X_PIXEL_ID}Authorization: Bearer {X_CAPI_TOKEN}
Content-Type: application/json{
"conversions": [
{
"conversion_id": "purchase",
"conversion_time": "2025-02-13T13:20:00.000Z",
"identifiers": [
{
"hashed_email": "<sha256(normalized-email)>"
},
{
"hashed_phone_number": "<sha256(e164-phone)>"
}
],
"event_id": "order_1001",
"value": 49.99,
"currency": "USD"
}
]
}Verified against the library dispatcher (src/dispatchers/x.ts). See the X (Twitter) setup guide for where to get each secret.
X_PIXEL_IDX_CAPI_TOKENX (Twitter) activates when every secret is present. One missing key and the platform no-ops — the rest still receive the event.
| Canonical event | X (Twitter) receives |
|---|---|
page_view | page_view |
lead | lead |
signup_start | signup_start (custom event passthrough) |
signup | signup |
checkout_created | checkout_created |
purchase | purchase |
reply_generated | reply_generated (custom event passthrough) |
upgrade_clicked | upgrade_clicked (custom event passthrough) |
Discover more free tools to fix your tracking
Pick a canonical conversion event, fill the fields, and see the exact JSON payload adscapi builds — before you write a line of code.
Try it nowType a raw email or phone number and see the normalized value plus its SHA-256 hash — the exact rules adscapi applies per platform. Nothing leaves the browser.
Try it nowSearch all 26 ad platforms adscapi dispatches to — support level, required secrets, and setup docs, always in sync with the library registry.
Try it nowadscapi is free and open source. Set your platform tokens, call track() once, and every configured Conversions API receives the event — hashed the way each platform expects.