CONNECTIONS / GA4
GA4 events, delivered to every ad platform.
Signals reads your GA4 event stream through the BigQuery export and forwards each event as it lands. Purchases, leads, and custom conversions reach every platform you advertise on, hashed and consent-filtered before they leave.
- ● ga4 :: signals live
- > event purchase value=142.00 USD
- > event begin_checkout step=payment
- hash sha256(email,phone) consent=filtered
- route meta · google · tiktok · pinterest
- ✓ 4 destinations synced · match 81%
The signal GA4 yields.
Every kind of signal that moves between GA4 and the platforms, through one hashed, deduplicated route.
- Web conversions
- The intraday tables update continuously through the day, so a purchase logged in GA4 this morning reaches ad platforms the same morning, not the next data refresh.
Pick your platform. Every use case for it, in one place.
Every way GA4 data moves, grouped by platform and ranked by how many use cases GA4 supports.
Meta 2 
Google 1 
LinkedIn 1 
OpenAI 1 
Pinterest 1 
Reddit 1 
Snap 1 
TikTok 1 
X 1 From authorization to delivered signal.
-
Connect
Link the GA4 BigQuery export, daily or streaming, as a read-only source, or point Signals at your Measurement Protocol stream directly.
-
Map
GA4 event and user parameters mapped to each destination's own event schema in the visual mapper.
-
Consent
Consent Mode v2 state read from GA4 and enforced per destination, so nothing reaches a platform a visitor opted out of.
-
Deliver
Server-side delivery to every mapped destination, verified in the live debugger before campaigns rely on it.
GA4 questions, answered.
Can Signals read our GA4 BigQuery export directly?
Yes. Signals connects to the GA4 BigQuery export as a read-only source, working from either the daily batch tables or the streaming intraday tables that update through the day. Standard ecommerce events and any custom events configured in GA4 are read the same way, with no separate SDK or tag needed on your site.
Do we still need gtag.js or the GA4 tag on our site?
Yes, GA4's own tag keeps doing what it already does: populating your analytics reports and the BigQuery export Signals reads from. Signals does not replace that collection layer; it reads the event stream GA4 already produces and forwards it server-side to ad platforms, so removing the tag would cut off both GA4 reporting and this connection.
How is Consent Mode handled when GA4 is the source?
Consent Mode v2 state is captured in GA4 exactly as Google requires it, and Signals reads that state alongside each event rather than inferring it separately. A visitor who denies analytics or ad storage consent in GA4 stays excluded from every destination Signals delivers to, so a consent decision made on-site holds everywhere downstream.
NEXT STEP
See your GA4 data working in every ad platform.
Ready to enable a use case, or still mapping what GA4 data could do? Our team helps you find the right place to start.
