Support

Aborted ad clicks: block IPs whose clicks never load your page

On this page

An aborted ad click is a Google Ads click on your ad that Tapper registers, but your website never loads and no events are recorded. When most of the recent clicks from one IP address end this way, Tapper flags the IP with the block reason Aborted ad click.

How it works

Aborted clicks come from bots and click scripts that trigger the ad click but never render the page, and from technical problems: a slow website, a script error, or a poor connection on the visitor's side.

Tapper looks at the Google Ads clicks it recorded from one IP address on that protected entity over the last 30 days. When the IP has enough clicks to judge and most of them never loaded your page, the IP is flagged Aborted ad click. The check is the same for every account: it is not a number you set, and it skips mobile carrier addresses, where many people share one IP.

The Aborted ad clicks list on the Click limits tab of a rule set does not decide this flag. The flag comes from the check above.

In Monitor-only Tapper records the flag and excludes nothing; every free trial runs this way. Once blocking is on, the IP is excluded like any other invalid IP. See Monitor-only.

This check is separate from Suspicious ad clicks on the Detection features tab, which is one number and counts visits where the page did load. See Suspicious ad clicks and minimum seconds on site.

Check your flagged IPs

  • Open the Clicks page and filter Block reason on Aborted ad click. Many rows from a few IP addresses point to automated traffic. See The Clicks page and the visitor drawer.
  • Aborted clicks from many IP addresses at once point to your website. On the dashboard Overview, the Clicks & failed script load % card shows the "Failed load rate {x}% of Google Ads clicks"; a jump usually means a slow page, a broken deployment or a tag that stopped loading. See Check that the monitoring script is working on your site.
  • Rows that look like real customers usually mean the monitoring script is missing from a landing page or blocked by a Content-Security-Policy header. See Allow Tapper in your Content Security Policy.

Still need help?

Chat with our team and mention this article.