Exclusions and Google Ads Sync
Turn detected fraud into Google Ads exclusions
Detection is only half the job. Once ClickLens flags an IP or a placement as a source of invalid traffic, you want it stopped at the ad platform so it cannot cost you again. An exclusion rule does that. ClickLens keeps your rules and syncs them to your Google Ads campaigns.
Google Ads sync is on the Growth plan and above. Creating and viewing rules is available on every plan.
Rule types
An exclusion rule is one of three types:
| Type | What it targets |
|---|---|
ip | A single IP address that produced bot or suspect traffic. |
placement | A publisher domain or app where your ads ran against invalid traffic. |
fingerprint | A device fingerprint seen across many fraudulent sessions. Used inside ClickLens for scoring; not pushed to any ad platform. |
Rules come from two places: the daily job auto-creates rules for high-confidence bot IPs, and you can add or remove rules by hand. ClickLens can also recommend exclusions ranked by bot rate before you commit to any of them.
What Google Ads can exclude
Google Ads is the one ad account ClickLens connects to. Microsoft Ads, Meta Ads and TikTok Ads cannot be connected yet, so rules for traffic from their ads are listed in your dashboard for you to add in those accounts by hand.
| Platform | IP | Placement | Conversion adjustment |
|---|---|---|---|
| Google Ads | Yes | Yes | Retract or restate by gclid |
Conversion adjustment is a separate feature from exclusion sync. Retractions and restatements run in a measured rollout: ClickLens shows the adjustment it would make on each conversion before it changes anything in your account. Read how that works in conversion protection.
How a sync runs
- Connect your Google Ads account once, in Settings.
- Trigger a sync from the dashboard. ClickLens collects the rules that have not synced yet.
- It pushes the rules to your Google Ads campaigns, then marks each pushed rule as synced so it is never sent twice.
- You get back how many rules synced, how many failed, and any Google errors verbatim. Rules Google cannot take are reported, never silently dropped.
A daily cron also pushes newly auto-created exclusions to every connected account, so the common case needs no manual step after the first connection.