Microsoft Ads UTM Auto-Tagging September 2026: What Changes for Analytics

Microsoft Ads UTM Auto-Tagging September 2026: What Changes for Analytics

Microsoft Advertising is changing how its UTM auto-tagging works on September 2, 2026, separating Search, Audience Network, Shopping, and Performance Max campaign types into distinct UTM source and medium values. Previously, auto-tagged Microsoft Ads traffic appeared under a single campaign type identifier in analytics, making it difficult to distinguish between Bing Search traffic and Microsoft Audience Network display traffic in GA4 and similar tools. The September change fixes this at the source: each campaign type will produce distinct UTM parameters, making channel attribution accurate without manual UTM override.

Key takeaways

1. Microsoft Advertising changes UTM auto-tagging on September 2, 2026 to produce separate UTM values for Search, Audience Network, Shopping, and Performance Max campaigns.
2. Before September 2, Microsoft Ads auto-tagging grouped different campaign types under the same UTM identifier -- making it impossible to distinguish Bing Search traffic from Audience Network display traffic in analytics without manual UTM overrides.
3. If your campaigns use manually specified UTM parameters (UTM override), this change will NOT affect your attribution -- manual UTMs take precedence over auto-tagging.
4. If your campaigns rely on Microsoft Ads auto-tagging and you currently have custom segments or comparisons built on existing UTM values, audit those segments before September 2 to prevent historical data breaks.
5. This change makes Microsoft Ads traffic attribution more accurate in GA4, particularly for Performance Max, which previously was indistinguishable from Search in auto-tagged data.

The attribution problem auto-tagging was creating

UTM parameters are the mechanism by which ad clicks get attributed in analytics tools. When a user clicks a Microsoft Ads ad, the auto-tagging system appends UTM parameters to the destination URL automatically, passing information to GA4 (or whatever analytics tool is in use) about the source, medium, and campaign of that click.

The historical problem: Microsoft Ads auto-tagging used a limited set of UTM values that did not distinguish between fundamentally different campaign types. A click from a Bing Search ad and a click from a Microsoft Audience Network display placement would appear under similar or identical UTM source/medium combinations in GA4. In practice, this meant:

• Cross-campaign ROAS was impossible to see accurately. A marketer viewing GA4's "Microsoft Ads" channel could not determine whether a conversion attributed to that channel came from a high-intent Bing Search query or a display impression on an Audience Network site.
• Performance Max was invisible as a distinct channel. With Microsoft PMax running across Search, Audience Network, and LinkedIn simultaneously, all PMax traffic aggregated under the same UTM values as standard Search traffic.
• Audience Network display underperformance was hidden. If Audience Network display produced lower-quality sessions than Bing Search, the aggregate channel metric obscured the mix -- the channel appeared to perform at the average of the two, masking the need for separate optimization decisions.

This is the same structural issue that affects cross-channel analytics generally: when multiple inventory types map to a single channel label, channel attribution in GA4 loses the precision needed to diagnose where ROAS is being made or lost.

What changes on September 2, 2026

After the September 2 change, Microsoft Ads auto-tagging will produce separate UTM identifiers for each major campaign type:

• Bing Search campaigns will continue to use existing Bing/CPC identifiers with the current parameter structure.
• Microsoft Audience Network campaigns (display, native, video) will receive distinct UTM values that identify them as a separate channel from Search.
• Microsoft Shopping campaigns will receive UTM values that identify Shopping as a distinct campaign type.
• Performance Max campaigns will receive distinct UTM values separating PMax traffic from both Search and Audience Network traffic.

The operational impact of this change in GA4: what currently appears as a single "Microsoft Ads" or "bing/cpc" channel entry will split into multiple channel rows, each representing a distinct campaign type. Conversions, sessions, and revenue that were attributed to the aggregate will now be split across the new channel entries.

Prooflytics

Stop stitching platform exports together

Every channel in one brief — plus the memory of what each one actually drove.

Start free trialSee pricing

14 days free · no credit card

What to audit before September 2

Audit 1: Check whether you use auto-tagging or manual UTMs.

In Microsoft Advertising, go to your account settings and check the URL tracking section. If you have manual UTM parameters specified at the account, campaign, or ad level (e.g., ?utm_source=bing&utm_medium=cpc&utm_campaign={campaignname}), the September change does not affect your attribution. Manual UTMs override auto-tagging.

If your account relies on Microsoft Ads auto-tagging with no manual UTM override, the September change WILL affect how your Microsoft Ads traffic appears in GA4 from September 2 forward.

Audit 2: Identify GA4 segments and comparisons that use Microsoft Ads UTM values.

In GA4, check:

• Exploration reports with segments filtered by source contains "bing" or medium = "cpc" that capture Microsoft Ads traffic
• Custom channel groups that include Microsoft Ads channel definitions
• Looker Studio or reporting tool filters based on Microsoft Ads UTM values
• Any comparison benchmarks or alerts set on Microsoft Ads channel performance

After September 2, these segments may behave differently if the UTM values they're filtering on change. Document current UTM values before the change so you can update segment definitions to include the new campaign-type-specific values.

Audit 3: Export current Microsoft Ads channel attribution for baseline comparison.

Before September 2, export 90 days of GA4 data showing sessions, conversions, and revenue by Microsoft Ads channel. This baseline allows you to assess whether the post-September data looks consistent with the pre-September trend or shows a break that requires investigation.

Audit 4: Review cross-channel budget allocation decisions that reference Microsoft Ads aggregate.

If your media mix model or budget allocation framework uses Microsoft Ads aggregate performance as a channel comparison input, the September change may require recalculating historical comparisons. A Microsoft Ads channel that previously included Bing Search and Audience Network display combined is not directly comparable to a post-September channel that separates them.

How this affects Performance Max in GA4 specifically

Performance Max on Microsoft Ads is the campaign type most affected by this change. PMax runs across multiple inventory types simultaneously, and its aggregate attribution in GA4 has been particularly opaque:

• Pre-September: PMax clicks appear under the same UTM values as Bing Search clicks in auto-tagged accounts. GA4 shows no distinction between a PMax conversion and a Search conversion.
• Post-September: PMax will appear as its own distinct channel in GA4, making it possible to see PMax-specific session quality, conversion rate, and revenue contribution.

For accounts running both standard Bing Search campaigns and Performance Max, the September change will make cross-campaign comparison meaningful for the first time in auto-tagged accounts. The expected outcome: GA4 will show whether PMax sessions convert at higher or lower rates than standard Search sessions from the same account, providing data to inform the campaign type mix.

This complements the Microsoft PMax placement-level conversion data released in May 2026 -- together, these changes give Microsoft PMax the attribution visibility that has historically been a gap versus Google PMax.

If you want consistent attribution now, before September 2

For accounts that need clean channel separation immediately rather than waiting for September 2, the solution is to implement manual UTM parameters for Microsoft Ads campaigns:

https://yoursite.com/landing-page
  ?utm_source=bing
  &utm_medium=cpc
  &utm_campaign={campaignname}
  &utm_content={adgroupname}
  &utm_term={keyword}
  &msclkid={msclkid}

Critical: retain &msclkid={msclkid} when adding manual UTMs. The msclkid parameter is Microsoft's click ID, equivalent to Google's gclid. If you specify manual UTMs without preserving msclkid, Microsoft Ads conversion tracking may break because the click-to-conversion linkage depends on the msclkid value being passed to your landing page.

For Performance Max specifically, use a distinct utm_source or utm_medium value:

&utm_source=microsoft_pmax
&utm_medium=paid_social

This creates a PMax-specific channel in GA4 that is separate from your Bing Search cpc channel, without waiting for the September auto-tagging change.

Bottom line

• Microsoft Ads changes UTM auto-tagging September 2, 2026 to separate Search, Audience Network, Shopping, and Performance Max into distinct channel identifiers in GA4.
• If you use manual UTM overrides already, this does not affect you. If you rely on Microsoft Ads auto-tagging, audit your GA4 segments and reporting before September 2.
• Export 90 days of current Microsoft Ads channel performance data as a baseline before the change creates a historical comparison break.
• Performance Max gains distinct channel attribution in GA4 after September 2 -- the first time PMax and standard Search traffic will be separately identifiable in auto-tagged accounts.
• Add a GA4 annotation on September 2 to mark the data structure change for future reference in historical analysis.
• See independent reviews of marketing analytics platforms with Microsoft Ads integration on G2.