| 开发者 | stopfakeclicks |
|---|---|
| 更新时间 | 2026年11月18日 06:35 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
stopfakeclicks_load_tag filter.
No. Anyone who adds to cart or buys is trusted for good, and phones on mobile networks (where one IP is shared by many people) are never blocked.
The tag is one small script loaded asynchronously, after your page. For visits from an ad, the device check runs once, when the browser is idle after the page has loaded.
Google Ads allows up to 500 excluded IP addresses per campaign. stopfakeclicks keeps its list at the account level, capped at 500 entries, and when the list is full it removes only its own oldest entries, never entries you added yourself.
Google does not offer campaign-level IP exclusions for Performance Max, video, App, hotel and Smart Display campaigns. An account-level exclusion list applies to Search, Shopping, Display, Performance Max, Demand Gen, Discover and YouTube campaigns, and that is the list the stopfakeclicks script keeps.
No. No Google Ads login is shared and no API connection is needed. You paste a script into your own Google Ads account, authorise it there and set it to run hourly.
No. Your first 7 days are watch-only: suspicious sources are recorded and nothing is blocked.
In 7 steps: see what Google already filtered, find the paid clicks that show no person on your site, exclude their IP addresses (up to 500 per campaign), set location targeting to Presence, switch off search partners that don't sell, exclude bad placements (up to 65,000 per account) and ask Google to review the last 60 days. The full guide, with a link to Google's help for each step: How to stop fake clicks on Google Ads. This plugin does steps 2 and 3 for you.
Yes, with Google Tag Manager. The script pushes the event sfc_human to the dataLayer on the first real mouse, touch or scroll input, so you can use it as a trigger condition for your conversion tags. Keys and anything typed are never read.