Changelog
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
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.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-10-09 UTC.
[null,null,["Last updated 2024-10-09 UTC."],[[["Google Analytics 4 automatically joins recent device and geographic data from website/app tagging with Measurement Protocol events using identifiers like `client_id` or `app_instance_ID`."],["You can now send `ad_impression` and `screen_view` events using Measurement Protocol, which were previously reserved."],["Measurement Protocol events are now properly attributed and exported to Ads even when `user_id` is sent separately with `app_instance_id`/`client_id`."],["Measurement Protocol now supports parameters like `session_id` for session-based reporting."],["Conversion events sent via Measurement Protocol no longer require an 8-hour delay."]]],[]]