Microsoft Ads UTM Update: What Changes September 2, 2026

Microsoft Advertising currently applies the same UTM auto-tagging pattern to every campaign format. Audience Ads, Shopping Ads, Video, and Performance Max all arrive in Google Analytics 4 tagged the same way as keyword-triggered Search ads, which means all of them are reported under Paid Search. That changes on September 2, 2026.

From that date, Microsoft Advertising replaces its universal auto-tagging with format-specific tags. Each campaign type carries its own utm_source, utm_medium, and campaign suffix, allowing analytics platforms to route the traffic into separate channels. No action is required. The tags change automatically for every account with auto-tagging enabled.

1. What Is Actually Changing

Microsoft Advertising UTM auto-tagging is becoming format-aware. Today the platform applies one universal tagging pattern to every campaign format, which is why Audience Ads, Shopping Ads, and Performance Max all end up grouped under Paid Search in third-party analytics. From September 2, 2026, each format carries values that map to its own channel definition.

Microsoft announced the change by email to advertisers in early June 2026. The operational instruction is unambiguous: no action is required. If you use UTM auto-tagging today, updated tags are applied automatically. If you don't use auto-tagging, the update doesn't apply to you and you can disregard it.

2. The New Tag Mapping

This is the mapping Microsoft published for advertisers using Google Analytics 4.

Two of these rows work through the campaign name rather than the medium, which is worth understanding because it explains why the suffix column exists at all. GA4's Paid Shopping definition requires a paid medium and a campaign name containing a shopping term. Its Cross-network definition matches on a campaign name containing "cross-network." So the suffix Microsoft appends to your campaign value is the mechanism that triggers the classification — not the source or medium alone.

If you're on a platform other than GA4, treat this table as a reference rather than a guarantee. Microsoft notes that other analytics tools may have similar default channel definitions and advises checking with your platform representative. Adobe Analytics users in particular will want to confirm their marketing channel processing rules can interpret msads as something other than a catchall.

3. The Reporting Problem This Fixes

The universal "Paid Search" label creates a specific distortion: it averages together formats that behave nothing alike. An Audience Ad on the MSN display network is bought on a CPM basis and targeted on profile signals. A Search ad triggers on a keyword and charges per click. Their click-through rates, conversion rates, and cost per acquisition are not comparable numbers, and blending them produces a channel average that describes neither one.

The practical consequence was that you couldn't compare your Microsoft Shopping performance against your Microsoft Search performance at the analytics channel level. You had to either pivot into Microsoft's own reporting interface or layer additional manual UTM parameters on top of the auto-tagging defaults to rebuild the distinction yourself.

That gap fed directly into budget decisions. If Shopping traffic appeared to underperform inside a blended Paid Search channel, there was no way to tell whether Shopping was genuinely weaker or whether the comparison was a tagging artifact. Microsoft's stated goal for the update is exactly this: format-level insight so spend can move toward the formats actually performing.

4. What Your Reports Look Like on September 2

September 2 introduces a structural break in your historical analytics data, and it will look like a performance event if nobody is expecting it. Historical sessions are not reprocessed — everything before that date keeps its Paid Search classification, and only traffic from that date forward carries the new tags.

Here is the shape of what you'll see, none of which reflects any change in actual campaign delivery:

• Paid Search drops. Sometimes sharply, depending on your format mix. Every non-Search format leaves the channel at once.
• Display appears or jumps. Audience Ads traffic lands here on cpm.
• Paid Shopping appears. Shopping Ads move out of Paid Search into their own channel.
• Paid Video appears. Video campaigns separate out under bing_video.
• Cross-network grows. Microsoft Performance Max joins Google Performance Max in the same channel — worth knowing, since those two are now aggregated together.

The Cross-network change has a secondary effect worth noting. After September 2, GA4's Cross-network channel contains Performance Max traffic from both Google Ads and Microsoft Advertising, because Microsoft aligned its naming with the convention GA4 was built around. If you currently use Cross-network as a proxy for Google Performance Max performance, that proxy is no longer accurate from September 2 onward.

5. What to Check Before the Switch

No action is required, but four checks are worth the time.

1. Confirm whether auto-tagging is even on. In Microsoft Advertising, UTM auto-tagging is an account-level setting. If it's off, this update doesn't touch you — but you should know which state you're in rather than assuming.
2. Inventory anything hardcoded to Paid Search. Audience segments, Looker Studio filters, BigQuery queries, conversion-path analyses, budget pacing dashboards. Anything filtering on utm_source=bing or the Paid Search channel will silently lose the non-Search formats on September 2.
3. Check your own URL tracking templates. If you set utm_campaign values through tracking templates, verify how they interact with Microsoft's appended suffix. The Paid Shopping and Cross-network classifications depend on campaign name content, so a template that overwrites or reformats the campaign value could break the mapping.
4. Verify your platform's channel definitions. If you're not on GA4, confirm your tool has a Cross-network equivalent and knows what msads is. Otherwise Performance Max lands in a default bucket.

Then, in the first week of September, spend ten minutes in Traffic acquisition with the primary dimension set to Session source / medium. You should see msads / cpm, msads / cpc, and bing_video / cpc appearing for the first time. If any Microsoft traffic is landing in Unassigned, that's your signal that a value isn't matching a channel definition and needs a custom channel group to catch it.

6. Where Auto-Tagging Ends and Yours Begins

Auto-tagging covers one platform. Microsoft Advertising is fixing its own tags on September 2, and Google Ads has handled its own through gclid for years — but that is where the automation stops. Email, organic social, affiliates, sponsorships, newsletters, partner placements, QR codes, and newer ad platforms with no auto-tagging at all are still tagged by hand, and those hand-built links are where GA4 attribution usually breaks.

The failure modes are the same ones this update is correcting, except nobody is going to fix them for you:

• A medium that matches no channel definition. utm_medium=ads or email-blast instead of cpc or email sends the session to Unassigned.
• Inconsistent casing or spelling. Facebook in one campaign and facebook in another creates two dimension values in GA4 that can never be merged.
• Missing parameters. A utm_source with no utm_medium is worse than no tagging at all, because GA4 stops falling back to the referrer.
• No preview before launch. Most teams find out a link was tagged wrong when they open GA4 a week later, by which point the sessions are already misfiled.

UTM Buddy is a UTM generator and UTM builder for GA4 built to catch those problems before a link goes out the door:

• GA4 attribution preview — see the exact default channel group a URL will land in before you publish it.
• Spell check and validation — flags misspellings and casing drift that would create permanent duplicate dimension values.
• Saved parameter templates — lock source and medium per platform so every campaign inherits the same convention.
• Bulk URL builder — generate dozens of correctly structured campaign URLs from one template.
• Team workspaces — hold naming conventions steady across brands, clients, and contributors.
• All nine UTM parameters — including utm_id, utm_source_platform, utm_marketing_tactic, and utm_creative_format.

Newer ad platforms are the clearest case for a real UTM builder, because several ship with no auto-tagging whatsoever. OpenAI Ads is one of them — every campaign parameter has to be added manually, or the traffic reports as organic AI referrals rather than paid.

Frequently Asked Questions

Starting September 2, 2026, Microsoft Advertising replaces its universal UTM auto-tagging with format-specific tags. Search, Audience Ads, Shopping Ads, Video, and Performance Max will each carry their own utm_source, utm_medium, and campaign suffix values so analytics platforms can report them as separate channels instead of grouping everything under Paid Search.

No action is required. If you use UTM auto-tagging today, the updated tags are applied automatically. If you do not use UTM auto-tagging, the update does not affect you. The one thing worth doing is adding an annotation on September 2 in your analytics tool so the resulting shift in channel composition is not misread as a performance change.

Historical data is not reprocessed. Sessions before September 2, 2026 keep their original Paid Search classification, and only traffic from that date forward carries the new format-specific tags. Any report comparing periods that span the change will show a structural break rather than a real change in campaign delivery.

Because Audience Ads, Shopping Ads, Video, and Performance Max traffic is being reclassified out of Paid Search into Display, Paid Shopping, Paid Video, and Cross-network. Total Microsoft Advertising traffic does not change. The Paid Search line drops only because traffic that never belonged there is finally being reported under its own format.

Performance Max traffic will fall into a default or unknown bucket. GA4 has a Cross-network channel definition, but platforms like Adobe Analytics may need their marketing channel processing rules updated to recognize the new values. Check your platform's channel rules against the new tag mapping before September 2.

Microsoft appends a campaign suffix such as shopping or cross-network to the campaign value for certain formats. If you set your own utm_campaign parameters through URL tracking templates, verify how those interact with the auto-tagged suffix after September 2, since GA4's Paid Shopping and Cross-network definitions match on campaign name content.

Wrapping Up

The September 2 update improves Microsoft Advertising measurement without requiring any configuration work. Format-level reporting becomes available automatically for every account using UTM auto-tagging.

The main risk is interpretive rather than technical. A channel mix that shifts on a single date resembles a performance change in a trend chart, and anyone reviewing those charts later in the year is unlikely to connect it to a tagging update. Annotate September 2, 2026 in your reporting tools, inform whoever owns channel reporting, and review any segment, filter, or dashboard hardcoded to Paid Search before the traffic is reclassified.