Google Ads exclusion lists
Spurn keeps flagged networks out of your Google Ads campaigns through IP exclusion lists, stays inside Google's 500-entry limits and never touches the entries you added yourself.
Two kinds of list#
Google Ads has two places to exclude IP addresses, and Spurn uses both.
| Account-level list | Campaign-level lists | |
|---|---|---|
| Limit | 500 entries per account | 500 entries per campaign |
| Applies to | Every campaign in the account: Search, Shopping, Display, Performance Max, Demand Gen, App, Discover and YouTube | The one campaign it belongs to |
| Not available for | Nothing | Performance Max, App, Video, Hotel and Smart Display campaigns |
| Accepts | IPv4 and IPv6, single addresses or CIDR blocks | IPv4 and IPv6, single addresses or CIDR blocks |
The two kinds add together: an IP on either list is excluded from that campaign. Spurn writes to the account-level list first, because it covers every campaign type, then to the lists of your Search, Shopping and Display campaigns.
If a network on your exclusion list still reaches an ad through a campaign its list does not cover, Spurn tags the click Already blocked so you can see the gap.
Spurn's share: 400 slots per list#
Spurn uses at most 400 of the 500 slots in each list by default: the account-level list and each campaign list. That leaves 100 slots in every list for your own entries. The slot count is set per ad account. If you keep more than 100 IP exclusions of your own, lower Spurn's share for that account so Google's limit is never hit.
Your own entries are never touched#
Spurn records the Google Ads resource name of every entry it creates, and it only ever removes entries on that record. IPs you or another tool added stay exactly where they are, even if Spurn later flags and unflags the same network.
Priority and rotation#
Once Spurn's share of a list is full, a new network can only go in if something comes out. Spurn ranks every exclusion by:
- Hard reasons first: Known bot, Automated browser and Tor exit node.
- Then the estimated spend on invalid clicks from that network.
- Then how recently it misbehaved.
When a higher-ranked network needs a slot, the lowest-ranked entry on the list is rotated out. It is not forgotten: it waits in overflow and goes back on as soon as a slot frees up, when an exclusion expires or you remove one. Every rotation is in the change log.
Each exclusion shows its delivery status for each linked ad account:
| Status | Meaning |
|---|---|
| Pending | Waiting to be pushed to the account |
| Applied | Confirmed in Google Ads |
| Overflow | Outranked while the list is full; waiting for a free slot |
| Removing | Being taken off the account |
| Removed | Off the account |
| Failed | The last push failed and will be retried |
A failed push is retried after 2, 8, 32 and 128 minutes. After 5 failed attempts Spurn stops retrying and sends you a connection alert, because something usually needs fixing on the account, such as an expired login.
Grouping into /24 blocks#
When two or more data-centre IPs from the same /24 block (or /48 for IPv6) are flagged, Spurn excludes the whole block as one entry. That uses one slot instead of several, and it also covers the neighbouring addresses a bot farm rotates through.
Only data-centre networks are grouped. Residential and mobile addresses are shared with real shoppers, so Spurn excludes them one IP at a time. You can turn grouping off with the Group subnets rule in the Rules tab.
How long an exclusion lasts#
An automatic exclusion lasts 30 days. Each time the network is flagged again, Spurn pushes the expiry date out. When an exclusion expires, Spurn takes it off your ad accounts, and it goes straight back on if the network returns and is flagged again.
Set Exclusion length in the Rules tab to change this. Set it to 0 to keep automatic exclusions until someone removes them. Expiry is what keeps slots free for networks that are still clicking, so a permanent setting fills your lists faster.
Adding your own entries in Spurn#
You can also add an address or a /24 block under Blocking, with a note such as "competitor's office", or through the REST API. Spurn delivers it to your linked ad accounts like any other exclusion, and it appears in the change log with your name.
Change log and undo#
Blocking, then Change log, records every change to your exclusions: created, extended, applied, rotated into overflow, restored, failed, removed and expired. Each entry says when it happened, which ad account it concerned and who made it: you, a teammate or Spurn.
To undo a block, remove the exclusion under Blocking. Spurn takes its entries off every linked ad account. To undo the undo, restore it. If a real customer was blocked, also add their address to the allowlist so it is never flagged again.
Performance Max#
Google does not accept campaign-level IP exclusions on Performance Max. The account-level list is the only IP exclusion Performance Max respects, so on an account that spends mostly on Performance Max, the account-level list is what protects it. Spurn's 400 slots there hold the highest-ranked networks.
On Pro and up, Spurn also adds account-level placement exclusions: apps and sites that send junk clicks to Display and Performance Max campaigns. Google applies account-level placement exclusions to Performance Max too. They have their own, much larger limit, separate from the IP lists.
Microsoft and Meta#
Microsoft Ads and Meta Ads have no API for IP exclusions, so Spurn protects them with exclusion audiences instead. See the Microsoft Ads guide and the Meta Ads guide.