CONNECTIONS / GA4 / GA4 to X CAPI
Your GA4 events, wired to the X Conversions API.
Signals reads your GA4 events through read access to your GA4 event stream, then reports online sales to X server-side so campaigns keep measuring conversions so X sees web conversions without an export.
- ● ga4 → x.capi :: live
- > read web_orders rows=15,572
- hash sha256(email,phone) consent=filtered
- route x deliver
- ✓ delivered · 11,679 matched
WHAT THIS ENABLES
GA4 to X Conversions API
X Conversions API for GA4: Signals reports online sales to X server-side so campaigns keep measuring conversions straight from your GA4 events, hashed and consent-screened as each event fires.
- Signals reports online sales to X server-side so campaigns keep measuring conversions, reading your GA4 events as each event fires.
- Online sales still counted on X, with no export step out of your GA4 events.
WHAT FLOWS WHERE
GA4 to X CAPI, mapped.
Each sync hands the on-site purchase and checkout events from your GA4 events to Signals, which hashes and filters every record, then X's Conversions API logs the web conversions for hashed-email matching.
Each sync hands the on-site purchase and checkout events from your GA4 events to Signals, which hashes and filters every record, then X's Conversions API logs the web conversions for hashed-email matching.
Built for the teams that own the number.
Analytics teams instrumenting GA4 who need X conversions that persist after the browser signal fades out of GA4 events.
From kickoff to verified events.
-
Connect
Read access to your GA4 event stream, mapped to X's Conversions API and tuned for hashed-email matching.
-
Map
Columns from your GA4 events align to X's Conversions API in the visual mapper, hashed as each event fires and checked for hashed-email matching.
-
Deliver
As each event fires, Signals reads your GA4 events and reports online sales to X server-side so campaigns keep measuring conversions, forwards each event as it arrives, with hashed-email matching watched in the debugger.
What ships with this use case.
X conversions that persist after the browser signal fades from your GA4 events, delivered as each event fires.
Online sales still counted on X out of your GA4 events, delivered as each event fires without event volume climbing.
Match feedback on hashed-email matching from X's Conversions API each run, tied back to your GA4 events.
What X CAPI actually receives.
- ● signals :: event payload
- > POST /conversion source=ga4.web_orders
- conversion_time 1784769528000
- identifiers [{ hashed_email: "9c04ef…" }]
- conversion_value 3441.00 · conversion_currency AED
- ✓ accepted · match=true
Adjacent moves on the same stack.
from GA4
GA4 to Meta CAPI
Meta Conversions API for GA4: Signals sends every browser checkout to Meta server-side so…
Learn morefrom GA4
GA4 to Meta CTM
Meta Click-to-Message for GA4: Signals credits orders that began in a WhatsApp or Messenger…
Learn more
same use case
BigCommerce to X CAPI
X Conversions API for BigCommerce: Signals reports online sales to X server-side so…
Learn moregeneric
X CAPI
Datahash implements X (Twitter) Conversions API with dedupe against the X Pixel and hashed…
Learn moreAsked on almost every call.
How often does the GA4 X CAPI sync run?
The pace follows your GA4 events: Signals sends changes from GA4 to X as each event fires. Because it forwards each event as it arrives, X conversions that persist after the browser signal fades stays current while analytics teams instrumenting GA4 keep hashed-email matching in view. Delivery needs no export and no manual upload.
What match rate should a GA4-sourced X CAPI batch expect?
In GA4, match rate tracks the email and phone quality your GA4 events carry. Clean identifiers land for X; blank ones never will. The first Conversions API report shows analytics teams instrumenting GA4 where hashed-email matching needs work, a data-quality task handled in GA4.
NEXT STEP