Google Analytics 4

Fidero delivers your events to Google Analytics 4 through the Measurement Protocol and stitches them to the browser session, so server conversions land on the same user and session as the web activity that led to them.

Channel	Browser + server
Consent category	`analytics`
Deduplication	No shared event ID – client-side and server-side events are routed so each fires once. The browser sends web events, and the server sends server events plus any you add to `webEventOverrides`.
Identifiers	The GA4 `client_id`, `session_id` and `session_number` captured in the browser and forwarded to the server, plus `user_id`. Optional enhanced user data – email, phone, name and address – is hashed when you enable it and advertising consent applies.

What it delivers

Server and browser events. Web events fire client-side through gtag. Server events reach GA4 through the Measurement Protocol – routed so each fires once
Session stitching. The client_id and session IDs captured in the browser travel to the server, so a server conversion joins the original web session
Standalone and Firebase properties. Both web Measurement IDs and Firebase-linked properties are supported

What you provide

Item	Detail
Measurement ID	Your GA4 Measurement ID, or a Firebase App ID for a Firebase-linked property.
Measurement Protocol API secret	Generated in the data stream settings of your GA4 property.

That's everything. Mapping, formatting, hashing and deduplication are already built in – you switch the destination on by requesting it, and the flow is on the Destinations overview.

What's automatic

Session capture. The GA4 client_id, session_id and session_number are read from the browser and forwarded, so server events keep the same session
Google Consent Mode. Consent signals – analytics_storage, ad_user_data and ad_personalization – are set from the visitor's consent state
Enhanced data hashing. When enabled, email, phone and name are SHA-256 hashed server-side before they leave

Enrichment, consent enforcement, delivery monitoring and managed adapter updates apply to every third-party destination – what every destination receives covers the standard treatment.

Event mapping

Fidero's standard events map to Google Analytics 4's own event names automatically:

Fidero event	Google Analytics 4 event
`purchase_completed`	`purchase`
`checkout_started`	`begin_checkout`
`payment_info_added`	`add_payment_info`
`item_added`	`add_to_cart`
`item_viewed`	`view_item`
`item_list_viewed`	`view_item_list`
`search_performed`	`search`
`signup_completed`	`sign_up`
`user_logged_in`	`login`
`lead_form_completed`	`generate_lead`
`trial_started`	`trial_start`
`subscription_started`	`purchase`
`trial_converted`	`purchase` – server events only
`subscription_renewed`	`purchase` – server events only
`subscription_cancelled`	`subscription_cancel`