Try the MCP server for Google Analytics. Install from GitHub, and see the announcement for more details.

Changelog

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.

2025-09-30

The GA4 Event Builder on the Google Analytics Demos and Tools site has been updated with the following features:

The screen_view and ad_impression events are now available to be sent for App data streams. See the 2023-09-27 entry for more context.
You can now include geographic information in your events using the user_location and ip_override fields.
Support for sending device information 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 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.

Added device and user_agent fields. Use either field to send device information for Measurement Protocol events.

Added a validation endpoint https://region1.google-analytics.com/debug/mp/collect for events to be collected in the EU.

Added user_location and ip_override fields. Use either field to send geographic information 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.

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

You can now send the ad_impression and screen_view events with Measurement Protocol. Previously, these were reserved events.

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

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.