X CAPI
X Conversions API, server-side and hashed.
Datahash implements X (Twitter) Conversions API with dedupe against the X Pixel and hashed identifier support.
- ● x.capi :: live
- > event Purchase value=214.00 AED
- hash sha256(em) twclid=captured
- dedupe event_id vs pixel matched
- ✓ delivered · conversion accepted
Built for the teams that own the number.
Teams that want server-side parity across every paid channel.
From kickoff to verified events.
-
Audit
X Pixel coverage and event map baseline.
-
Configure
Server-side Conversions API with dedupe against the Pixel and hashed identifiers.
-
Verify
Events confirmed in X Ads Manager before go-live.
WHAT FLOWS WHERE
One use case, every source.
A purchase fires on your website, Signals hashes the identifiers and deduplicates on the shared event ID, then posts the event to X's Conversions API server-side.
A purchase fires on your website, Signals hashes the identifiers and deduplicates on the shared event ID, then posts the event to X's Conversions API server-side.
What ships with this offering.
Deduped Pixel plus CAPI on every key event.
Hashed identifier support for better matching.
Server-side delivery resilient to browser loss.
ON THE WIRE
What the platform actually receives.
Identifiers are hashed with SHA-256 at source. The payload the destination sees never contains raw PII.
- ● signals :: event payload
- > POST /12/measurement/conversions/{pixel}
- event "Purchase" · conversion_id "e2f9c1…"
- identifiers hashed_email "9b1a4d…" · twclid "tw.1…"
- conversion_time 1789002233 · value 214 · AED
- ✓ accepted · 1 conversion
Adjacent moves on the same stack.
meta
Meta Web CAPI
Datahash is a Meta Business Partner. We set up Meta Conversions API on your website server-side, deduped with your existing Meta Pixel, hashed and privacy-safe.
Learn more
tiktok
TikTok Web eAPI
Datahash is a TikTok Partner. We deliver server-side TikTok Events API with dedupe against your existing Pixel and full support for TikTok's advanced matching parameters.
Learn more
Reddit CAPI
Datahash sets up Reddit CAPI with dedupe against the Reddit Pixel and hashed advanced matching.
Learn more
LinkedIn CAPI
Datahash implements LinkedIn CAPI with hashed identifiers, deduplication, and CRM-driven lead stage delivery for B2B campaigns.
Learn moreBring it from where the data lives.
Every source that supports this use case. Pick a platform to see the exact setup.
Custom
Questions your team will ask.
Do we keep the X Pixel?
Yes. The X Pixel keeps running in the browser exactly as it does today, while the Conversions API runs alongside it rather than replacing it. Datahash dedupes both on a shared event identifier, so each conversion counts once in X Ads Manager while overall coverage improves, including events the Pixel alone would miss.
What identifiers does X match on?
X matches primarily on hashed email plus the click identifiers carried from the ad itself. Datahash hashes every identifier before it leaves your environment, then attaches the strongest key set your site is able to capture on each event, which improves match rates without ever exposing raw customer data to X.
How long does setup take?
With ad account access and a working event map in place, the integration is typically configured and verified within a single working session. Datahash then monitors the connection through its first days live, checking that events land correctly in X Ads Manager and that matching rates hold steady before handing the connection off to your team.
NEXT STEP
Live in fifteen minutes. Measurable in a week.
Talk to our team of solutions engineers. We map your source data, propose an integration plan, and give you a live setup in the same call where possible.