GA4 goes quiet, Microsoft rewires UTMs, and Google redraws ad borders
GA4 Measurement Protocol enters maintenance mode as Microsoft Advertising fixes UTM tagging and bans vanish for crypto display ads across all markets.
A quiet notice appeared on Google’s developer documentation this week, and most practitioners who saw it paused. The GA4 Measurement Protocol - the HTTP-based pipeline that analytics engineers and paid media teams have relied on for server-side event collection since the Universal Analytics migration - has been placed in maintenance mode. No shutdown date has been announced. No features will be added. The banner on the canonical reference page at developers.google.com reads plainly: “Upgrade to the Data Manager API to future-proof your integration.”
The significance is technical, but the implications reach well beyond engineering teams.
What the GA4 Measurement Protocol freeze means in practice
The Measurement Protocol was never a standalone product. It was designed to run alongside gtag.js, Google Tag Manager, or the Firebase SDK - filling the gaps that browser-based collection could not cover. Server-side purchase completions, offline conversion ingestion from CRM systems, kiosk and point-of-sale events, call center integrations: these are the use cases the protocol served. Teams running ecommerce operations, in particular, have leaned on it to ensure transaction data reaches GA4 without depending on client-side JavaScript executing correctly in every browser environment.
The technical architecture is straightforward: an HTTP POST to a single endpoint, carrying an API secret as a query parameter along with a measurement ID and a JSON payload of one or more events. The events follow GA4’s standard schema, making the protocol accessible to any developer already familiar with GA4’s event model - no additional SDK required on the server side. That simplicity has been part of its appeal.
What changes now is trajectory. The protocol still works. Existing implementations will not break on any specific date. What they will not receive is any expansion of functionality - no new event types, no updated parameters, no adaptation to whatever measurement requirements emerge as privacy regulations tighten or attribution models evolve. Digital marketing consultant Vlad Simion, writing on LinkedIn on June 5, 2026, described the development as Google “quietly moving the GA4 Measurement Protocol into maintenance mode” and characterized the situation with precision: the message is clear that no future enhancements are planned, even though no sunset date has been declared. Analytics consultant Nichelle Halstrom, writing separately, described it as “likely the first step in getting early adopters to migrate to the Data Manager API.”
The designated replacement, the Data Manager API, launched in December 2025. It provides a unified data ingestion layer across Google’s advertising and analytics ecosystem rather than GA4 alone, and it covers a broader set of data types including first-party signals that feed into ad systems such as Customer Match. The architectural difference is not merely administrative: the Measurement Protocol was GA4-specific, while the Data Manager API is positioned as cross-product infrastructure. For teams already running server-side tagging through Google Cloud or a CAPI provider, the migration path exists. For smaller operations where the Measurement Protocol was chosen precisely because it required nothing more than an HTTP request and a text editor, the path is considerably steeper.
Microsoft fixes a measurement problem no one talked about loudly
The same week brought a different kind of measurement development, this one from Microsoft. The company emailed advertisers in early June to notify them that UTM auto-tagging across the Microsoft Advertising platform will change on September 2, 2026, and the change addresses something that has quietly distorted channel-level reporting for years.
The current system applies a single universal UTM configuration to all Microsoft Advertising campaign types. Every format - Search, Audience Ads, Shopping, Performance Max, Video - arrives in Google Analytics 4 carrying parameters that route it into the “Paid Search” channel. An Audience Ad served to an MSN reader on a CPM basis looks identical in GA4 to a keyword-triggered search click. The averages produced by that combined reporting - click-through rates, conversion rates, cost per acquisition - reflect a blend of inventory types that behave in fundamentally different ways.
From September 2, the auto-tagging will become format-aware. Search campaigns will carry utm_source=bing and utm_medium=cpc, routing to GA4’s “Paid Search” channel definition as before. Audience Ads will shift to utm_source=msadsand utm_medium=cpm, landing in “Display.” Shopping Ads will use utm_source=msads and utm_medium=cpc with a “shopping” campaign suffix, mapping to “Paid Shopping.” Video campaigns will appear under utm_source=bing_video and utm_medium=cpc in “Paid Video.” Performance Max will carry utm_source=msads and utm_medium=crossnetwork with a “cross-network” campaign suffix.
That last point carries a practical caveat. GA4 introduced the Cross-network channel definition to accommodate multi-placement automated campaigns, but not every analytics configuration includes it. On platforms that do not recognize the new parameter combination, Performance Max traffic will fall into “Default/Unknown” - a catch-all that is arguably less informative than “Paid Search.” Microsoft’s email advises advertisers on other analytics platforms to contact their platform representative before September to verify compatibility.
No action is required from advertisers using UTM auto-tagging. The updated tags apply automatically. Advertisers who have built custom channel groupings in GA4 or hardcoded UTM parameters on specific campaigns will need to review those configurations before the September cutoff. The change arrives as Microsoft has also been expanding Performance Max placement reporting to include conversions, clicks, and spend at the URL level - a direction that suggests the platform is investing broadly in making automated campaign formats more measurable and auditable.
Microsoft opens display inventory to crypto exchanges, four years after search
A policy boundary that Microsoft had held since 2022 also moved this week. According to the May 2026 Pilot Program Policies update, cryptocurrency exchanges are now permitted to advertise across the Microsoft Audience Network in all markets where Microsoft accepts cryptocurrency advertising. The restriction that confined crypto exchange campaigns strictly to search inventory - in place since Microsoft first opened to the sector in May 2022 - has been lifted.
The Microsoft Audience Network serves display and native placements across MSN, Microsoft Start, Outlook.com, and Microsoft Edge, as well as third-party publisher inventory sourced programmatically. Unlike search campaigns, which reach users at the moment of a declared query, Audience Network placements operate on behavioral and interest-based targeting signals derived from Microsoft’s user graph. For cryptocurrency exchanges, the distinction matters. Search captures existing intent; audience-based inventory reaches potential customers earlier in the decision cycle, in content environments that carry contextual relevance - financial news pages on MSN, for instance, or Outlook inboxes belonging to users profiled as financially active.
The geographic expansion that preceded this policy change puts the display opening in context. Since 2022, Microsoft had been extending search eligibility for crypto exchanges market by market. In January 2026 alone, 27 European markets were added to the search list, including Germany, France, the Netherlands, Spain, Italy, and the United Kingdom. Before that, India and Japan joined in April 2025. Canada, New Zealand, and Switzerland gained search access in December 2024. The May 2026 Audience Ads update caps that sequence by removing the display prohibition globally, rather than expanding by territory.
Advertisers must still comply with all applicable cryptocurrency policies, and the change sits within the Pilot Program framework, which means it remains subject to revision.
Google’s Search profiles launch with an uneven gate
On June 6, 2026, Ibrahim Badr, Product Manager for Search, confirmed via Google’s official blog that Search profiles are formally live in the United States. The feature gives publishers and creators a claimable page inside Google Search and Discover - a cover image, a bio, links to social platforms, and aggregated content that syncs from connected accounts within 24 to 48 hours. Publishers can pin up to 8 posts from the past 365 days as featured content.
The stated eligibility threshold is 100,000 followers on at least one major platform. But Damien Andell, co-founder of 1492.vision, a research group focused on Google Discover, had already surfaced cases on June 5 of creators holding active Search profiles without meeting that threshold on any individual platform. One example, the account @docs_sports_picks, showed 74,500 YouTube subscribers, 13,400 X followers, 2,300 Instagram followers, and 1,900 Facebook followers - a total of 93,100 across platforms, none of which individually crossed the 100,000 threshold. A second case, the Lose It! app, held 63,000 Instagram followers and 21,500 on X. Both were active private beta participants whose profiles predated the official public requirements.
The discrepancy does not appear to be a policy error; it reflects the gap between beta access granted under earlier criteria and the thresholds applied to the public rollout. What it illustrates is the practical complexity of a feature that aggregates social signals across platforms to construct a credibility gate. A creator with 95,000 followers distributed across six accounts does not qualify under the stated rules, while a creator with 100,001 on a single platform does. Whether that logic holds up under scrutiny as the rollout widens is an open question.
The Search profiles development is not unrelated to the broader measurement story. As Google builds out AI Mode, AI Overviews, and Gemini app integrations, the surfaces where brands and publishers appear are multiplying - and so is the need to track visibility across them. Google also announced on May 27, 2026 the introduction of AI performance insights in Merchant Center, a reporting feature showing retailers their share of voice across AI Mode, AI Overviews, and the Gemini app. The rollout targets five markets - the United States, Canada, Australia, India, and New Zealand - with no precise timeline given for individual market access.
Ohio shuts the door on prediction market ads
One further policy shift arrived quietly. Effective June 2, 2026, Google Ads removed Ohio from the list of US states where prediction market advertising is permitted. The update to Google’s Advertising Policies Help Center states simply that “advertising of prediction markets and related products in Ohio is prohibited effective June 2, 2026.” Ohio joins Nevada on the exclusion list; the rest of eligible US states remain open to the category, provided advertisers hold certification from Google and are either a CFTC-designated Designated Contract Market or an NFA-authorized brokerage.
The removal reflects an active legal dispute between Ohio gambling regulators and CFTC-regulated prediction market exchanges over jurisdiction. Ohio state authorities have taken the position that event-contract markets constitute gambling under state law, placing them in conflict with the federal CFTC’s position that these products fall under commodity futures regulation. Google’s policy change does not resolve that dispute but removes the platform from its path.
Also noted
June 6, 2026 - Meta activated scam pop-up alerts and expanded player protections for the FIFA World Cup 2026, using Visa transaction intelligence to help dismantle fake gambling sites targeting fans. PPC Land
June 6, 2026 - Brave launched Brave Origin, a $59.99 one-time-fee browser variant that removes Leo AI, Rewards, VPN, and Tor integration while preserving Brave Shields on desktop and Android. PPC Land
June 6, 2026 - AdPlayer.Pro reported reaching 551 million daily ad requests and a peak of 10,000 requests per second, while adding vertical video format support and Interstitial Video Ads 2.0 across outstream placements. PPC Land
June 6, 2026 - Google Demand Gen and Discovery campaign clarifications issued on June 3 outlined how sensitive interest categories and restricted targeting are handled in personalized advertising. PPC Land
June 6, 2026 - YouTube froze ad revenue for Bernth’s 170,000-subscriber guitar channel after an address verification letter failed to arrive, illustrating the single-platform income risk faced by creators dependent on AdSense. PPC Land