GA4 Measurement Protocol: Server-Side Event Sending Explained

How the Measurement Protocol works

The GA4 Measurement Protocol is an HTTP API. You send a POST request to https://www.google analytics.com/mp/collect with your Measurement ID, an API Secret, and a JSON payload describing the event. Google processes the request and attributes the event to a user session based on the client_id (for web) or app_instance_id (for apps) you include in the payload.

The critical requirement: the client_id must match an existing GA4 session.

Measurement Protocol events sent with unknown client_ids are accepted by the API but cannot be attributed to a user session and won't appear in standard reports.

Always capture the client_id from the browser session and pass it to your backend along with the transaction or action that triggers the server side event.

Common use cases

• Refunds: The most important Measurement Protocol use case. When your backend processes a return, send a refund event with the original transaction_id to offset revenue.
• Subscription renewals: When a subscription renews in your billing system, send a purchase event server side. This captures revenue that happens without any user browser session (scheduled renewals, card on file charges).
• Offline conversions: If a user signs up online and converts offline (phone sale, in person visit), the Measurement Protocol lets you record that conversion against their original online session.

Validation and debugging

Measurement Protocol events are NOT visible in GA4 DebugView, this is a common source of confusion. To validate your implementation, use the Measurement Protocol Validation endpoint: https://www.google analytics.com/debug/mp/collect. It returns a JSON response describing any validation errors without sending the event to GA4.

For production validation, check the GA4 Realtime report 5 to 10 minutes after sending test events.

If events don't appear, verify your API Secret is correctly generated (Admin → Data Streams → Measurement Protocol API secrets) and that your client_id matches a real GA4 session from the same property.