試用 Google Analytics 的 MCP 伺服器。從
GitHub 安裝，詳情請參閱
公告。
Changelog
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
您可以在這裡瞭解各個 Measurement Protocol 版本異動內容。
如要接收 Google Analytics API 的官方公告，請訂閱 Google Analytics API 通知群組。
2025-06-11
- 新增
device 和 user_agent 欄位。使用任一欄位傳送裝置資訊，以供 Measurement Protocol 事件使用。
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 做為參數納入，這樣評估通訊協定事件就會顯示在以工作階段為準的報表中。user_id：先前，如果 (a) 傳送 app_instance_id/client_id 時沒有 user_id，且 (b) 傳送的 Measurement Protocol 事件含有 app_instance_id 和 user_id，系統就無法將這些事件正確匯出至 Google Ads。這項問題已修正，現在系統會匯出並歸因 Measurement Protocol 事件。
2021-02-26
2020-10-14
- 將「應用程式 + 網站」更名為「Google Analytics 4」。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-08-26 (世界標準時間)。
[null,null,["上次更新時間：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."]]
