---
title: "Microsoft Ads Click Monitoring: A Paste-Ready Block List Workflow"
description: "A weekly routine for Microsoft Ads click monitoring, from a UET baseline to a dated, paste-ready IP block list applied to the right campaigns."
url: https://blockclickfraud.com/microsoft-ads-click-monitoring/
date: 2026-10-16
modified: 2026-10-20
author: "Block Click Fraud"
image: https://blockclickfraud.com/wp-content/uploads/2026/10/microsoft-ads-click-monitoring-featured.webp
categories: ["Uncategorized"]
type: post
lang: en
---

# Microsoft Ads Click Monitoring: A Paste-Ready Block List Workflow

Microsoft Ads click monitoring works best as a short weekly routine: confirm your UET conversion tracking is recording properly, review click-level data on a fixed day, give each odd source a verdict and a reason, then paste a clean one-IP-per-line list into the right campaign. Microsoft filters some invalid traffic itself and credits you for it. It does not tell you which sources slipped through, so that part is on you.

## Step 1: confirm your UET and conversion baseline

Click monitoring without conversion data is guesswork. An odd click that became a booked call is a customer. The same click with no follow-up is a question.

Microsoft's setup guidance is simple: create a UET tag in Microsoft Advertising, then add the tracking code to every page of your site. Then set up conversion goals that match what a real lead looks like for you, such as a form submission or a call.

Before you trust any of it, test it. Submit your own form, place a test call if you track calls, and confirm both show up. Then write down your normal week: typical clicks, typical conversions, typical cost. Microsoft's own advice on spotting invalid clicks is to learn your usual daily, weekly and monthly click volume so sudden changes stand out. That baseline is what every later check is measured against.

## Conversion tracking vs click monitoring

They answer different questions, and you need both.

| | Conversion tracking (UET) | Click monitoring |
| --- | --- | --- |
| Question it answers | Did this traffic produce a lead or sale? | Where did each paid click come from, and was it genuine? |
| Main data source | The UET tag and your conversion goals | Click records, server logs, landing page data |
| What it catches | Drops in conversion rate, campaigns that spend without results | Repeat sources, automated traffic, clicks from places you do not serve |
| What it misses | Which sources caused a drop | Whether a clean-looking click had any buying intent |
| What you do with it | Shift budget, fix landing pages, adjust bids | Exclude sources, document reasons, contact support |

Microsoft's help pages point out that a sudden change in conversion rate could mean more low-quality and invalid clicks. Conversion tracking raises the flag. Click monitoring tells you who to block.

## Step 2: review click-level data on a schedule

Pick one day a week and stick to it.

Inside Microsoft Advertising, add the Low-quality clicks and Low-quality click rate columns to your reports through the column modifier. Microsoft sorts every click into standard-quality, low-quality or invalid, and you are only billed for standard-quality clicks. Clicks later found to be low-quality or invalid are adjusted on your bill, though they can still appear in reports as standard-quality. The [Microsoft Ads invalid click report guide](/microsoft-ads-invalid-click-report/) explains how to read these numbers.

Then look outside the ad platform. Pull the week's paid visits from your server logs or analytics and look for:

- The same address returning many times with no conversion.

- Visits from regions you do not serve.

- Sessions that leave instantly, in clusters.

- Traffic from hosting providers rather than home or mobile networks. [Datacenter vs residential IP fraud](/datacenter-vs-residential-ip-fraud/) explains why that difference matters.

Before you blame fraud, check the ordinary causes Microsoft lists for higher click volume: seasonal changes, a sale or promotion, recent news, changes to your ad text or site, and new inbound links.

## Step 3: assign a verdict and a reason

Every source you review gets one of three verdicts, with a written reason. In three months nobody will remember why an address was blocked.

| Verdict | What it means | Action |
| --- | --- | --- |
| Clean | Behaves like a normal prospect, whether or not it converted | None. Leave it alone. |
| Suspect | Something is off, but you are not sure yet | Note it and check again next week |
| Fraud | Clearly not a genuine prospect: automated, repeating with no intent, or faking its identity | Add to the block list with the reason and date |

Leave legitimate crawlers alone. [Good bots you should never block](/good-bots-never-block/) lists them.

## Step 4: build a paste-ready block list

Microsoft's IP exclusion box wants one IP address per line. It accepts IPv4 only, each address needs all four parts, and only the last part can be a wildcard, as in 127.0.0.* for the whole range from 127.0.0.0 to 127.0.0.255. Entries in any other format will not work.

Keep one master file per account in plain text:

1. Add each new fraud address on its own line.
2. Remove duplicates. The same address flagged twice wastes a slot.
3. Sort the list so ranges and neighbours sit together. That makes it easy to see when several addresses could become one wildcard entry.
4. Save a dated copy each week, for example with the date in the file name. If something goes wrong after an update, you can see exactly what changed.
5. Keep the reasons in a separate sheet keyed by address, so the paste file stays clean.

The paste file should contain nothing but addresses. No notes, no commas, no blank lines.

## Step 5: apply it to the right campaign and document it

In Microsoft Advertising, go to Campaigns, tick the campaign you want to change, choose Edit, then Other changes, and pick IP address exclusions from the Campaign settings menu. IP exclusions must be added at the campaign level, not the ad group level.

Microsoft's help page states a maximum of 100 IP addresses or ranges per campaign. That is far tighter than Google's limit, so wildcards and regular pruning matter more here. Limits change, so check Microsoft's current page before you plan around it. [Microsoft Ads click fraud](/microsoft-ads-click-fraud/) covers what to do when you hit the cap, and [Microsoft Ads vs Google Ads click fraud](/microsoft-ads-vs-google-ads-click-fraud/) compares how the two platforms handle exclusions.

After you paste, record what you did: date, campaign, number of entries added, and the name of the master file version you used. A block on one campaign does nothing for the others, so apply the list wherever the source appears.

## A review cadence for Microsoft Ads click monitoring

A rhythm that holds up for most accounts:

- **Weekly:** review clicks and conversions against your baseline, assign verdicts, update and paste the list.

- **Monthly:** recheck suspect sources, merge neighbouring addresses into wildcards, and remove old entries that have not appeared again so you keep room under the cap.

- **Whenever conversion rate moves sharply:** run the weekly review early, and if you believe you were charged for invalid clicks, contact Microsoft support with your records.

If you want every click checked and the paste-ready list built for you, [see how Block Click Fraud works](/how-it-works/).

## Frequently Asked Questions

### Does Microsoft Ads charge for invalid clicks?

Microsoft says you are only billed for standard-quality clicks. If clicks are later found to be low-quality or invalid, your bill is adjusted. Those clicks can still appear as standard-quality in your reports, so the report alone will not show the credit.

### How many IP addresses can I exclude per Microsoft Ads campaign?

Microsoft's help page currently states a maximum of 100 IP addresses or ranges per campaign. Use last-part wildcards to cover ranges, and check the current page before planning, since limits can change.

### Can I add IP exclusions at the ad group level in Microsoft Ads?

No. Microsoft's instructions say IP exclusions must be added at the campaign level, not the ad group level. Plan to apply your list to each campaign that needs it, and keep a note of which campaigns have which version.

### Why does my pasted list get rejected?

Usually because of formatting. Microsoft wants one IPv4 address per line, all four parts present, and a wildcard only in the last part. Strip out notes, commas, IPv6 addresses and blank lines.

### How often should I review Microsoft Ads clicks?

Weekly works for most accounts, with a monthly cleanup of the list. Review sooner if your conversion rate changes suddenly, since Microsoft notes that can signal more low-quality and invalid clicks.

## Sources

- [Microsoft Advertising Help: how to prevent your ads from showing to certain people (IP exclusions)](https://learn.microsoft.com/en-us/advertising/msa-help/hlp_ba_proc_addexclusions)

- [Microsoft Advertising Help: monitoring clicks, telling the good from the bad](https://learn.microsoft.com/en-us/advertising/msa-help/hlp_ba_conc_aboutpreventinginvalidclicks)

- [Microsoft Advertising Help: setting up UET](https://learn.microsoft.com/en-us/advertising/msa-help/hlp_ba_conc_uet_setup_master)
