Microsoft Advertising has added age and gender controls to Performance Max, giving advertisers a way to explicitly include or exclude demographic groups from an automated campaign type. In its August 31 product roundup, Microsoft said the controls were already available to many advertisers and were rolling out toward general availability on September 8.
There is an important status caveat on September 8: Microsoft’s public announcement still says the feature is “rolling out to many advertisers” and says it “will be generally available” on September 8. Microsoft’s current Bulk API schema now lists campaign-level negative age and negative gender criteria as supported for Performance Max, but that does not independently prove that every eligible account has completed the UI rollout.
For B2B paid-media teams, the useful story is not simply that Microsoft added more targeting. It is that an automated campaign type now has a narrow deterministic delivery control alongside newer reporting and experiment surfaces. Our read: demographics should become a governed exclusion decision where they are permitted, not a shortcut for assuming the algorithm will perform better.
Direct answer — what changed in Microsoft Performance Max demographic targeting?
Microsoft now lets Performance Max advertisers explicitly include or exclude supported age brackets and gender groups. The control changes who the campaign can deliver to; it is not merely an audience signal. Microsoft scheduled general availability for September 8, but its public announcement still describes a rollout, so IVRIS is not treating rollout completion as independently confirmed.
Key Takeaways
- Microsoft says Performance Max can explicitly include or exclude age and gender groups, rather than only use them as audience preferences.
- Supported ages are 18–24, 25–34, 35–49, 50–64, 65+, and Unknown; gender options are Male, Female, and Unknown.
- Microsoft’s Bulk API schema lists campaign negative age and gender criteria specifically for Performance Max.
- Financial, insurance, education, career and employment, and housing advertising face Microsoft restrictions on demographic use for personalization, segmentation, or profiling.
- Microsoft has not published a performance uplift claim for these demographic controls.
What Microsoft Actually Put Into PMax
The newest product announcement is unusually explicit about the control boundary: advertisers can include or exclude age brackets and gender groups to limit Performance Max delivery. Microsoft’s AgeRange documentation lists 18–24, 25–34, 35–49, 50–64, 65+, and Unknown as the usable bands; two other enum values in the API are marked reserved. Its gender value set lists Male, Female, and Unknown.
The implementation evidence is clearest on exclusions. Microsoft’s current Bulk file schema lists “Campaign Negative Age Criterion” and “Campaign Negative Gender Criterion” as Performance Max-supported record types. The dedicated negative-age documentation also says campaign-level negative age criteria are supported only for Performance Max and warns that excluding Unknown can significantly reduce reach.
Microsoft’s announcement does not narrow the feature to a geography, account tier, or PMax subtype. It describes Performance Max generally, while the staged rollout means access can still differ by account during the transition.
Some older Microsoft Learn pages still say PMax lacks age or gender campaign criteria. They predate this rollout, so the August 31 announcement and newer Bulk schema are the controlling evidence.
Why This Is Different From an Audience Signal
Microsoft Performance Max already had audience groups that could contain age and gender dimensions as inputs to help the system find customers. That is not the same thing as an exclusion. A signal gives the model context; a negative campaign criterion changes eligibility. Microsoft’s own wording says the new controls can limit delivery to selected demographics.
The distinction is important for governance. When we covered Microsoft AI Max for Search in April, the useful pattern was the return of explicit guardrails inside increasingly automated media workflows. PMax demographic exclusions extend that pattern: Microsoft still automates bidding, inventory and delivery decisions, but advertisers can now put a hard boundary around one demographic dimension.
Microsoft’s Campaign object documentation also says the TargetSetting used for audience “target and bid” versus “bid only” cannot be used with Performance Max. This is not simply an audience signal switched into target-and-bid mode.
What This Control Does Not Prove
Microsoft has not claimed that demographic exclusions lower CPA, raise ROAS, improve lead quality, or solve PMax opacity. Excluding a group changes the population the system can reach; it does not establish why prior performance differed.
The same August roundup adds two useful evidence surfaces around PMax. Search terms are now easier to retrieve from both Search Term Insights and the Search Term report. Uplift experiments can estimate the conversion or conversion-value lift from adding PMax alongside comparable non-PMax campaigns. But Microsoft describes that experiment as a PMax-versus-non-PMax test, not a dedicated test of demographic exclusions. Upgrade experiments remain in pilot.
Microsoft has not announced a demographic-exclusion experiment or performance benchmark for this feature. Teams changing eligibility should record the change date, conversion definitions, budget and bidding state before interpreting later movement.
What B2B Teams Should Do Now
First, verify availability in the account. Microsoft scheduled general availability for September 8, but its public announcement has not been updated to confirm rollout completion.
Second, separate exclusions from signals in campaign QA. Record which demographic groups are hard eligibility boundaries and which audience inputs remain model guidance.
Third, check the policy boundary before using demographics. Microsoft’s demographic documentation says advertisers connected with financial, insurance, education, career and employment, or housing services cannot use demographics such as age or gender for personalizing advertising, segmenting, or profiling customers. This is a restriction, not an optimization recommendation.
Finally, require evidence before narrowing reach. Preserve a before-state and watch qualified outcomes rather than CTR alone. Microsoft has returned a useful control surface, not proof that a narrower audience performs better.
Frequently Asked Questions
Microsoft said the controls were rolling out to many advertisers and would be generally available on September 8, 2026. On September 8, its public announcement still uses that rollout language. Current API documentation supports PMax-specific negative age and gender criteria, but IVRIS is not treating full account rollout as independently confirmed.
Microsoft’s current age values are 18–24, 25–34, 35–49, 50–64, 65+, and Unknown. The product announcement lists Male, Female, and Unknown for gender. Microsoft’s API also contains two reserved age enum values, but they are not documented as usable targeting bands.
No. Audience groups can provide age, gender, and audience dimensions as inputs to help Microsoft find customers. The new PMax control explicitly includes or excludes demographic groups from delivery. Microsoft also documents that the standard campaign TargetSetting for audience “target and bid” versus “bid only” is unavailable to Performance Max.
No. Microsoft’s demographic documentation says advertisers connected with financial, insurance, education, career and employment, or housing services cannot use demographics such as age and gender for personalization, segmentation, or profiling. Separately, the PMax feature itself was still described by Microsoft as rolling out toward September 8 availability.
