Meta Ads
Meta has no IP exclusions. Spurn keeps flagged visitors out of your Facebook and Instagram ad sets with an exclusion audience, fed through your pixel, and imports your campaign stats.
How it works#
- Each flagged click goes to your pixel. When Spurn's final verdict on a click is invalid, Spurn sends it to your Meta pixel through the Conversions API as a custom event,
InvalidTraffic. The event carries Meta's own browser cookies (_fbpand_fbc) where your site has them, the visitor's IP address and browser, and the click's Spurn id, so Meta never counts it twice. The Spurn tag also firesSpurnInvalidTrafficin the browser when your pixel is on the page. - Spurn keeps one audience on those events. A website custom audience called Spurn: invalid traffic (exclude) holds everyone who triggered either event in the last 180 days.
- Every active ad set excludes it. Spurn adds the audience to each active ad set's excluded audiences, keeping the exclusions you already have, and checks for new ad sets every hour.
Meta treats excluded audiences as a hard rule, including in Advantage+ audience, so these people are not shown your ads.
Meta exclusion audiences are part of the Growth plan and higher, and the AppSumo Shop tier and up.
What is and is not possible#
- Meta only excludes people it recognises. A visitor joins the audience when Meta can match them to a Facebook or Instagram account. That stops click farms and repeat human fraud. A headless bot with no Meta account never joins, so for bots the protection that matters is on your other platforms and in your reports.
- Recent clicks only. Meta refuses events older than seven days. Spurn sends flagged clicks within about five minutes, so this only matters if your connection was down for a week.
- Legacy Advantage+ shopping campaigns only accept location targeting, so they cannot exclude an audience. Spurn lists any such ad sets on the account's page. Meta stopped letting apps create these campaigns, and Advantage+ sales campaigns accept the exclusion.
- No click-level report. Meta does not publish which clicks it billed, so Spurn cannot find ghost clicks in Meta. Refund claims for Meta list the flagged clicks that reached your site carrying an
fbclid, and say so. - No IP blocking. Meta has no field for it, at ad set or account level.
Connect your account#
- In Spurn, open Ad accounts and choose Connect Meta Ads.
- Log in with Facebook and choose the business portfolio, the ad accounts and the pixels Spurn may use. Spurn asks for permission to manage and read ads (
ads_management,ads_read) and to see your business assets (business_management). - Back in Spurn, your ad accounts are listed with their pixels. Enable the ones to protect and link each to the sites its ads land on.
- If an account has more than one pixel, choose the one installed on your site in the account's settings.
Before the audience can be created, someone with access to the ad account must accept Meta's Custom Audience terms in Ads Manager. If they have not, the account's page shows Meta's message and Spurn tries again within the hour.
Stats#
Spurn imports per-campaign link clicks, spend and purchases every hour from Meta's Insights reports. Link clicks are the clicks that can land on your site, so Meta's cost per click lines up with what Spurn sees.
When something goes wrong#
- "Choose a pixel". The account has more than one pixel and Spurn will not guess. Pick the one on your site.
- "Reconnect Meta Ads". The access was removed in Business Settings, or the person who connected lost access to the business. Reconnect to resume; the audience and your settings carry over.
- An ad set is listed as refused. Meta would not take the exclusion on it and Spurn shows Meta's reason. The other ad sets are still covered.
- The audience looks small. It only holds people Meta matched to an account, and audiences take a while to fill. Spurn's own reports count every flagged click regardless.