Microsoft Advertising this month emailed advertisers notifying them that it will update UTM auto-tagging starting September 2, 2026, changing how campaign traffic from the platform is categorized inside third-party analytics tools such as Google Analytics 4. No action is required from advertisers currently using UTM auto-tagging, as the updated tags will be applied automatically.

The change addresses a long-standing measurement gap. According to Microsoft, the current system applies a universal UTM tagging approach across all campaign formats, which causes campaign types including Audience Ads, Shopping Ads, and Performance Max to be grouped together under a single "Paid Search" label in analytics reports. That grouping has made it difficult to understand which specific formats are driving traffic, and budget decisions have often been made on incomplete channel-level data as a result.

What is actually changing on September 2

The core of the update is that UTM auto-tagging will become format-aware. Each campaign type will carry its own combination of utm_source, utm_medium, and campaign suffix values, making it possible for analytics platforms to route the traffic into distinct reporting channels.

According to Microsoft, the updated tag mapping will work as follows for advertisers using Google Analytics 4:

Search campaigns will use utm_source=bing and utm_medium=cpc with no campaign suffix, which maps to the "Paid Search" channel definition in GA4.

Audience Ads will use utm_source=msads and utm_medium=cpm with no campaign suffix, routing traffic into the "Display" channel.

Shopping Ads will carry utm_source=msads and utm_medium=cpc with a campaign suffix of "shopping", landing under the "Paid Shopping" channel definition in GA4.

Video campaigns will use utm_source=bing_video and utm_medium=cpc, mapping to "Paid Video".

Performance Max will use utm_source=msads and utm_medium=crossnetwork with a "cross-network" campaign suffix, which corresponds to the "Cross-network" channel definition - or "Default/Unknown" if the analytics platform does not have that channel defined.

The "Default/Unknown" outcome for Performance Max deserves attention. GA4 introduced the Cross-network channel definition to accommodate automated campaign types that serve across multiple placements, but not every analytics configuration includes it. Advertisers relying on platforms other than GA4 should verify whether their tool's default channel definitions can interpret the new tag values correctly. Microsoft's email advises users of other analytics platforms to contact their platform representative for guidance.

The problem this solves

The current "Paid Search" catch-all creates a specific distortion in channel-level reporting. When Audience Ads and Shopping Ads appear under the same label as keyword-triggered Search campaigns, the aggregate metrics - click-through rates, conversion rates, cost per acquisition - reflect a blend of very different audience behaviors and inventory types. An Audience Ad served on the MSN display network operates on a CPM basis and targets users based on profile signals; a Search Ad triggers on a keyword and charges per click. Lumping both under "Paid Search" inside GA4 produces averages that do not represent either format accurately.

The measurement debate around hardcoded UTMs and dynamic tracking parameters in Google Ads has made clear how much analytics accuracy depends on precise tagging infrastructure. The parallel problem in Microsoft Advertising has received less attention, partly because the universal tagging was invisible to anyone not cross-referencing the raw parameter values.

Context: Performance Max and the attribution challenge

The update comes as Microsoft Advertising has steadily expanded Performance Max into a central campaign type. Microsoft launched Performance Max campaigns globally in March 2024, and the format has since received a sequence of significant capability updates.

In January 2026, Microsoft expanded search theme limits to 50 per Performance Max campaign, giving advertisers more signal input for automated targeting. That same month, Microsoft added customer acquisition goals and URL tracking templates at the asset group level, increasing the measurement infrastructure available within the campaign type itself.

More recently, in May 2026, Microsoft expanded Performance Max placement reporting to include conversions, clicks, and spend at the website URL level, a granularity that the company described as exceeding what most industry alternatives currently provide. That development and the current UTM update point in the same direction: Microsoft is investing in making automated campaign types more auditable.

The challenge is that automation and measurement have been moving at different speeds. Performance Max aggregates Search, Audience, Shopping, and other inventory into a single campaign shell, while analytics platforms have historically received only a generic signal about where that traffic came from. The September 2 tagging change brings the analytics signal closer to the campaign architecture that advertisers are actually managing.

How attribution was affected under the old system

To understand the significance of the change, it helps to trace what was happening to campaign traffic in analytics before this update. When a user clicked a Shopping Ad on Bing, the traffic arrived at the advertiser's site with UTM parameters that tagged it as Paid Search. Inside GA4, that session was attributed to the Paid Search channel - the same channel receiving traffic from keyword-triggered text ads. Revenue and conversion events generated by that session were then credited to Paid Search.

An advertiser comparing the performance of their Microsoft Shopping campaigns against their Microsoft Search campaigns could not do so at the analytics channel level. They would need to use Microsoft's own reporting interface, or build custom segments using additional UTM parameters layered on top of the auto-tagging defaults. The limitation affected budget decisions: if Shopping traffic appeared to underperform Paid Search in GA4, it was impossible to tell whether the problem was Shopping performance or a tagging artifact.

The broader difficulty of session attribution in GA4 is well documented. A December 2025 LinkedIn poll involving 624 professionals found that 59% answered a question about GA4 session attribution mechanics incorrectly. Adding another opaque tagging layer on top of that complexity compounded the diagnostic challenge.

What advertisers using non-GA4 platforms should check

Microsoft's communication focuses on GA4, but the company explicitly acknowledges that other analytics platforms may have default channel definitions similar to GA4's structure. The practical implication is that the mapping provided in the email serves as a reference - advertisers should compare the incoming utm_source and utm_medium values against their platform's channel grouping rules.

Advertisers using Adobe Analytics, for example, will need to verify whether their processing rules or marketing channel definitions will correctly classify utm_source=msads combined with utm_medium=crossnetwork as a distinct channel, or whether it will fall into a catchall bucket. The same applies to any platform with custom channel logic that was built around the assumption that all Microsoft Advertising traffic arrives as Paid Search.

The "shopping" campaign suffix used for Shopping Ads is also worth noting. This is a campaign-level parameter appended to the URL, not the utm_campaign value set by the advertiser. Advertisers who have their own utm_campaignparameters set through URL templates may need to check how these interact with the platform's auto-tagging behavior after September 2.

No action required - but verification is worth doing

Microsoft's message is unambiguous about the operational requirement: nothing needs to be done. Advertisers using UTM auto-tagging will have the updated tags applied automatically on September 2. Advertisers not using UTM auto-tagging are instructed to disregard the update.

That said, September 2 will introduce a structural break in historical analytics data for most Microsoft Advertising accounts. Reports that compare channel performance across time periods spanning the transition date will show a shift in channel composition that is attributable to the tagging change rather than actual campaign performance changes. Audience Ads traffic that was previously reported as Paid Search will appear in Display from September 2 onward. Performance Max traffic that appeared as Paid Search will shift to Cross-network.

Advertisers maintaining historical benchmarks in GA4 or other platforms should annotate this date in their analytics tools to avoid misinterpreting the channel-level trend lines. The shift will look like Paid Search traffic declining and Display, Paid Shopping, Paid Video, and Cross-network traffic appearing from that date - all without any corresponding change in actual campaign delivery.

The question of how analytics data informs budget allocation is directly relevant here. GA4 has been building cross-channel budgeting infrastructure that depends on accurate medium-level attribution. If Microsoft Advertising traffic was misclassified into Paid Search before September 2, any cross-channel models built on that data will have factored in a distorted input.

Broader measurement context

The UTM tagging landscape has become more complex over the past two years as more traffic sources have adopted parameter-based attribution. ChatGPT expanded UTM parameter coverage on links in June 2025, addressing a gap where AI-generated referrals were arriving as direct traffic. Google introduced additional UTM parameters including utm_source_platform, utm_creative_format, and utm_marketing_tactic to support more granular campaign classification within its own ecosystem.

Microsoft's update follows that direction. The utm_medium=crossnetwork value used for Performance Max is directly analogous to the "cross-network" medium that Google Ads uses for its own Performance Max campaigns, where Google similarly serves ads across Search, YouTube, Display, and Shopping within a single campaign structure. That alignment in naming is not accidental - it allows GA4's channel definitions, which were built with Google's own campaign types in mind, to classify Microsoft's Performance Max traffic in the same grouping as Google's equivalent campaign type.

This matters for advertisers running campaigns on both platforms simultaneously. After September 2, cross-platform attribution reports in GA4 will show Microsoft Advertising Performance Max traffic and Google Ads Performance Max traffic in the same Cross-network channel. Whether that aggregation is useful or obscuring depends on the reporting question being asked, but it represents a closer alignment between how the two platforms present themselves to third-party analytics tools than existed before.

Universal Event Tracking, Microsoft's own conversion tracking infrastructure, remains separate from UTM-based analytics and is not affected by this change. Advertisers using UET for conversion optimization within the Microsoft Advertising platform will see no change to how conversion data is recorded or used for bidding.

Timeline

Summary

Who: Microsoft Advertising, the advertising platform operated by Microsoft, sent a notification to advertisers using UTM auto-tagging.

What: Starting September 2, 2026, Microsoft Advertising will apply format-specific UTM tags automatically, replacing the current universal tagging system. Each campaign format - Search, Audience Ads, Shopping Ads, Video, and Performance Max - will carry distinct utm_source, utm_medium, and campaign suffix values that map to separate channel groups in GA4 and compatible analytics platforms.

When: The announcement was made on June 5, 2026. The change takes effect September 2, 2026.

Where: The change affects all Microsoft Advertising accounts that have UTM auto-tagging enabled. It is visible inside third-party analytics platforms such as Google Analytics 4, Adobe Analytics, and any platform that parses UTM parameters to assign channel definitions.

Why: The current system groups Audience Ads, Shopping Ads, and Performance Max under a single "Paid Search" label in analytics, obscuring format-level performance differences and complicating budget decisions that depend on accurate channel attribution. The update aligns Microsoft Advertising's analytics signal with the actual campaign architecture advertisers are managing.