Facebook and Instagram ads are bought in Meta Ads Manager, so every control here is Meta's. On Google Ads, ClickFortify adds flagged sources to the campaign's IP exclusion list. Meta offers no IP exclusion, so ClickFortify does not block IPs on Meta and does not send IP addresses to Meta. This post is part of our guide to Meta Ads click fraud.
How we checked this. No ad-account test was run. We read Meta's targeting, custom audience and Conversions API references, Meta's Business Help pages and Google's IP exclusions page on 19 November 2026, and searched each for any IP field. We rendered four Facebook Help Center pages in a browser to read what a Page block, a hidden comment and the viewer's ad controls do.
What you probably want, and where Meta handles it:
- Stop bots and fraud: score the visit, cut placements and filter conversions, as in click-level protection on Meta without IP addresses.
- Keep someone, like a competitor, out: a customer list exclusion, if you hold their email or phone.
- Keep your own staff out: the employer exclusion in Audience controls.
- Keep a country out: Locations, not IPs.
Why people expect an IP exclusion in Facebook Ads
Google Ads has an IP exclusion list; Meta's targeting, in Ads Manager and the Marketing API, has no field that targets or excludes an IP address.
How IP exclusion works on Google Ads
Google's help page Exclude IP addresses says: "You can exclude up to 500 IP addresses per campaign." It adds that "Internet Protocol (IP) Exclusions are now supported at the account level", and where both lists exist, "Google Ads will merge the exclusion lists." Some campaign types are left out: "Campaign-level IP exclusions aren't available for" Performance Max, video, hotel, App and Smart Display. See how Google Ads IP exclusions work and the 500 IP exclusion limit.
Why you cannot exclude an IP address in Meta Ads
Where IP appears in Meta's references, it is never an exclusion:
- Targeting spec. The only IP mention in Basic Targeting concerns a person's home location: "Facebook validates this by IP". That is Meta placing people, not you excluding addresses. The spec uses
excluded_geo_locations"to exclude areas"; no exclusion field takes an IP. - Customer lists. Meta's Customer File Custom Audiences guide lists email addresses, phone numbers, names, dates of birth, gender, locations, app and Page-scoped user IDs, and mobile advertising IDs. No IP identifier is on the list.
- Conversions API. In the Conversions API,
client_ip_addressis one of the customer information parameters, and Meta says it "must never be hashed". It helps Meta match a server event to a person. It excludes no one.
Our reading, not Meta's: Meta delivers ads to Meta accounts, so its exclusions are people, places and placements.
Even if Meta had one, an IP list would miss. Our reasoning: shared addresses, VPNs and residential proxies make IP lists block real people and miss rotating bots; see why IP blocking fails against residential proxies.
Each thing you might want to block, and the Meta control that handles it:
| What you want to block | Meta Ads | Meta control to use |
|---|---|---|
| An IP address or a list of IPs | No | None; client_ip_address is only a Conversions API matching key. Google Ads, by contrast, allows up to 500 IP exclusions per campaign |
| Visitors on a VPN or proxy | No VPN or proxy setting | None; score the visit on your own landing page |
| A country, region or city | Yes, by the location Meta assigns a person | Locations in the ad set; the location control in Audience controls |
| Someone, such as a competitor | Partly, if Meta matches their details | Customer list or exclusion-only custom audience, excluded in the ad set |
| Your own staff | Yes, by employer | Audience controls, employer exclusion |
| Interests and behaviours | Exclusions removed from January 2025 | A brand protection selection only, in Audience controls |
| Bad apps and sites | Yes | Placement controls; publisher block lists |
| Visitors you flagged on your own site | Only if Meta matches them to an account | Website custom audience from a Pixel event, excluded in the ad set |
| Clicks the platform finds invalid | Not charged | Meta's own filter |
Sources: Google's Exclude IP addresses page and the Meta pages linked here, read 19 November 2026.
What Meta offers instead of blocking IP addresses
Meta's exclusion controls fall into four groups: account-level Audience controls, locations, custom audience exclusions and placements.
Account-level Audience controls, including the employer exclusion
Audience controls in Advertising settings set exclusions for the whole ad account: countries, a minimum age, brand protection exclusions and your own employees. Meta says it is "gradually introducing this feature", so it may not be in your account yet.
Meta's page Set audience and placement controls gives the path: "Go to Advertising settings." then "Click Audience controls." Countries can be included or excluded singly or as country groups, and for brand protection Meta now offers "only a selection for brand protection".
For staff, toggle on "My business doesn't show ads to its own employees", then pick the employer under "Exclude people who match". The controls "will be applied to all existing campaigns in your ad account".
In our reading, that brand protection selection is what remains of detailed targeting exclusions, and Meta began removing them in January 2025. Its developer blog post Removal of Detailed Targeting Exclusions, dated 21 January 2025, said "we are removing Detailed Targeting exclusions" and kept employer exclusion "within Audience controls at the account level".
In the ad set, Advantage+ audience has its own audience controls, separate from the account-level ones: "You can choose Locations, Minimum age, Custom audiences to exclude and Languages" (Audience controls in Advantage+ audience).
Locations in the ad set
Location exclusion follows the current or home location Meta assigns a person; in our reading, you cannot exclude a network. Per About location selection, someone living in an included location "may see your ad while visiting an excluded location". For the steps, see why Facebook ads get clicks from other countries.
Custom audience exclusions
A custom audience exclusion keeps people Meta can match out of an ad set. Meta's Advanced targeting reference allows "500 custom audiences in excluded_custom_audiences". Three types:
- Customer list. It matches details "such as email or phone number used to match customers to profiles" (About customer list custom audiences).
- Exclusion-only custom audience. A customer list type that "can only be used to exclude people from your ad audience"; "you cannot change it to a regular custom audience" later (About exclusion-only custom audiences).
- Website custom audience. Built "based on events from your Meta Pixel", with rules such as "People who visited specific web pages", "up to 5 rules" per audience, and "it won't backfill" (Create a website custom audience).
Placement controls and publisher block lists
Placement controls and publisher block lists are Meta's substitute for an IP list against bad apps and sites. On Audience Network, Meta's Placement targeting reference lets you exclude a custom list of "app store URLs or domain URLs". Publisher block lists live in the Meta Brand Safety and Suitability Center, where viewing partner-publisher lists needs a business portfolio (Create a publisher block list).
For Sales, Leads and App promotion, Meta says "the option to make placement selections is removed in ad sets" (Choose ad placements), so use Placement controls in Advertising settings. Exclusions may not be total:
- Meta's help page, read 19 November 2026. Per limited spending on excluded placements, Meta may spend "a total of up to 5% of your budget on excluded placements".
- The older wording differs. Meta's developer blog of 8 October 2025 said up to 5% "for each excluded placement".
For the steps, see how to exclude Audience Network.
Can you block someone, like a competitor, from seeing your Facebook ads?
As the advertiser, you can exclude one person only if you hold their contact details and Meta matches them to an account; nothing on Meta guarantees it.
- Customer list or exclusion-only custom audience. Add their email or phone and exclude it in the ad set. Our reasoning: a person on an email Meta cannot match, on another account or logged out can still see the ad.
- A company's staff. Use the employer exclusion in Audience controls.
- A Page block does not list ads. Per How to block or unblock profiles from your Facebook Page, a blocked profile or Page "can no longer:" see your Page posts, tag your Page, invite it to events or groups, message it, or find it in search, and a blocked follower is removed. Ads are not on Meta's list of what a Page block stops.
- Hiding a comment hides only that comment. A hidden comment stays "visible to the person who wrote it and their friends".
- Viewer controls belong to the viewer. Why am I seeing ads from an advertiser on Facebook? describes Hide an ad and Advertiser choices, which the person seeing your ad uses, not you.
If a competitor is clicking, see how to stop competitors clicking your ads.
A traced example, an illustration and not an account we tested. An advertiser moves from Google Ads to Meta with an IP exclusion list and one competitor's email from an old enquiry. The IP list has nowhere to go: no targeting field and no customer list identifier takes an IP. The email goes into a customer list excluded in the ad set, and works only if it matches the competitor's Meta account. Its bot clicks are handled on the page and in conversions, below.
How click-level protection works on Meta without IP addresses
Without IP exclusion, protection moves from the address to the visit, the audience, the placement and the conversion.
Score the visit on your landing page
ClickFortify recognizes Facebook and Instagram ad clicks by their fbclid and scores each visit that loads your landing page on 100+ device, network and behavior data points. Signals include device characteristics, data-center, proxy and VPN origins, and on-page behavior. Each flagged visit is kept as a click record in the dashboard, which also flags three suspicious-conversion patterns: a conversion within 2 seconds of the click, one from a visitor already classified as a bot, and a device with 3 or more conversions. On Meta these flags drive conversion filtering and placement actions, not IP blocks.
Build an exclusion audience from flagged visitors yourself
You can exclude flagged visitors only through a website custom audience you build yourself, and only visitors Meta matches to an account join it. If your site logic marks a visit as suspect, for example with a custom Pixel event or a page only flagged visits reach, build a website custom audience on it and exclude it in the ad set. The limits:
- Only matched accounts join. Meta's rule reads "Include Meta Accounts who meet" the criteria. Our reading: a visitor Meta cannot tie to an account never joins, nor does a bot without one.
- No history. The audience starts empty and fills from the day you create it.
- A tradeoff. Firing a Pixel event for a suspect visit also sends that visit to Meta (our reading).
Some IP-blocking tools for Meta do this automatically. That is an audience exclusion, not an IP block. ClickFortify does not build or push audience exclusions. Our judgment: worth it for repeat humans you can match, weak against bots.
Send Meta only filtered conversions
Meta's delivery learns from the conversions you send. When the CAPI proxy is enabled, conversions sent through ClickFortify are checked against the visitor's fraud score, and flagged events are dropped or tagged before Meta receives them. The proxy filters the server events sent through it; events your pixel fires in the browser still reach Meta.
If a bot's server copy is dropped, Meta still receives the browser copy, which can count. Meta's page Deduplicate pixel and server events says "we generally prefer the event that is received first". For setup, see fraud-filtered conversions through CAPI.
Cut the placements where bad traffic concentrates
When fraud is detected on an ad set, ClickFortify can switch off Audience Network on that ad set automatically. This is opt-in and enabled per ad account. ClickFortify pushes flagged publishers to Meta's publisher block list, so the apps and sites behind bad traffic stop receiving your ads where Meta applies that list. See Audience Network fraud protection.
What no IP-blocking tool can do on Facebook ads
No tool, ours included, can write an IP exclusion into Meta, because Meta has no field that excludes an IP address.
- No IP exclusion. No tool can exclude an IP or IP range on Meta, or send Meta IPs to exclude.
- No pre-click block. Tools act after the click reaches your page, not before Meta serves the ad.
- No unseen clicks. A click that never loads the page is invisible to any on-page script.
- No Instant Forms. They never load your page, so validate them in your CRM; see fake leads in Facebook lead ads.
- No filtering after the Pixel fires. Events the Meta Pixel fires in the browser still reach Meta; the CAPI proxy filters only the server events sent through it.
- No guaranteed credit. Meta's invalid clicks page counts clicks from "fake accounts, bots, scrapers, browser add-ons" as invalid: "You will not be charged for clicks that are determined to be invalid". Meta publishes no catch rate. See whether Meta credits invalid clicks and invalid traffic.
Claims that a tool blocks single IPs on Facebook describe no setting Meta documents. Such tools build audiences, cut placements or filter conversions; ask which of the three. To keep your own staff out, use the employer exclusion in Audience controls, not an IP.
What ClickFortify does on Meta, and what it cannot
ClickFortify does not block IPs on Meta and does not send IP addresses to Meta. It also does not create audience exclusions. On Meta it scores landing-page visits, flags suspicious conversions, filters the server events sent through the CAPI proxy when enabled, can switch off Audience Network on ad sets with detected fraud (opt-in per ad account), and pushes flagged publishers to Meta's publisher block list. The proxy filters the server events sent through it; events your pixel fires in the browser still reach Meta. See ClickFortify for Meta Ads.
Checklist: what to set up on Meta, in order
To protect Facebook and Instagram ads without IP blocking, start with the controls that apply to every campaign, then work down to conversions.
- Set Audience controls: locations, minimum age and the employer exclusion.
- For Sales, Leads and App promotion, use account-level Placement controls; the Audience Network guide linked above covers limited spend.
- Add a publisher block list for apps and sites that send junk.
- Exclude known bad actors with a customer list or an exclusion-only custom audience.
- Score visits on your landing page and review flagged click records.
- Send Meta filtered conversions through the Conversions API, knowing pixel events still reach Meta.
- Report suspect clicks to Meta with click-level evidence; expect a credit only for clicks Meta finds invalid.
The verdict on blocking IP addresses in Facebook ads
Stop looking for an IP setting on Meta: put the effort into conversions and placements first, and use audiences for people you can name. A flagged-visitor audience suits repeat humans Meta can match, not bots. A tool sold as IP blocking on Meta gives you audiences, placements or conversion filtering at best.
No ad-account test was run. Meta publishes no invalid-click catch rate, so we give none. The ad-set placement change and account-level Audience and Placement controls are being introduced gradually. For every related guide, see all Meta Ads fraud guides.




