Double Click Penalty - The Tell

[levo]

Finally I've stumbled upon a website with the double click penalty - I was trying to report the ad that was covering the content and noticed the confirmation box.

If you want to check if you got the penalty, right-click the ad, click inspect, and check if the ad code has the following part.

<div [class]="confirmedClickVisible ? 'visible' : ''" dir="ltr" id="common_15click_overlay" on="tap:AMP.setState({confirmedClickVisible: !confirmedClickVisible})" role="button" tabindex="0"><div class="common-15click-dialog"><div class="dialog-msg">Visit Site</div><div class="dialog-buttons"><div class="dialog-cancel"><span>No</span></div>

The keyword to look for is 'confirmedClickVisible'

[tangor]

Interesting!

Just curious why disabling the ad, killing js temporarily were not done. I say this from the stand point of g should know their biz and really don't need ME to supply examples that break their rules. :)

[ronron]

I had many problems with the double click penalty in the past two years. In my situation, I fixed the issues that was causing it, and have not experienced the double click penalty since (almost a year without).

1) Rare instance where the double click penalty was applied, right after a huge DDOS spike in traffic from Opera Mini proxies. What I'm guessing happened was a clickbot(?) or some automated software clicking and triggering Googles defenses. To fix this, I use CloudFlare to block proxies in general. A lot of ASN blocks, but it works for me.

2) Label "Advertisement" on all ads. On mobile scrolling down a page, an ad without a label can easily look like page content. Putting a label likely appeased the Google gods.

[matbennett]

It's a definitely tell in that if you see it you have the issue. But you can also have the issue without seeing it too. The click-confirmation behaviour is not always applied to every impression