更新日志
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
您可以在此处了解每个 Measurement Protocol 版本中的变化。
如需了解有关 Google Analytics API 的官方公告，请订阅 Google Analytics API Notify 群组。
2025-06-11
2025-05-28
- 为要在欧盟境内收集的活动添加了验证端点
https://region1.google-analytics.com/debug/mp/collect。
2025-05-14
- 添加了
user_location 和 ip_override 字段。您可以使用任一字段发送地理位置信息，以用于 Measurement Protocol 事件。
- 新增了一个端点
https://region1.google-analytics.com/mp/collect，如果您希望在欧盟境内收集 Measurement Protocol 数据，可以使用此端点。
2024-09-10
- Google Analytics 现在会自动将标记中的最新设备信息与使用
client_id 或 app_instance_ID 的 Measurement Protocol 事件相联接。
2023-09-27
2023-01-23
- Google Analytics 4 现在会自动将标记中的最新地理位置信息与使用
client_id 或 app_instance_ID 的 Measurement Protocol 事件相联接。
2022-05-23
session_id：将 session_id 添加为参数，以便 Measurement Protocol 事件显示在基于会话的报告中。user_id：之前，如果 (a) app_instance_id/client_id 在发送时不带 user_id，并且 (b) 发送 Measurement Protocol 事件时 app_instance_id 带有 user_id，那么 MP 事件将不会正确导出到 Google Ads。此问题已得到解决，现在可导出 Measurement Protocol 事件并对其进行归因。
2021-02-26
2020-10-14
- 已将名称从“应用 + 网站”更新为“Google Analytics 4”。
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-08-26。
[null,null,["最后更新时间 (UTC)：2025-08-26。"],[[["\u003cp\u003eGoogle Analytics 4 automatically joins recent device and geographic data from website/app tagging with Measurement Protocol events using identifiers like \u003ccode\u003eclient_id\u003c/code\u003e or \u003ccode\u003eapp_instance_ID\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eYou can now send \u003ccode\u003ead_impression\u003c/code\u003e and \u003ccode\u003escreen_view\u003c/code\u003e events using Measurement Protocol, which were previously reserved.\u003c/p\u003e\n"],["\u003cp\u003eMeasurement Protocol events are now properly attributed and exported to Ads even when \u003ccode\u003euser_id\u003c/code\u003e is sent separately with \u003ccode\u003eapp_instance_id\u003c/code\u003e/\u003ccode\u003eclient_id\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eMeasurement Protocol now supports parameters like \u003ccode\u003esession_id\u003c/code\u003e for session-based reporting.\u003c/p\u003e\n"],["\u003cp\u003eConversion events sent via Measurement Protocol no longer require an 8-hour delay.\u003c/p\u003e\n"]]],["Google Analytics updates include automatically joining device and geographic information with Measurement Protocol events using `client_id` or `app_instance_ID`. The `ad_impression` and `screen_view` events are now supported. `session_id` inclusion enables session-based reporting. Fixed an issue preventing proper export and attribution of Measurement Protocol events when using `user_id`. Conversion events now support real-time reporting. The App + Web name was changed to Google Analytics 4.\n"],null,["Here's where you can learn what's changed in each Measurement Protocol release.\n\nFor official Google Analytics API announcements, subscribe to the [Google\nAnalytics API Notify Group](//groups.google.com/forum/#!forum/google-analytics-api-notify).\n\n2025-06-11\n\n- Added `device` and `user_agent` fields. Use either field to [send device\n information](/analytics/devguides/collection/protocol/ga4/reference#payload_device_info) for Measurement Protocol events.\n\n2025-05-28\n\n- Added a [validation](/analytics/devguides/collection/protocol/ga4/validating-events) endpoint `https://region1.google-analytics.com/debug/mp/collect` for events to be collected in the EU.\n\n2025-05-14\n\n- Added `user_location` and `ip_override` fields. Use either field to [send geographic information](/analytics/devguides/collection/protocol/ga4/reference#payload_geo_info) for Measurement Protocol events.\n- 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.\n\n2024-09-10\n\n- Google Analytics now automatically joins the most recent device information from tagging with Measurement Protocol events using `client_id` or `app_instance_ID`.\n\n2023-09-27\n\n- You can now send the [`ad_impression`](/analytics/devguides/collection/protocol/ga4/reference/events#ad_impression) and [`screen_view`](/analytics/devguides/collection/protocol/ga4/reference/events#screen_view) events with Measurement Protocol. Previously, these were [reserved events](/analytics/devguides/collection/protocol/ga4/reference?#reserved_names).\n\n2023-01-23\n\n- Google Analytics 4 now automatically joins the most recent geographic information from tagging with Measurement Protocol events using `client_id` or `app_instance_ID`.\n\n2022-05-23\n\n- `session_id`: include `session_id` as a param, so that measurement protocol events appear in session-based reporting.\n- `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.\n\n2021-02-26\n\n- Conversion events no longer need to be sent with an 8 hour delay.\n\n2020-10-14\n\n- Updated naming from App + Web to Google Analytics 4."]]
