# Microsoft Ads Structure: Locations, Language and Distribution

> Design Search campaigns around budget ownership, language, location intent and current network distribution controls.

Source: https://mentionx.ai/learn/microsoft-ads/microsoft-ads-campaign-locations-language-distribution  
Author: Dipuck Jones, founder of MentionX  
Updated: 8 November 2026  
Level: Practitioner

**Microsoft Search structure should reflect who owns the budget, which offers can serve each market and which language, location and network controls must remain independent. A campaign name does not override the actual ad-group settings or distribution options.**

> **Key takeaways**
> - Split campaigns for meaningful commercial or control differences, not decorative complexity.
> - Review location intent and language together; Microsoft does not translate ads.
> - Microsoft sites and select traffic is not a Bing-only option.
> - Check AI Max defaults and imported settings before calling a campaign keyword-only.

*Checked 8 November 2026 (CET) against Microsoft targeting, distribution, Audience and AI Max documentation. Structural recommendations are editorial judgement. Ledgerline's markets, products and account design are fictional and illustrative.*

## Which differences justify a separate campaign?

Start with boundaries that cannot safely share governance. Independent budgets, incompatible delivery markets, different commercial outcomes, separate legal obligations or materially different language experiences can justify separate campaigns. A campaign should have a clear owner and a coherent decision when performance changes.

Do not split every keyword into a separate campaign merely to reproduce a legacy agency template. Extra entities create extra budgets, import mappings, alerts and reporting work. If two groups share the same offer, market, language, objective and controls, explain what a split would improve before adding it.

Ad groups can organise related intent and creative within a campaign, but they do not create independent campaign budgets. If one product family must have a guaranteed internal allocation under the merchant's approval policy, a shared campaign may not express that requirement adequately.

The [Google account setup lesson](https://mentionx.ai/learn/google-ads/google-ads-account-setup-checklist) offers general governance concepts. Microsoft's hierarchy and current feature scope must determine the final design. Similar-looking campaign structures can behave differently once distribution, language overrides and automation are considered.

## How should you map offers to the hierarchy?

Create a structure sheet before building. For each proposed campaign, record market, language, outcome, budget owner, bid strategy, distribution policy and destination set. For each ad group, record the buyer need, keyword family, creative proposition and relevant audience associations.

| Structural decision | Separate when | Keep together when |
| --- | --- | --- |
| Campaign budget | Owners or approved spend envelopes differ | One owner can govern the combined allocation |
| Market | Fulfilment, offer or restrictions differ materially | The same promises and controls genuinely apply |
| Language | Ads and destination experience require separate review | The full journey supports the same intended audience |
| Ad group | Buyer decisions need different creative and pages | The query family shares one coherent proposition |
| Audience association | Restriction or observation serves a clear purpose | Additional layers add no actionable distinction |

The table is a planning aid, not a rule that every country requires its own campaign. A multinational business might govern several markets together if the relevant settings, economics and customer experience are compatible. Conversely, two regions in one country may require separation if delivery promises differ.

Name entities so the commercial purpose is visible without encoding every setting. Keep a separate settings register because names become stale. A campaign called Germany Search can still contain an incorrect location-intent setting or an inherited language override.

## What does location targeting mean in practice?

Microsoft distinguishes people in a targeted location from people in, searching for or viewing information about it, depending on the available option. Choose based on the offer. A physical delivery promise normally requires a different review from a tourism or relocation service that legitimately serves people researching a destination.

Location signals are not perfect proof of physical presence. Do not describe targeting as a guaranteed legal geofence or a substitute for checkout eligibility. The website should still validate delivery coverage and clearly explain limitations before a customer commits.

Review exclusions and unsupported targets. An imported postcode or small region can map differently, including radius or parent-location behaviour. Inspect the saved target list and the resulting geographic intent rather than assuming the source selection survived unchanged.

Document the intended policy in plain language. “Customers physically present in our eligible delivery area” is a clearer acceptance statement than “use the default location option.” Then ask the authorised operator to demonstrate which current settings express that policy and what residual uncertainty remains.

## How does language affect eligibility?

Microsoft uses language signals and campaign or ad-group settings to determine eligibility. It does not translate the advertiser's text or landing page. A language setting that allows an audience to see an ad does not make the customer experience understandable.

Review the whole journey: ad, sitelink or other asset, landing page, product details, delivery information, checkout and support. A translated headline leading to an incompatible or untranslated purchase process is not a complete localisation plan.

Standard Search can have relevant ad-group language settings, while campaign types such as Performance Max use campaign-level language and location controls. Do not assume a setting available at one hierarchy level exists for every product. Record the actual scope in the structure sheet.

For inherited accounts, compare campaign settings with ad-group overrides. An operator may change the campaign language and assume all delivery follows it, while an older ad group retains a different configuration. Review actual saved values, especially after import, duplication or a bulk edit.

## What do the current distribution choices mean?

Microsoft's current documentation describes the entire Microsoft Advertising Network and Microsoft sites and select traffic. The narrower option still includes selected partners. It should not be renamed Bing-only in a client report or internal approval request.

The documentation also states that both options include Search and Audience ads. Therefore, choosing a Search campaign is not a sufficient explanation of every possible delivery context. Review current distribution settings and actual reporting rather than relying on the campaign-type label alone.

Distribution is an ad-group-level setting even when chosen during creation. This makes inherited inconsistencies possible: two ad groups in the same campaign can deserve different inspection. A campaign-wide verbal policy is not enforced merely because the team agreed it in a meeting.

Some select traffic is reported in aggregate rather than exposing individual domains. Other partner traffic can be reviewed through website or publisher reporting and applicable exclusions. Do not promise that every domain is visible or that every first-party surface can be individually excluded with the same control.

## How should you evaluate partner and Audience exposure?

Start with the intended role and comparable outcomes. A publisher segment with a lower click price is not automatically better if purchases are weaker or qualification is poor. Conversely, a different conversion pattern does not prove fraudulent traffic.

Use the reporting that is actually available, including its aggregation and attribution limits. Document what cannot be separated. If a manager requests an exact performance figure for an unreported individual select partner, explain the limitation rather than manufacturing a split from broader totals.

Audience placement controls and related features can be in rollout or limited availability. Confirm the actual account's options before designing a required exclusion policy around them. If a necessary brand-safety or legal requirement cannot be expressed, do not launch that configuration until an acceptable route is agreed.

A separate Audience campaign can support a distinct native, display or online-video hypothesis, but it introduces its own budget and targeting decisions. Do not assume it is merely an automatic extension of the Search plan or that the same creative is suitable in every browsing context.

## Why should AI Max appear in the structure review?

Microsoft's August 2026 announcement states that AI Max is enabled by default for new Search campaigns, with an option to opt out. The suite includes search-term matching, text customisation and final URL expansion. A new campaign should therefore be inspected before anyone describes it as limited to a manual keyword and URL plan.

Check each component and its eligibility rather than treating the parent label as a complete description. Conversion-based strategy requirements and feature-specific access can affect what operates. URL boundaries and generated text can change the practical meaning of an ad group's intent theme.

Scheduled Google imports can inherit AI Max settings. Add an automation-owner column to the structure sheet so the team knows whether a local choice may later be changed upstream. The approved design should survive the operating model, not just the day it is created.

> **Pro move:** Review the hierarchy in two views: the intended commercial map and an export of actual settings. Differences between the two are usually more useful than a perfectly formatted naming convention.

## What should an international handover test?

Have the receiving market owner review the actual offer, not only the translated campaign name. Ask them to identify an unsupported address, an ambiguous product term and a checkout condition that differs from the source market. These cases often expose whether the structure truly supports local operations or merely copies source settings.

Include a settings snapshot with the account, campaign, ad group, language, location intent, exclusions and distribution scope visible. Redact unnecessary personal information. Attach the plain-language acceptance statement and the owner who verified it. If a later operator cannot reconcile the snapshot with the commercial map, treat that mismatch as a review task before changing bids. The purpose is not to create more documentation for its own sake; it is to make local obligations testable across staff and agency transitions.

## Worked example: Ledgerline

Ledgerline plans an illustrative German-language campaign for desk organisers and a separate English-language bulk-office enquiry programme. The merchant initially wants one campaign because both sell office products. Review shows different budget owners, destination experiences and success definitions.

The team separates those commercial responsibilities, then uses ad groups for coherent product or enquiry themes. It documents presence-oriented delivery intent for the storefront, reviews the actual language configuration and records the narrower distribution option without calling it Bing-only.

### Walkthrough

1. List each offer's eligible delivery area, language experience and business outcome.
2. Assign a budget owner and decide which differences require separate campaigns.
3. Map ad groups to compatible query families, ads and landing pages.
4. Inspect campaign and ad-group location and language settings for overrides.
5. Record the actual distribution choice and its reporting limitations.
6. Review AI Max components, URL boundaries and any imported source control.
7. Create an acceptance checklist that an authorised operator can compare with saved settings.

No results are invented. The example's benefit is a clearer operating design, not a claimed improvement in click-through rate, reach or sales.

## Common mistakes

A common mistake is using country names in campaigns as if names enforce targeting. Another is translating an ad without checking the page, checkout or support experience. Both create a gap between the account diagram and the customer journey.

Do not promise granular partner exclusions from controls that report selected traffic only in aggregate. Also avoid splitting campaigns to solve a problem that actually belongs to measurement or fulfilment. More structure cannot make an unsupported delivery promise true or a duplicated purchase event reliable.

## Try it yourself

Draft a hierarchy for two offers with different commercial obligations. Include campaign owner, outcome, budget envelope, market, language, distribution and destination set. Add ad-group intent and any audience modes or overrides that could affect reach.

Then write three adversarial checks: an unsupported location, a stale ad-group language and an AI Max setting restored by import. Explain how the team would detect each before serving. The exercise is complete when the intended design can be tested against actual settings, not merely when every entity has a neat name.

## Quick quiz

**1. Does a language setting translate the ad or destination?**

*Answer:* No. The advertiser must provide and verify the intended language experience throughout the journey.

**2. Where does Microsoft's documented Search distribution setting apply?**

*Answer:* At ad-group level, so inspect actual ad-group values even when the choice was made during campaign creation.

**3. Why inspect AI Max when creating a new Search campaign?**

*Answer:* Microsoft's current announcement says it is enabled by default for new Search campaigns, while individual components and eligibility still require review.

## What should the structure handover include?

Provide the commercial map, actual-setting acceptance criteria, override inventory and automation ownership. A new operator should understand both what the account is intended to do and which settings make that intention real.

Previous: [Microsoft Ads Match Types: Search Terms and Negative Controls](https://mentionx.ai/learn/microsoft-ads/microsoft-ads-match-types-search-terms-negatives) · Next: [Microsoft Ads Creative: Responsive Search Ads and Asset Review](https://mentionx.ai/learn/microsoft-ads/microsoft-ads-responsive-search-ads-assets)

Or return to the [Microsoft Ads for Marketers track](https://mentionx.ai/learn/microsoft-ads/microsoft-ads-for-marketers).

Related: [Microsoft Ads Keyword Research: Planner, Intent and Evidence](https://mentionx.ai/learn/microsoft-ads/microsoft-ads-keyword-planner-intent-research) · [Microsoft Ads Audiences: Remarketing, Match and LinkedIn Signals](https://mentionx.ai/learn/microsoft-ads/microsoft-ads-audiences-remarketing-customer-match) · [Microsoft Audience Campaigns: Native, Display and Online Video](https://mentionx.ai/learn/microsoft-ads/microsoft-ads-audience-native-display-video)

## Common questions

**Does selecting a language translate the customer journey?** No. Ads, destinations, checkout and support need their own appropriate language experience. Verify campaign and ad-group settings as well as the content.

**Is Microsoft sites and select traffic Bing-only?** No. The documented option includes Microsoft sites and selected partner traffic. Some selected traffic is reported in aggregate rather than by individual domain.

**Does location targeting guarantee physical presence?** No. Review the chosen location-intent option and acknowledge signal limitations. The website still needs truthful delivery eligibility and appropriate customer checks.

## Sources

- [Ad distribution settings](https://learn.microsoft.com/en-us/advertising/msa-help/hlp_ba_conc_aboutaddistributionhidden)
- [How does ad language and location targeting affect who can see my ads?](https://learn.microsoft.com/en-us/advertising/msa-help/hlp_ba_conc_loctargetandlang)
- [Reimagining Search campaigns for the AI era with AI Max](https://about.ads.microsoft.com/en/blog/post/august-2026/reimagining-search-campaigns-for-the-ai-era-with-ai-max)
- [What are audience campaigns?](https://learn.microsoft.com/en-us/advertising/msa-help/hlp_ba_conc_nativeads)
- All accessed 8 Nov 2026 (CET).

## Frequently asked questions

### Does selecting a language translate the customer journey?

No. Ads, destinations, checkout and support need their own appropriate language experience. Verify campaign and ad-group settings as well as the content.

### Is Microsoft sites and select traffic Bing-only?

No. The documented option includes Microsoft sites and selected partner traffic. Some selected traffic is reported in aggregate rather than by individual domain.

### Does location targeting guarantee physical presence?

No. Review the chosen location-intent option and acknowledge signal limitations. The website still needs truthful delivery eligibility and appropriate customer checks.

---

Written and reviewed by Dipuck Jones for MentionX Learn. The HTML version of this page: https://mentionx.ai/learn/microsoft-ads/microsoft-ads-campaign-locations-language-distribution