Google has quietly moved the GA4 Measurement Protocol into maintenance mode, according to a notice that appeared on its official developer documentation page. No sunset date has been announced and no shutdown is imminent, but the language is clear: no future enhancements are planned. Google is now pointing server-side event collection toward the Data Manager API, a newer unified ingestion layer that launched in December 2025 with a broader scope across Google's advertising ecosystem.

What the maintenance mode notice says

The official Google Analytics developer documentation now carries a banner that reads: "The Measurement protocol is now in maintenance mode. No future enhancements are planned. Upgrade to the Data Manager API to future-proof your integration." The notice sits at the top of the GA4 Measurement Protocol reference page at developers.google.com, the canonical location that analytics engineers and developers consult when building or maintaining integrations.

No specific date has been publicly associated with the status change. Digital marketing consultant Vlad Simion, who posted about the development on LinkedIn, described the shift as Google quietly moving the GA4 Measurement Protocol into "maintenance mode." Simion noted that "no sunset date has been announced, so this is not a shutdown notice" and characterized the situation plainly: "the message is pretty clear: no future enhancements are planned."

Analytics consultant Nichelle Halstrom, writing separately on LinkedIn, described the move as "likely the first step in getting early adopters to migrate to the Data Manager API." Halstrom noted that while no official deprecation announcement has been made, Google's direction is evident.

What the GA4 Measurement Protocol is and who uses it

The GA4 Measurement Protocol is a set of rules allowing developers and engineers to send raw event data directly from a client or server to a GA4 property via HTTP requests. It was designed specifically to augment - not replace - automatic data collection that flows through gtag.js, Google Tag Manager, and the Firebase SDK. According to Google's documentation, the protocol is intended for use cases such as tying online behavior to offline interactions, measuring server-side events, sending data from devices without automatic collection like kiosks or point-of-sale systems, and recording interactions that fall outside the standard user-interaction flow.

Users of the protocol are required to use it alongside standard tagging implementations. The documentation states clearly that gtag, Tag Manager, or Google Analytics for Firebase must also be in place. Without those, only partial reporting is available because the Measurement Protocol alone does not establish complete session context.

The protocol operates through a single HTTP POST endpoint. Each request carries an API secret - a credential generated inside the GA4 property interface and passed as a query parameter - along with a measurement ID and a JSON payload containing one or more events. The events follow GA4's standard schema, meaning the same event names and parameters used in client-side collection apply in Measurement Protocol calls as well. The design makes the protocol relatively accessible for developers already familiar with GA4's event model, requiring no additional SDK installation on the server side.

Why this matters for paid media and analytics teams

The Measurement Protocol has served as the backbone for a range of server-side use cases that marketing and analytics teams rely on daily. Offline conversion ingestion - particularly sending purchase completions, lead closings, and CRM-qualified events back into GA4 after the fact - has been a common implementation pattern. Ecommerce teams that process server-side transactions have used it to ensure order data reaches GA4 without depending on browser-side JavaScript executing reliably. Developers building integrations for kiosks, connected devices, or call center systems have leaned on it as a straightforward HTTP-based path into Google Analytics.

With the protocol now in a holding pattern, those teams are looking at a different architectural path. The question is not whether existing implementations will break tomorrow - they will not. The question is whether investing further in Measurement Protocol-based infrastructure is prudent when the upstream product is no longer receiving development attention.

The Data Manager API as the designated alternative

According to Google, the Data Manager API is the forward path for server-side event collection. The contrast between the two products is technical and architectural rather than merely administrative. Vlad Simion outlined the differences: the Data Manager API provides a "unified data model across Google advertising products," includes "encryption support for user data," supports sending "one event to multiple destinations in a single request," and carries "no API secret to manage."

Nichelle Halstrom framed the same differences from a paid media perspective: encryption support was not available in the Measurement Protocol; the Data Manager API can send a single event - such as a purchase - to both GA4 and Google Ads simultaneously in one request; it uses a unified data model and schema across all platforms; and it removes the API secret requirement entirely.

The ability to route a single server-side event to multiple Google destinations in one call is significant for teams currently managing separate pipelines. As PPC Land has documented, many advertisers have historically maintained distinct integrations for Google Ads offline conversions, GA4 event ingestion, and DV360 audience uploads - essentially three separate data pipes carrying overlapping information to different endpoints. The Data Manager API consolidates those into a single request.

The Data Manager API was formally launched on December 9, 2025, with eleven integration partners at launch: AdSwerve, Customerlabs, Data Hash, Fifty Five, Hightouch, Jellyfish, Lytics, Tealium, Treasure Data, and Zapier, among others. It operates via both REST and gRPC protocols. Authentication uses OAuth 2.0 with the datamanager scope, which is distinct from the scopes used by the Google Ads API. Each Google Cloud project is limited to 100,000 requests per day and 300 requests per minute, with individual requests supporting up to 10,000 audience members or 2,000 conversion events and up to 10 user identifiers per record.

Encryption, schema consistency, and confidential matching

One of the more concrete architectural differences is the Data Manager API's support for encrypted data uploads. The API accepts data encrypted using XChaCha20-Poly1305 algorithms. Wrapped data encryption keys can be secured by either Google Cloud Platform or Amazon Web Services key management systems - a detail relevant for organizations whose infrastructure does not sit entirely within Google Cloud. The Measurement Protocol had no equivalent capability; data passed to GA4 via HTTP was unencrypted at the application layer.

The unified schema is a second meaningful distinction. A field like "transaction ID" could carry subtly different meanings depending on which Google product pipeline received it - a fragmentation issue that the Data Manager API addresses by enforcing one schema across Google Ads, Google Marketing Platform, and Google Analytics. PPC Land's coverage of the April 2026 Ads DevCast episode on the topic noted that Melissa Ng, the product manager for Data Manager API at Google, described this consistency as making the addition of new use cases significantly faster: a team already sending offline conversion data through the API can add support for offline conversion adjustments or enhanced conversions for web without rebuilding the integration, because the endpoint and schema stay the same.

Treasure Data, one of the launch partners, reported an 80 percent reduction in engineering effort after consolidating onto the Data Manager API from separate integrations for Google Ads Customer Match, Google Analytics audiences, and DV360 audience management.

Access restrictions remain a practical concern

One limiting factor for teams looking to migrate immediately is that the Data Manager API is not fully open. As Jorg van de Ven noted in the LinkedIn discussion thread on Vlad Simion's post, "the alternative, the Data Manager, is still on an allow list. Meaning you have to request access in order to use it. So, if you need a solution today, measurement protocol seems your best bet... Or wait until the Data Manager becomes available."

This access constraint means that while the Measurement Protocol is no longer receiving investment, it remains the operationally available path for some teams in the near term. The migration from Measurement Protocol to Data Manager API is not a decision teams can universally act on immediately - it depends on whether they have been granted API access and whether they have completed the prerequisite setup of a Google Cloud project with the Data Manager API enabled.

A broader pattern of Google consolidating data pathways

The Measurement Protocol status change is one piece inside a larger pattern that has been unfolding since late 2025. Google formally blocked new offline conversion imports via the Google Ads API from June 15, 2026, requiring any developer not already using the path to adopt the Data Manager API instead. Before that, Google forced Customer Match uploads to migrate to the Data Manager API by April 1, 2026, ending support for the older OfflineUserDataJobService and UserDataService routes in the Google Ads API.

The Data Manager API itself has continued to expand. Version 1.6 of the API, released on May 7, 2026, introduced native support for uploading store sales conversions to Google Ads and expanded event ingestion for Google Analytics across both web and app data streams. This was the most comprehensive feature addition to the API since it reached general availability in October 2025.

On the Google Tag Manager side, a broader merge of GTM and Google Tag is underway, adding another dimension to how Google is restructuring its measurement and tagging infrastructure. Google Analytics itself has also been reconfigured around user-provided data, with the November 2025 update changing how demographics and interests data are sourced.

Google Analytics additionally collapsed enhanced conversions for web and for leads into a single toggle in April 2026, accepting user-provided data simultaneously from website tags, Data Manager, and API connections - removing the previous requirement to select a single implementation method. The Measurement Protocol's move to maintenance mode fits into this progression: legacy paths are being deprecated or frozen while the Data Manager API absorbs their functionality under a unified, privacy-aligned architecture.

What this means for measurement architecture decisions

For marketing technology teams evaluating their current server-side measurement stack, the maintenance mode status of the Measurement Protocol is a signal rather than a deadline. Existing implementations will continue to function. Events sent via HTTP to the GA4 collection endpoint will still be processed and appear in reports. The behavioral change, at this stage, is the absence of future development - no new event types, no schema expansions, no additional destination support, and no new privacy features.

The Data Manager API, by contrast, is actively receiving development resources. The progression from launch in December 2025 through general availability in October 2025, the version 1.6 release in May 2026 adding store sales and expanded Analytics event support, and the ongoing enforcement of migration deadlines for Customer Match and offline conversions all point to where Google's engineering investment is concentrated.

For teams running offline conversion pipelines, ecommerce purchase ingestion, or CRM event matching via the Measurement Protocol, the architecture question is now a matter of timing. The technical migration requires establishing a Google Cloud project, configuring OAuth 2.0 credentials with the datamanager scope, mapping existing event payloads to the Data Manager API schema, and - for teams targeting GA4 specifically - granting the operating account access to the Analytics property. The diagnostic tooling inside GA4 (Realtime report and DebugView) remains available for verification after migration.

The access allowlist is the primary practical brake on immediate migration for some organizations. Teams that have not yet applied for Data Manager API access and need an active solution in the near term will continue to rely on the Measurement Protocol until access is granted.

Timeline

Summary

Who: Google, analytics engineers, paid media teams, and marketing technology developers who use the GA4 Measurement Protocol to send server-side or offline events directly to Google Analytics via HTTP requests.

What: Google has placed the GA4 Measurement Protocol in maintenance mode. According to the official developer documentation, no future enhancements are planned. Google now points developers toward the Data Manager API for server-side event collection, a newer interface that supports a unified data model, encryption via XChaCha20-Poly1305, multi-destination event routing in a single request, and no API secret requirement.

When: No specific date for the maintenance mode designation has been publicly announced by Google, but the notice on the developer documentation page was confirmed in June 2026. The Data Manager API, positioned as the replacement, launched on December 9, 2025, and reached general availability in October 2025.

Where: The maintenance mode designation appears on Google's official GA4 Measurement Protocol developer documentation at developers.google.com. The Data Manager API is accessible as a server-side API via REST and gRPC, requiring a Google Cloud project with the Data Manager API enabled and OAuth 2.0 credentials with the datamanager scope.

Why: The maintenance mode status reflects a broader architectural consolidation at Google, shifting server-side data ingestion from product-specific APIs - including the Measurement Protocol for GA4 and the Google Ads API for offline conversions and Customer Match - into the Data Manager API as a single unified ingestion layer across Google Ads, Google Analytics, and Display and Video 360. The consolidation aligns with privacy requirements including encryption support and consent fields tied to Digital Markets Act obligations, capabilities the Measurement Protocol did not offer.