Businesses that pay for Google Ads clicks
From a sole trader to a large advertiser: set the rules once, and ClickShield applies them to every click on your ads.
ClickShield recognizes devices that keep clicking your ads and excludes their IP in your Google Ads campaigns, automatically and only while the ban lasts.
Ad click
gclid demo-a4IP 203.0.113.24
4th click from this device in 5 minutes
| Device | Visits | Status |
|---|---|---|
| Qx7fK2mR…now | ||
| Lp5GvX2c…17 minutes ago | ||
| b8MsR3yZ…40 minutes ago |
| IP address | Added by |
|---|---|
| Campaign: Search · Services | |
| 203.0.113.24 | ClickShield |
| 203.0.113.91 | ClickShield |
A fake click is a click on a paid ad with no customer behind it: the same device clicking again and again, a bot, a competitor or anyone else.
Google Ads charges for the click, not the intent. Every such click spends budget you meant for real customers.
Google Ads already filters out some invalid clicks on its own. ClickShield adds rules you set on top: how often a device may click, and how long it then stays out.
Sample: one device, 4 paid clicks in 5 minutes
Three steps. Once it’s set up, ClickShield works on its own.
Add the domain your ads lead to and paste the same line into the <head> of its pages.
www.example.test
<script async src="https://clickshield-web-370434332956.europe-west4.run.app/cs.js"></script> The same line for every domain you add
Fingerprint Pro recognizes the device. A click beacon arrives even before that, so ClickShield also counts visitors who leave before the page loads.
When a device goes over your limit, ClickShield excludes its IP in your linked campaigns, and lets it back in when the ban ends.
after 1 day
You set the rules per pool of domains, and ClickShield applies them in the Google Ads campaigns you link to that pool.
Defaults, set per pool.
A device that clicks more than 3 times in 5 minutes, or more than 10 times in 24 hours, gets banned.
Its latest IP is then excluded from the campaigns linked to the pool.
A ban lapses, but the offense stays on record. A device that comes back and overdoes it again stays out longer.
These are defaults, and each pool can change them. You lift a permanent ban yourself, whenever you like.
Every ad click is recorded with its time, gclid, landing page, IP and how the page was opened.
Reloads, the back and forward buttons and pages restored from the browser cache are recorded, never counted.
Sample: one device’s record
You link Google Ads campaigns to a pool. ClickShield adds its own IP exclusions to them, and removes each one at the next sync after its ban ends.
ClickShield never touches exclusions you added yourself in Google Ads.
| IP address | Added by | Status |
|---|---|---|
| 203.0.113.91 | ClickShield | Sent |
| 192.0.2.57 | ClickShield | |
| 198.51.100.23 | You, by hand | Stays |
One Google Ads connection reaches every account you manage, and pools group your domains, by client for example. That makes ClickShield a fit for agencies too.
Sample: domains by pool
ClickShield and this page speak Croatian, English, German and Spanish.
Sample: the same status in four languages
The script can wait for your cookie banner and start only once the visitor agrees. Mention ClickShield in your privacy notice.
In the page’s <head>
<script async src="https://clickshield-web-370434332956.europe-west4.run.app/cs.js" data-consent="wait"></script> Once the visitor agrees
(window.ClickShield = window.ClickShield || []).push('consent'); The Overview shows how setup stands, your ad clicks, the devices currently excluded and the exclusions waiting to go to Google Ads.
From a sole trader to a large advertiser: set the rules once, and ClickShield applies them to every click on your ads.
Your clients’ domains and Google Ads accounts sit under one account, and each pool has its own rules and campaigns.
You set up the domain, the pool, tracking and Google Ads yourself. Tracking takes one line of code on your site.
Add your domain
The website your ads send visitors to.
Prove you own it
One DNS record proves the domain is yours. Until it is verified, ClickShield accepts none of its traffic.
Add it to a pool that flags new devices
The pool’s visit limits decide which devices are flagged.
Install tracking
One script line puts the click beacon and the Fingerprint agent on your ad landing pages.
Connect Google Ads
Sign in with Google so ClickShield can send exclusions to your campaigns.
Link campaigns
The linked campaigns then exclude a flagged device’s latest IP, so their ads stop showing to that IP.