CONNECTIONS / X
X Conversions API, server-side and hashed.
Datahash works directly with X to implement the X Conversions API, with dedupe against the X Pixel and hashed identifier support.
- > event x.sync status=ok
- hash sha256(email,phone) pii=cleared
- route every X destination
- ✓ X connected · live
The full X stack, page by page.
Every source, one path into X.
Signals hashes and dedupes each event once, then routes it to every X destination on this page. No separate pipeline per offering.
Brands running X on Signals.
Questions your team will ask.
What is the X Conversions API?
X's server-side channel for sending conversion events directly from your systems to X. It keeps campaign measurement intact where the X Pixel is blocked or limited by browser privacy controls. Datahash implements it end to end, from event mapping and hashing through dedupe validation and production monitoring.
How does dedupe against the X Pixel work?
Both sources send the same event with a shared identifier and X keeps only one copy. Datahash generates and matches the event IDs across pixel and server, so running both never double counts a conversion. The pixel still captures browser-side signals the server-side event cannot see on its own.
What identifiers does X match on?
X matches on hashed email, hashed phone number, and the X click ID (twclid) captured on landing. Identifiers are hashed with SHA-256 at source, so raw PII never leaves your systems unhashed. Richer identifiers on each event raise match rates and give X's optimization more signal to work with.
NEXT STEP
Book a X stack working session.
We map your source data against every integration on this page and propose a sequence.