Skip to content
DestinationActivation

X (Twitter) Conversions API

X requires signed requests (OAuth 1.0a) and conversions pointing to an event pre-created in the ads account (the tw-… id). The platform signs every call and builds the identifiers — hashed email and phone, IP and user agent — skipping events without a primary identifier, which the API would reject.

Data delivered

Data delivered

  • Conversions tied to your account event id (tw-…)
  • Hashed email and phone + IP and user agent
  • Conversion value and deduplication id

What it is for

What you can do with it

  • Attribute sales to X campaigns without relying on the pixel
  • Reuse the same purchase event that already feeds Meta and TikTok

Why integrate

The business reason, not just the tech

Conversions without X's pixel

The server-side path attributes the sale to the campaign even when the browser blocks tracking — using the same purchase event you already configured for other destinations.

OAuth handled for you

X's API requires every request signed with OAuth 1.0a — four keys and per-call crypto. You paste the keys once into the vault; signing is automatic.

Pre-created events, mapped once

X works with events created in the account (tw-… ids). Copy the id from the manager, map it in the Delivery, and every conversion lands on the right event.

How to connect

Step by step

  1. Step 1

    Create the conversion event in X Ads and copy the tw-… id.

  2. Step 2

    Create the destination with the 4 OAuth keys from your developer account.

  3. Step 3

    Create a Delivery mapping your event to the matching tw-… id.

Frequently asked questions

Why four keys?

X's API uses OAuth 1.0a: consumer key and secret identify the app; access token and secret identify the account. All four live in the secrets vault, never in the interface.

Start measuring what actually becomes revenue

Create a free account, connect your first source and see your first lead timeline today. No card required.