Here's where you can learn what's changed in each Measurement Protocol release.

For official Google Analytics API announcements, subscribe to the [Google
Analytics API Notify Group](https://groups.google.com/forum/#!forum/google-analytics-api-notify).

## 2026-02-17

- Added support for accepting a [client ID
  cookie](https://support.google.com/analytics/answer/11397207) for `client_id` and a [session ID cookie](https://support.google.com/analytics/answer/11397207) for `session_id`.

We still recommend sending non-cookie values for `client_id` and
`session_id`, for example using the approach in [Send events to Measurement
Protocol](https://developers.google.com/gtagjs/reference/api#get_mp_example).

## 2026-01-08

- The [validation](https://developers.google.com/analytics/devguides/collection/protocol/ga4/validating-events.md.txt) endpoint has been updated to support the change from [2025-12-11](https://developers.google.com/analytics/devguides/collection/protocol/ga4/changelog.md.txt#2025-12-11), which allows `in_app_purchase` events to be sent to App streams. This is now a valid event.

## 2025-12-11

- Google Analytics now lets you send `in_app_purchase` events to an App stream using the Measurement Protocol. For other stream types, the `in_app_purchase` event is still a [reserved
  event](https://developers.google.com/analytics/devguides/collection/protocol/ga4/reference#reserved_names) and is not allowed.
- An update is coming soon to the [validation](https://developers.google.com/analytics/devguides/collection/protocol/ga4/validating-events.md.txt) endpoint to align with this change. In the meantime, `in_app_purchase` will still be flagged as a reserved event.

## 2025-12-11

- Added support for accepting [`session_id`](https://developers.google.com/analytics/devguides/collection/protocol/ga4/reference.md.txt#session_id) and `session_number` event parameter values in the format used by the corresponding [Analytics Session Id](https://support.google.com/tagmanager/answer/7182738#utilities) and [Analytics Session Number](https://support.google.com/tagmanager/answer/7182738#utilities) built-in variables in Google Tag Manager.

## 2025-09-30

The [GA4 Event Builder](https://ga-dev-tools.google/ga4/event-builder/) on the
Google Analytics Demos and Tools site has been updated with the following
features:

- The [`screen_view`](https://developers.google.com/analytics/devguides/collection/protocol/ga4/reference/events.md.txt#screen_view) and [`ad_impression`](https://developers.google.com/analytics/devguides/collection/protocol/ga4/reference/events.md.txt#ad_impression) events are now available to be sent for App data streams. See the [2023-09-27 entry](https://developers.google.com/analytics/devguides/collection/protocol/ga4/changelog.md.txt#2023-09-27) for more context.
- You can now include [geographic information](https://developers.google.com/analytics/devguides/collection/protocol/ga4/reference.md.txt#payload_geo_info) in your events using the `user_location` and `ip_override` fields.
- Support for sending [device information](https://developers.google.com/analytics/devguides/collection/protocol/ga4/reference.md.txt#payload_device_info) has been added, including `device` attributes (brand, model, etc.) as well as the `user_agent` string.
- A new toggle lets you send data to the EU-specific endpoint (`https://region1.google-analytics.com/mp/collect`) and use the corresponding EU validation endpoint.
- Support for [overriding `timestamp_micros`](https://developers.google.com/analytics/devguides/collection/protocol/ga4/sending-events.md.txt#override_timestamp) at the event level and within user properties has been added. The tool also now includes an easy-to-use date time picker to help you input the Unix timestamps.

## 2025-06-11

- Added `device` and `user_agent` fields. Use either field to [send device
  information](https://developers.google.com/analytics/devguides/collection/protocol/ga4/reference#payload_device_info) for Measurement Protocol events.

## 2025-05-28

- Added a [validation](https://developers.google.com/analytics/devguides/collection/protocol/ga4/validating-events.md.txt) endpoint `https://region1.google-analytics.com/debug/mp/collect` for events to be collected in the EU.

## 2025-05-14

- Added `user_location` and `ip_override` fields. Use either field to [send geographic information](https://developers.google.com/analytics/devguides/collection/protocol/ga4/reference.md.txt#payload_geo_info) for Measurement Protocol events.
- Added a new endpoint `https://region1.google-analytics.com/mp/collect` to use if you want your Measurement Protocol data to be collected in the EU.

## 2024-09-10

- Google Analytics now automatically joins the most recent device information from tagging with Measurement Protocol events using `client_id` or `app_instance_ID`.

## 2023-09-27

- You can now send the [`ad_impression`](https://developers.google.com/analytics/devguides/collection/protocol/ga4/reference/events.md.txt#ad_impression) and [`screen_view`](https://developers.google.com/analytics/devguides/collection/protocol/ga4/reference/events.md.txt#screen_view) events with Measurement Protocol. Previously, these were [reserved events](https://developers.google.com/analytics/devguides/collection/protocol/ga4/reference.md.txt#reserved_names).

## 2023-01-23

- Google Analytics 4 now automatically joins the most recent geographic information from tagging with Measurement Protocol events using `client_id` or `app_instance_ID`.

## 2022-05-23

- `session_id`: include `session_id` as a param, so that measurement protocol events appear in session-based reporting.
- `user_id`: previously, if (a) `app_instance_id`/`client_id` is sent without `user_id` and (b) measurement protocol events are sent with `app_instance_id` with `user_id`, the MP events weren't being exported to Ads properly. This has been fixed so that now the measurement protocol events are exported and attributed.

## 2021-02-26

- Conversion events no longer need to be sent with an 8 hour delay.

## 2020-10-14

- Updated naming from App + Web to Google Analytics 4.