> ## Content Index
> Fetch the complete content index at: https://cascader.io/blog/llms.txt
> Use this file to discover other available public pages before exploring further.

# Can I keep a Microsoft Search campaign from spending on audience and partner sites when search volume is low?
- URL: https://cascader.io/blog/microsoft-search-audience-partner-spend-low-volume/
- Published: 2026-10-03T14:00:49.000Z
- Updated: 2026-10-07T18:58:52.000Z
- Description: Narrow Microsoft Search delivery, check what publisher reports actually cover, and verify exclusions. When useful search demand runs out, spending less can be the right result.
- Author: Rick Hecker
- Tags: Cascader Answers, #Import 2026-10-01 11:26

**You can narrow a Microsoft Search campaign’s reach and block some unwanted destinations where Microsoft supports website exclusions. You cannot assume that its self-service settings will make it Bing-search-only.** The narrower “Microsoft sites and select traffic” option still includes audience placements and select partners. Start with delivery reports, apply the controls that fit the reported traffic, then verify what actually stops. [Microsoft’s ad distribution settings](https://github.com/MicrosoftDocs/Advertising/blob/main/advertising/msa-help/hlp%5FBA%5FCONC%5FAboutAdDistributionHidden.md?ref=cascader.io)

When search volume is low, spending less can be the right result. A budget permits spending; it does not oblige you to buy every available substitute for the searches you wanted.

![A turquoise bus marked with a magnifying glass stands beside a driver studying a map in a hall with a newspaper kiosk, an envelope doorway and a search doorway.](https://cdn.mymidnight.blog/ced556cd9f9c0c8315cfbe0744a3baf0/2026/10/feature.png)

## “Search” is on the campaign’s name badge, not every destination

A Search campaign can extend search ads into audience placements. Microsoft documents that it can reuse the search ad’s text and destination URL, with image annotations that can appear automatically. Using responsive search ads, or removing your own image extensions, does not by itself establish search-only delivery. A separate **Audience campaign** is a different campaign type; its placement controls and exclusion limits must not be read as rules for audience traffic inside a Search campaign. [Microsoft’s Audience ads guide](https://learn.microsoft.com/en-us/advertising/guides/audience-ads?view=bingads-13&ref=cascader.io)

The guest list for “Microsoft sites and select traffic” includes Bing, MSN, Outlook and select partners, whose traffic is reported in aggregate. “The entire Microsoft Advertising Network” adds further partners. **Both options include search and audience advertising.** The narrower option removes additional partners; it is not an audience-off switch. [Ad distribution scope](https://github.com/MicrosoftDocs/Advertising/blob/main/advertising/msa-help/hlp%5FBA%5FCONC%5FAboutAdDistributionHidden.md?ref=cascader.io)

That is why “the campaign went flat, so Microsoft filled the budget with audience traffic” needs checking. A changed mixture could explain the decline. The decline alone cannot establish that mixture, or prove why it changed.

## Find the spend before trying to stop it

Use the same campaign and date range in two views:

- **Campaign spending by Network** shows the material part of the problem. On **All campaigns → Campaigns → Campaigns**, select the table’s **Segment → Network** and inspect spend. Microsoft documents that interface route; its campaign-report API defines categories including Audience and Syndicated search partners. Keep the labels actually returned in your view. [Campaign table segmentation](https://github.com/MicrosoftDocs/Advertising/blob/main/advertising/msa-help/hlp%5FBA%5FCONC%5FSegmentation.md?ref=cascader.io), [campaign report categories](https://learn.microsoft.com/en-us/advertising/reporting-service/campaignperformancereportcolumn?view=bingads-13&ref=cascader.io)
- **Website URL (publisher)** shows the publisher destinations Microsoft makes available. Open **Reporting → Templates**, find that report, and include campaign, ad group, website, clicks, spend and the relevant conversion goal. Use it to identify exclusions and locate the ad groups buying the traffic. [Report templates and Website URL reporting](https://github.com/MicrosoftDocs/Advertising/blob/main/advertising/msa-help/hlp%5FBA%5FPROC%5FCreateReport.md?ref=cascader.io)

If the publisher export lacks **Network**, **keep the two views separate**: the campaign view establishes the reported network totals; the publisher view identifies disclosed destinations. You can still narrow distribution and pursue eligible site exclusions. You cannot assign a destination’s spend to Audience by spreading a campaign total across its websites—or by recognizing a Microsoft domain. Microsoft’s API specification does not establish that Network is available in the self-service Website URL template. If you already have an authorized integration and need both fields in one report, see “Network and publisher rows through an existing integration” below. [Self-service report documentation](https://github.com/MicrosoftDocs/Advertising/blob/main/advertising/msa-help/hlp%5FBA%5FPROC%5FCreateReport.md?ref=cascader.io), [publisher field definitions](https://learn.microsoft.com/en-us/advertising/reporting-service/publisherusageperformancereportcolumn?view=bingads-13&ref=cascader.io)

Even a report with both fields cannot supply individual sites inside the select-partner aggregate. The publisher report is useful evidence within its coverage, not an itemized receipt for every surface. [Select-partner reporting limit](https://github.com/MicrosoftDocs/Advertising/blob/main/advertising/msa-help/hlp%5FBA%5FCONC%5FAboutAdDistributionHidden.md?ref=cascader.io)

Do not use a clean search-terms report as an all-clear. Microsoft’s API guide explicitly says that **Search Query Performance and Share of Voice reports omit Audience ad performance**, even when an ad-distribution column or filter is requested. Those reports answer search questions; they cannot certify that no audience spend occurred. [Audience reporting coverage](https://learn.microsoft.com/en-us/advertising/guides/audience-ads?view=bingads-13&ref=cascader.io#audience-ads-reporting)

## Narrow the distribution, then make the exclusions apply

In each spending **Search campaign** ad group, open **Campaigns → Ad groups → Settings → Advanced settings → Ad distribution**. To remove additional partners, choose **Microsoft sites and select traffic** and save. This is an ad-group setting; changing one leaves the others to check. [Microsoft’s distribution procedure](https://github.com/MicrosoftDocs/Advertising/blob/main/advertising/msa-help/hlp%5FBA%5FCONC%5FAboutAdDistributionHidden.md?ref=cascader.io)

Do not treat all Microsoft-owned destinations as having one settled exclusion rule. Microsoft’s **Add exclusions** page says Search campaigns can block audience destinations such as MSN, Edge and Outlook, while protecting Microsoft search and Yahoo search. It says Audience campaigns cannot block Microsoft-owned sites. [Add exclusions](https://github.com/MicrosoftDocs/Advertising/blob/main/advertising/msa-help/hlp%5FBA%5FPROC%5FAddExclusions.md?ref=cascader.io)

Its **Website control lists** page opens with a broader statement that Microsoft sites cannot be excluded, then later distinguishes Search from Audience campaigns. These passages conflict; the narrower campaign-type distinction does not erase that conflict. [Website control lists](https://github.com/MicrosoftDocs/Advertising/blob/main/advertising/msa-help/hlp%5FBA%5FCONC%5FWebExclusionsTargetedWebsites.md?ref=cascader.io)

For unwanted destinations visible in the publisher report where Microsoft supports exclusions, create a website exclusion list under **Tools → Content suitability → Website control lists → Campaign exclusions**. Enter the destinations, save the list, then select it and **associate the intended campaign**. A saved list without an association is a beautifully organized piece of stationery. [Create and associate website control lists](https://github.com/MicrosoftDocs/Advertising/blob/main/advertising/msa-help/hlp%5FBA%5FCONC%5FWebExclusionsTargetedWebsites.md?ref=cascader.io)

The list you just made is **created in the advertising account and associated with campaigns**. A different list is **created in a manager account and associated with accounts**. Microsoft’s FAQ calls these “campaign-level” and “account-level” lists respectively, while other passages name the creation level. Identify yours by where you created it and what you associated it with. **Associated lists add exclusions to the applicable campaign or ad-group exclusions.** [List objects and associations](https://github.com/MicrosoftDocs/Advertising/blob/main/advertising/msa-help/hlp%5FBA%5FCONC%5FWebExclusionsTargetedWebsites.md?ref=cascader.io)

Use the root domain without `www` when you intend to cover its subdomains. For an app, use the publisher report’s **Mobile bundle** ID in the website exclusion list. [Domain handling](https://github.com/MicrosoftDocs/Advertising/blob/main/advertising/msa-help/hlp%5FBA%5FCONC%5FWebExclusionsTargetedWebsites.md?ref=cascader.io), [app exclusions](https://github.com/MicrosoftDocs/Advertising/blob/main/advertising/msa-help/hlp%5FBA%5FPROC%5FAddExclusions.md?ref=cascader.io)

**For the ad group you narrowed, use the campaign-associated list route above.** The self-service help documents that route and Search audience exclusions; a separate API condition for URLs entered directly on campaigns or ad groups does not establish that all exclusions fail after narrowing. If you are checking those direct exclusions, see “Direct sets in an existing entire-network ad group” below for the network prerequisite and replacement rule. Do not widen reach merely to satisfy that prerequisite. [Self-service list and exclusion guidance](https://github.com/MicrosoftDocs/Advertising/blob/main/advertising/msa-help/hlp%5FBA%5FCONC%5FWebExclusionsTargetedWebsites.md?ref=cascader.io)

## A saved setting is the beginning of the check

Record when you made the change. Re-run the network and publisher views for a later period, separate from the earlier spend. Check whether the unwanted traffic stops, whether another unwanted destination takes its place, and what happens to useful traffic. A list’s existence proves that you created a list. Later delivery establishes whether it did the job. If publisher rows lack Network, report changes in destination spend and changes in campaign network totals separately. A disappeared website does not establish that all Audience delivery stopped.

If delivery persists after narrowing, first check the campaign-associated list’s contents and association. If direct exclusions are involved, check the selected network and establish that the direct operation is supported there before applying its replacement rule. Take that configuration and the post-change report to support if applicability or delivery remains unresolved. When partner traffic is aggregated, keep that limit visible: you can evaluate and control the reported category only as far as the available settings allow. You cannot exclude an undisclosed domain by guessing its name.

Also inspect any scheduled Google Ads import and the settings it is permitted to overwrite. An imported change can undo the configuration you thought you had finished. Choose the import behavior deliberately and verify the affected settings after its next run; do not assume a support-applied exclusion has the same persistence rules as an ordinary campaign setting. [Microsoft liaison’s import guidance](https://officialppcchat.com/2026/01/19/all-your-2026-microsoft-ads-questions-answered-with-navah-hopkins-of-microsoft-ads/?ref=cascader.io)

For audience delivery inside a Search campaign, apply the documented exclusion route, check the result, and escalate persistent delivery. In a January 2026 PPCChat discussion, Microsoft liaison Navah Hopkins described asking support for **display exclusions with a data-based reason**. That is a request route, not a guarantee of approval or of excluding every partner. [PPCChat’s Microsoft Ads questions, including display exclusions](https://officialppcchat.com/2026/01/19/all-your-2026-microsoft-ads-questions-answered-with-navah-hopkins-of-microsoft-ads/?ref=cascader.io)

Give support the campaign IDs, network and publisher spend, the unwanted destinations, the saved exclusions and associations, and the business result you can substantiate. Keep campaign-level network totals separate from publisher figures when no report row connects them. Ask which inventory the change excludes, whether it applies to the account or named campaigns, and what happens to new campaigns. “Please stop this reported audience delivery” is a more testable request than “please make it Microsoft-only.”

## Decide what the remaining campaign earns

When source-linked lead quality is missing, make the decision you can support. Use the campaign’s total spend and actual qualified outcomes, allowing for your normal qualification delay. Treat network-level platform conversions as preliminary evidence, and keep view-through credit distinct from outcomes following a click; neither alone proves that an audience placement created extra business. [Publisher conversion and view-through definitions](https://learn.microsoft.com/en-us/advertising/reporting-service/publisherusageperformancereportcolumn?view=bingads-13&ref=cascader.io)

If the whole campaign is worth buying **and its remaining inventory meets your requirement**, you can retain it at a spending level whose uncertainty you can afford while improving source tracking. If the campaign is unacceptable and you cannot isolate or stop the offending inventory, **lower the budget or pause the campaign**. You do not need a complete placement verdict to stop funding an unacceptable aggregate. If your requirement is strictly search-only, unresolved audience delivery is itself a reason to stop until a suitable control is confirmed. The same applies if your requirement excludes particular partners and the remaining aggregate cannot establish that they are absent.

When your tracking does connect qualification to a network, a changed mixture can explain the business result. Suppose a lead campaign has these **illustrative figures**, after enough time for leads to be qualified and attributed to their traffic source:

If columns extend beyond the page, scroll sideways. With a keyboard, focus the table and use the arrow keys.

| Period  | Search spend / qualified leads | Audience spend / qualified leads | Total cost per qualified lead |
| ------- | ------------------------------ | -------------------------------- | ----------------------------- |
| Earlier | $480 / 8                       | $120 / 0                         | $600 ÷ 8 = $75                |
| Later   | $180 / 3                       | $420 / 0                         | $600 ÷ 3 = $200               |

The search portion still costs $60 per qualified lead in both periods. The campaign looks dramatically worse because more of its spending buys a portion that, in this example, produces none. That makes inventory control a relevant intervention. If search itself had become more expensive per qualified lead, excluding audience sites would leave that separate problem to solve.

This illustration gives no separate partner result. It does not identify which partners, if any, sit inside the Search figures. To judge a partner’s economics, you need outcomes linked to that partner; a good Search average cannot settle it. You can still exclude an otherwise eligible unwanted site without first measuring its profitability.

These are business-qualified leads, not automatically every form submission counted by Microsoft. If your existing tracking cannot connect qualification to a network, you cannot truthfully fill in this table from publisher clicks and a CRM total; use the aggregate decision above.

Return to the illustrative campaign. Suppose exclusions actually remove the $420 audience spend, while the search portion continues to spend $180 and produce three qualified leads. You now have **$60 per qualified lead on $180 spent**. You do not have evidence that the unused $420 can buy another seven leads. The profitable little search campaign may simply be little.

If $60 meets your economics and you accept the remaining inventory, keeping that smaller campaign can make sense. That is a decision about the aggregate you are still buying, not a separate approval of its partners. Where a partner can be identified and qualified outcomes attributed to it, evaluate its spend against those outcomes separately. Where partners remain undisclosed in an aggregate, decide whether buying that aggregate meets your inventory requirement; the $60 average cannot prove which partners are absent. If the remaining search leads are too costly or unsuitable, inventory controls have not rescued it. Reduce spending or pause while you address that separate issue. There is no benefit in winning the distribution-setting argument and losing the business one.

Low search volume does not make unwanted reach compulsory. The useful outcome may be a narrower, quieter campaign—or a decision that Microsoft cannot presently deliver the traffic you are willing to buy.

## Network and publisher rows through an existing integration

To obtain **Network and publisher in the same rows**, use an authorized Reporting API integration. Ask whoever runs it for a daily **Publisher usage performance report** with `Network`, `PublisherUrl`, `CampaignId`, `AdGroupId`, `TimePeriod`, `Clicks` and `Spend`, scoped to this campaign and period. These columns belong in one report request; the selected attributes break its statistics into rows. You do not need to join a campaign total onto each website. Check the report’s date boundaries and completeness before comparing exports. [Publisher report request](https://learn.microsoft.com/en-us/advertising/reporting-service/publisherusageperformancereportrequest?view=bingads-13&ref=cascader.io), [available columns](https://learn.microsoft.com/en-us/advertising/reporting-service/publisherusageperformancereportcolumn?view=bingads-13&ref=cascader.io), [report grouping and completeness](https://learn.microsoft.com/en-us/advertising/guides/reports?view=bingads-13&ref=cascader.io)

That route requires a developer token and OAuth consent for a user with access to the advertising account. A developer token grants no extra account permissions. It is a reporting integration, not another option on the template menu. [API access requirements](https://learn.microsoft.com/en-us/advertising/guides/get-started?view=bingads-13&ref=cascader.io)

Use these rows for the same evidence and later-delivery checks described above. They connect reported network and publisher spending within the report’s coverage; they do not supply business qualification or reveal individual sites inside the select-partner aggregate.

## Direct sets in an existing entire-network ad group

**Direct exclusions need a separate network check.** These are URLs entered on a campaign or ad group itself, rather than in an associated list. For direct syndicated-site exclusions, Microsoft’s API documentation requires the ad group’s Network to be `OwnedAndOperatedAndSyndicatedSearch`, which Microsoft maps to **the entire network**. The common route’s narrower choice maps to `OwnedAndOperatedOnly`. Those are different settings, not two spellings of the same permission slip. [Direct-operation prerequisite](https://learn.microsoft.com/en-us/advertising/campaign-management-service/adgroupnegativesites?view=bingads-13&ref=cascader.io#negativesites), [network-value mapping](https://learn.microsoft.com/en-us/advertising/campaign-management-service/network?view=bingads-13&ref=cascader.io#values)

This is a different configuration from the narrowed associated-list route. The specific API condition does not establish that direct operations in the UI and API have identical applicability. Before relying on a direct syndicated-site fix under the narrower selection, ask Microsoft to confirm support for that operation on that network. Do not widen reach merely to satisfy the direct-operation prerequisite. [Self-service list and exclusion guidance](https://github.com/MicrosoftDocs/Advertising/blob/main/advertising/msa-help/hlp%5FBA%5FCONC%5FWebExclusionsTargetedWebsites.md?ref=cascader.io)

If you are instead checking an **existing entire-network ad group with otherwise-excludable syndicated sites**, this optional example shows which direct set applies. Suppose the campaign’s direct set excludes site A and the ad group’s direct set excludes site B. Microsoft uses **B instead of A plus B** for that ad group. To preserve both through direct exclusions in that configuration, put A and B in the ad group’s direct set. Associated lists remain additional; an ad-group direct set does not replace them. [Direct replacement and list addition](https://learn.microsoft.com/en-us/advertising/guides/negative-sites?view=bingads-13&ref=cascader.io)

After any applicable direct change, use the later-delivery and import checks above. A stored direct set does not establish that the operation applies to the selected network or that the unwanted traffic stopped.