Integrations / Other
Google GA4
Server-side event tracking via the GA4 Measurement Protocol with session handling, engagement time, Consent Mode v2, IP-resolved geo, and Enhanced Conversions (user_data).
Datafly Signal delivers first-party events to Google GA4 server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Google GA4 expects.
Why route Google GA4 through Datafly Signal
Delivery happens server-to-server
Signal sends events to Google GA4 from your own infrastructure rather than from the visitor's browser, so delivery does not depend on client-side conditions.
Email, phone number, first name and last name hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so Google GA4 receives match keys rather than raw personal data.
Client IP and user agent are preserved
Server-to-server delivery normally loses both, which weakens matching. Signal forwards the genuine visitor values as request headers so Google GA4 attributes the event to the right session.
Click identifiers are captured and replayed
Signal stores gclid, wbraid, gbraid first-party at collection time and attaches them to the conversion later, so attribution survives even when the original landing cookie has expired.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the Google GA4 rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
Google GA4 is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
add_payment_infoadd_shipping_infoadd_to_cartadd_to_wishlistbegin_checkoutbooking_cancelledbooking_completedbooking_startedbrochure_downloadedconfigure_vehiclecontent_downloadeddealer_contacteddemo_requesteddestination_searcheddestination_viewedfeature_usedfinance_quote_requestedflight_searchedflight_viewedgenerate_leadget_quotehotel_searchedhotel_viewedlisting_savedlisting_viewedloginonboarding_completedonboarding_startedpageplan_viewedpolicy_cancelledpolicy_renewedpurchasequote_receivedquote_requestedquote_startedrefundremove_from_cartsearchselect_itemselect_promotionservice_appointment_bookedsign_upsubscription_cancelledsubscription_startedtest_drive_bookedtrade_in_valuedtrial_startedvehicle_comparedvehicle_savedvehicle_searchedvehicle_viewedview_cartview_itemview_item_listview_promotionVertical presets
Standard (page views + sessions), Retail, Travel, B2B / SaaS, Automotive, Insurance. Each preset starts from a working configuration for that vertical rather than a blank field map.
Frequently asked questions
Does Datafly Signal integrate with Google GA4?
Yes. Datafly Signal delivers first-party events to Google GA4 server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Google GA4 expects. The integration is included in every deployment at no additional cost.
How is server-side Google GA4 tracking different from the Google GA4 tag?
The Google GA4 tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to Google GA4 from your server, so delivery does not depend on browser conditions.
What personal data is sent to Google GA4?
Email, phone number, first name and last name are normalised and SHA-256 hashed inside your own deployment before delivery, so Google GA4 receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to Google GA4?
The blueprint ships with mappings for add_payment_info, add_shipping_info, add_to_cart, add_to_wishlist, begin_checkout, booking_cancelled, booking_completed, booking_started, and more. Any event in your schema can be mapped to Google GA4 through pipeline configuration without a code change.
Do I need to keep the Google GA4 tag on my site?
No. Signal delivers to Google GA4 from the server, so no client-side Google GA4 script is required on your site.
Ready to move Google GA4 server-side?
See how Datafly Signal delivers first-party events to Google GA4 from infrastructure you control, with hashed identity and consent enforcement built in.