Use the Data Manager API instead of the Measurement Protocol

Google has moved the Measurement Protocol into maintenance mode. No new features are planned for it. If you send server-side events to GA4 this way, nothing breaks today. But your integration will not improve from here.

The replacement is the Data Manager API. 

Here is what changes and how to move across.

What do you gain by upgrading?

1. The Data Manager API uses one unified data model across all Google advertising products. The Measurement Protocol is tied to Google Analytics alone.
2. The Data Manager API supports Encryption. The Measurement Protocol does not.
3. One Data Manager API request can send events to multiple destinations. The Measurement Protocol sends to a single data stream per request.
4. The Data Manager API does not need an API secret. The Measurement Protocol requires it.

The prerequisites.

Before you send anything, you need a project, credentials and account access.

Check the prerequisites:

1. A Google Cloud project. Both new and existing work.
2. A Google Account with the serviceusage.services.enable permission. Both the Owner and Service Usage Admin roles include it.
3. The Google Cloud CLI is installed.

Then enable the Data Manager API in your Google Cloud project.

Next, authenticate. 

You can use a user account or a service account. 

The user account route uses Application Default Credentials, so your code automatically finds the credentials. 

The steps are:

1. Configure the Google Auth Platform branding settings for your project.
2. Add the Data Manager API scope under Data Access, then set the publishing status and user type under Audience. The scope is sensitive, so any app that obtains user credentials for it must pass Google OAuth verification.
3. Create a Desktop OAuth2 client and download the client configuration.
4. Run gcloud auth application-default login with the datamanager and cloud-platform scopes, pointing at the client JSON file.
5. Confirm it worked with gcloud auth application-default print-access-token. A successful run prints an access token.

Service accounts follow a similar path but use impersonation rather than keys, which is the safer option for unattended jobs.

Finally, grant access to the destination. For GA4, add the email of the operating account to your Google Analytics property.

With access in place, the migration itself is short.

1. Install a client library.
2. Convert your existing requests using the field mappings reference.
3. Send your events to your GA4 property through the Data Manager API.
4. Verify the results. Use the diagnostics tool, or check the Realtime report and DebugView inside GA4.

The bigger reason to move.

The Data Manager API lets you send audience and conversion data to multiple Google advertising products in a single call. It also supports confidential matching and encryption.

That is the real shift. You stop maintaining a Google Analytics-only pipe and start running one feed into the wider Google advertising stack.

If you collect server-side data, plan the upgrade now while the old path still works. Migrations are easier before a deadline forces them.

Further reading:

1. Upgrade from Measurement Protocol to the Data Manager API.
2. Here's how to set up access to the Data Manager API with an SDK or REST.
3. Use the mappings in the tables to map a Measurement Protocol data collection request (/mp/collect) to its IngestEventsRequest equivalent in the Data Manager API.
4. Work through this guide to get familiar with the process of sending events with the Data Manager API.