이제 Google 애널리틱스 4에서 client_id 또는 app_instance_ID를 사용하여 태그에서 가져온 최신 지리 정보를 측정 프로토콜 이벤트와 자동으로 결합합니다.
2022-05-23
session_id: session_id가 매개변수로 포함되므로 측정 프로토콜 이벤트가 세션 기반 보고서에 표시됩니다.
user_id: 이전에는 (a) app_instance_id/client_id가 user_id 없이 전송되고 (b) 측정 프로토콜 이벤트가 user_id가 포함된 app_instance_id와 함께 전송되는 경우 MP 이벤트가 Ads 속성으로 전송되지 않았습니다. 이 문제가 해결되어 이제 측정 프로토콜 이벤트가 내보내지고 기여도가 부여됩니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["필요한 정보가 없음","missingTheInformationINeed","thumb-down"],["너무 복잡함/단계 수가 너무 많음","tooComplicatedTooManySteps","thumb-down"],["오래됨","outOfDate","thumb-down"],["번역 문제","translationIssue","thumb-down"],["샘플/코드 문제","samplesCodeIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-08-26(UTC)"],[[["\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."]]
