Choose the platform you want to see in this guide:
Format the request
The Google Analytics Measurement Protocol only supports HTTP POST requests.
To send an event, use the following format:
POST /mp/collect HTTP/1.1
HOST: www.google-analytics.com
Content-Type: application/json
PAYLOAD_DATA
You must provide the following in the request URL:
api_secret: The API SECRET generated in the Google Analytics UI.
To create a new secret, navigate to
Admin > Data collection and modification > Data streams >
choose your stream > Measurement Protocol API secrets > Create.
measurement_id: The measurement ID associated with a stream, found in the
Google Analytics UI under Admin > Data Streams > choose your
stream > Measurement ID.
The measurement_id isn't your Stream ID.
You must provide a request body in the JSON POST body format for
the Measurement Protocol. Here's an example:
While session_start is a reserved event
name,
creating a new session_id creates a new session without the need to send
session_start. Understand how sessions are
counted.
Try it
Here's an example you can use to send multiple events at once. This example
sends a tutorial_begin event and a
join_group event to your Google Analytics server, includes geographic
information using the user_location field, and includes device information
using the device field.
The Measurement Protocol uses the first timestamp it finds in the following list
for each event in the request:
The timestamp_micros of the event.
The timestamp_micros of the request.
The time that the Measurement Protocol receives the request.
The following example sends a request-level timestamp that applies to all of the
events in the request. As a result, the Measurement Protocol assigns both the
tutorial_begin and join_group events a timestamp of
requestUnixEpochTimeInMicros.
The following example sends both a request-level timestamp and an event-level
timestamp. As a result, the Measurement Protocol assigns the tutorial_begin
event a timestamp of tutorialBeginUnixEpochTimeInMicros, and the join_group
event a timestamp of requestUnixEpochTimeInMicros.
The following limitations apply to sending Measurement Protocol events to Google
Analytics:
Requests can have a maximum of 25 events.
Events can have a maximum of 25 parameters.
Events can have a maximum of 25 user properties.
User property names must be 24 characters or fewer.
User property values must be 36 characters or fewer.
Event names must be 40 characters or fewer, can only contain alphanumeric
characters and underscores, and must start with an alphabetic character.
Parameter names including item parameters must be 40 characters or fewer,
can only contain alphanumeric characters and underscores, and must start
with an alphabetic character.
Parameter values including item parameter values must be 100 characters or
fewer for a standard Google Analytics property, and 500 characters or fewer
for a Google Analytics 360 property.
Item parameters can have a maximum of 10 custom parameters.
The post body must be smaller than 130kB.
App Measurement Protocol events sent to Google Analytics don't populate Search
audiences in Google Ads for app users.
For additional requirements of each use case, see common use cases.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-31 UTC."],[[["\u003cp\u003eThis guide explains how to send web and app stream events to a Google Analytics server using the Measurement Protocol.\u003c/p\u003e\n"],["\u003cp\u003eYou must format the request as an HTTP POST request and include your API Secret and Measurement ID in the URL.\u003c/p\u003e\n"],["\u003cp\u003eThe request body should contain client ID, optional user ID and consent settings, timestamp, and an array of events.\u003c/p\u003e\n"],["\u003cp\u003eEvents can include parameters like \u003ccode\u003eengagement_time_msec\u003c/code\u003e and \u003ccode\u003esession_id\u003c/code\u003e to display user activity in Realtime reports.\u003c/p\u003e\n"],["\u003cp\u003eThe Measurement Protocol has limitations on the number of events, parameters, and user properties allowed in a single request.\u003c/p\u003e\n"]]],["To send events to Google Analytics, use HTTP `POST` requests to `www.google-analytics.com/mp/collect`. Include `api_secret` and `measurement_id` in the URL. The request body should include `client_id`, and optionally `user_id`, `consent`, and `timestamp_micros`. Send events as an array within the `events` key. For real-time reporting, include `engagement_time_msec` and `session_id` in the event parameters. Timestamps can be set per event or at the request level. There are limitations on request size, event, and parameter counts.\n"],null,["This guide explains how you can send\n[Google Analytics Measurement Protocol](/analytics/devguides/collection/protocol/ga4) web and app stream\n[events](/analytics/devguides/collection/protocol/ga4/reference/events) to a\nGoogle Analytics server, so that you can view Measurement Protocol events in your\n[Google Analytics reports](/analytics/devguides/reporting/data/v1/basics).\n\nChoose the platform you want to see in this guide: \nFirebase gtag.js\n\nFormat the request\n\nThe Google Analytics Measurement Protocol only supports HTTP `POST` requests.\n\nTo send an event, use the following format: \n\n POST /mp/collect HTTP/1.1\n HOST: www.google-analytics.com\n Content-Type: application/json\n\n \u003cvar translate=\"no\"\u003ePAYLOAD_DATA\u003c/var\u003e\n\n| **Tip:** If you want your data to be processed in the EU, change the `HOST` in the example to `region1.google-analytics.com`.\n\nYou must provide the following in the request URL:\n\n- `api_secret`: The **API SECRET** generated in the Google Analytics UI.\n\n To create a new secret, navigate to\n **Admin** \\\u003e **Data collection and modification** \\\u003e **Data streams** \\\u003e\n **choose your stream** \\\u003e **Measurement Protocol API secrets** \\\u003e **Create**.\n\n\u003cbr /\u003e\n\n- `measurement_id`: The measurement ID associated with a stream, found in the\n Google Analytics UI under **Admin** \\\u003e **Data Streams** \\\u003e **choose your\n stream** \\\u003e **Measurement ID**.\n\n The `measurement_id` isn't your **Stream ID**.\n\nSee [query parameters](/analytics/devguides/collection/protocol/ga4/reference#payload_query_parameters) for the full reference.\n\nYou must provide the following in the request body:\n\n\u003cbr /\u003e\n\n- `client_id`: A unique identifier for a client. This is different than a Firebase `app_instance_id`. Use [gtag.js('get')](/gtagjs/reference/api#get_mp_example).\n\n\u003c!-- --\u003e\n\n- `user_id`: Optional. A unique identifier for a user. Can only contain UTF-8\n characters. See [User-ID for cross-platform analysis](https://support.google.com/analytics/answer/9213390) for more information\n about this identifier.\n\n- `consent`: Optional. Learn how to set [consent\n settings](/analytics/devguides/collection/protocol/ga4/reference#payload_consent).\n\n- `user_location`: Optional. The [geographic information](/analytics/devguides/collection/protocol/ga4/reference#payload_geo_info) for the events in\n the request.\n\n- `ip_override`: Optional. The IP address from which Google Analytics should\n derive [geographic information](/analytics/devguides/collection/protocol/ga4/reference#payload_geo_info) for the events in the request.\n\n Google Analytics ignores this field if the request also includes\n `user_location`.\n- `device`: Optional. The [device information](/analytics/devguides/collection/protocol/ga4/reference#payload_device_info) for the events in the request.\n\n\u003c!-- --\u003e\n\n- `timestamp_micros`: Optional. The Unix epoch time, in microseconds, for the\n events and user properties in the request. If not specified, [defaults to the\n time of the request](#override_timestamp).\n\n- `events`: An array of event items. You can include multiple events in one\n request.\n\n In order for user activity to display in reports like\n [Realtime](/analytics/devguides/reporting/data/v1/realtime-basics),\n `engagement_time_msec` and `session_id` must be supplied as part of the\n `params` for an `event`. The `engagement_time_msec` parameter should reflect\n the event's engagement time in milliseconds.\n\n \u003cbr /\u003e\n\n Here's an example:\n\n\u003cbr /\u003e\n\n {\n \"client_id\": \"\u003cvar translate=\"no\"\u003eCLIENT_ID\u003c/var\u003e\",\n \"events\": [\n {\n \"name\": \"campaign_details\",\n \"params\": {\n \"campaign_id\": \"google_1234\",\n \"campaign\": \"Summer_fun\",\n \"source\": \"google\",\n \"medium\": \"cpc\",\n \"term\": \"summer+travel\",\n \"content\": \"logolink\",\n \"session_id\": \"123\",\n \"engagement_time_msec\": 100\n }\n }\n ]\n }\n\nWhile `session_start` is a [reserved event\nname](/analytics/devguides/collection/protocol/ga4/reference#reserved_names),\ncreating a new `session_id` creates a new session without the need to send\n`session_start`. Understand how [sessions are\ncounted](//support.google.com/analytics/answer/9191807).\n\nTry it\n\nHere's an example you can use to send multiple events at once. This example\nsends a [`tutorial_begin`](/analytics/devguides/collection/protocol/ga4/reference/events?tech=aw_measurement_protocol#tutorial_begin) event and a\n[`join_group`](/analytics/devguides/collection/protocol/ga4/reference/events?tech=aw_measurement_protocol#join_group) event to your Google Analytics server, includes [geographic\ninformation](/analytics/devguides/collection/protocol/ga4/reference#payload_geo_info) using the `user_location` field, and includes [device information](/analytics/devguides/collection/protocol/ga4/reference#payload_device_info)\nusing the `device` field.\n\n\u003cbr /\u003e\n\n const measurementId = \"\u003cvar translate=\"no\"\u003eMEASUREMENT_ID\u003c/var\u003e\";\n const apiSecret = \"\u003cvar translate=\"no\"\u003eAPI_SECRET\u003c/var\u003e\";\n\n fetch(`https://www.google-analytics.com/mp/collect?measurement_id=${measurementId}&api_secret=${apiSecret}`, {\n method: \"POST\",\n body: JSON.stringify({\n client_id: \"\u003cvar translate=\"no\"\u003eCLIENT_ID\u003c/var\u003e\",\n events: [\n {\n name: \"tutorial_begin\",\n params: {\n \"session_id\": \"\u003cvar translate=\"no\"\u003eSESSION_ID\u003c/var\u003e\",\n \"engagement_time_msec\": 100\n }\n },\n {\n name: \"join_group\",\n params: {\n \"group_id\": \"G_12345\",\n \"session_id\": \"\u003cvar translate=\"no\"\u003eSESSION_ID\u003c/var\u003e\",\n \"engagement_time_msec\": 150\n }\n }\n ],\n user_location: {\n city: \"Mountain View\",\n region_id: \"US-CA\",\n country_id: \"US\",\n subcontinent_id: \"021\",\n continent_id: \"019\"\n },\n device: {\n category: \"mobile\",\n language: \"en\",\n screen_resolution: \"1280x2856\",\n operating_system: \"Android\",\n operating_system_version: \"14\",\n model: \"Pixel 9 Pro\",\n brand: \"Google\",\n browser: \"Chrome\",\n browser_version: \"136.0.7103.60\"\n }\n })\n });\n\nOverride timestamp\n\nThe Measurement Protocol uses the *first* timestamp it finds in the following list\nfor each event in the request:\n\n1. The `timestamp_micros` of the event.\n2. The `timestamp_micros` of the request.\n3. The time that the Measurement Protocol receives the request.\n\nThe following example sends a request-level timestamp that applies to all of the\nevents in the request. As a result, the Measurement Protocol assigns both the\n`tutorial_begin` and `join_group` events a timestamp of\n`requestUnixEpochTimeInMicros`. \n\n {\n \"timestamp_micros\": requestUnixEpochTimeInMicros,\n \"events\": [\n {\n \"name\": \"tutorial_begin\"\n },\n {\n \"name\": \"join_group\",\n \"params\": {\n \"group_id\": \"G_12345\",\n }\n }\n ]\n }\n\nThe following example sends both a request-level timestamp and an event-level\ntimestamp. As a result, the Measurement Protocol assigns the `tutorial_begin`\nevent a timestamp of `tutorialBeginUnixEpochTimeInMicros`, and the `join_group`\nevent a timestamp of `requestUnixEpochTimeInMicros`. \n\n {\n \"timestamp_micros\": requestUnixEpochTimeInMicros,\n \"events\": [\n {\n \"name\": \"tutorial_begin\",\n \"timestamp_micros\": tutorialBeginUnixEpochTimeInMicros\n },\n {\n \"name\": \"join_group\",\n \"params\": {\n \"group_id\": \"G_12345\",\n }\n }\n ]\n }\n\nLimitations\n\nThe following limitations apply to sending Measurement Protocol events to Google\nAnalytics:\n| **Note:** For information on the limitations of 360 features, see [Google Analytics\n| 360](//support.google.com/analytics/answer/11202874).\n\n- Requests can have a maximum of 25 events.\n- Events can have a maximum of 25 parameters.\n- Events can have a maximum of 25 user properties.\n- User property names must be 24 characters or fewer.\n- User property values must be 36 characters or fewer.\n- Event names must be 40 characters or fewer, can only contain alpha-numeric characters and underscores, and must start with an alphabetic character.\n- Parameter names including item parameters must be 40 characters or fewer, can only contain alpha-numeric characters and underscores, and must start with an alphabetic character.\n- Parameter values including item parameter values must be 100 characters or fewer for a standard Google Analytics property, and 500 characters or fewer for a Google Analytics 360 property.\n- Item parameters can have a maximum of 10 custom parameters.\n- The post body must be smaller than 130kB.\n- App Measurement Protocol events sent to Google Analytics don't populate Search audiences in Google Ads for app users.\n\nFor additional requirements of each use case, see [common use cases](/analytics/devguides/collection/protocol/ga4/use-cases)."]]