S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | |||
5 | 6 | 7 | 8 | 9 | 10 | 11 |
12 | 13 | 14 | 15 | 16 | 17 | 18 |
19 | 20 | 21 | 22 | 23 | 24 | 25 |
26 | 27 | 28 | 29 | 30 |
Thwarting Adblockers
When I started tracking adblockers on my site I didn’t have much of an intuition how common adblockers were, or how much it was affecting my bottom line. As a one person company, I have limited time to throw at any one problem so these types of questions always warrant an investigation to see if it’s worth my time and effort. If ad blockers were used by a small enough percentage of my audience, I would ignore the issue and focus on writing new apps.
Initially I came up with an arbitrary threshold of an acceptable amount of ad blocking. As long as adblocking was less than 15% of my traffic, my bottom line would remain mostly intact. Actually, the first number in my head was 10%, but I bumped it up after it appeared 12% of my ads were being blocked. There was no real reason behind either number, just intuition. The first time the percentage of blocked ads rose above 15% I decided to look the other way. Maybe 17% was a more reasonable number. Than I had my first 20% ads blocked day, followed by my first 40% day, and finally a day over 50%. The bandwidth I was paying for to host the webapps was costing me more than the money I was earning from them. Forget earning money, it was costing me money! Ignoring the problem was no longer an option.
Thankfully my Ad blocking detection script was generating a fair amount of data. I had replaced those “console.log” calls with google analytics event recordings, so I could generate a fairly extensive profile of just who was using adblockers.
I wasn’t surprised to see that adblocking was more common on desktop than mobile browsers. I think that’s pretty common knowledge these days. What caught me off guard was the stark divide between weekend behavior and weekday behavior. Even accounting for browser type, adblocking was nearly non existent on the weekends. Digging further I learned some corporate networks block ads as a matter of policy.
Penalize the user for their network administrator’s policy didn’t seem like the right course of action. Yes, blocking ads are against my terms of service, but what choice did they have? They have no control over their coprorate’s network policy and I’m more likely to incure their ire than get any positive benefit from blocking them. I opted to go a different route.
I opted to show different, unblockable ads that address many concerns that advocates of adblocking raise.
When google adsense is blocked, I now serve static image & text ads to Amazon. Because the only javascript running is javascript I wrote, rather than a third party script, there is no additional security concern. Nor is their an extra strain on resources beyond what running my apps would cause anyway. No third party involvement also means no additional privacy concerns. The new ad policy that addresses the objections of most people who use ad blockeres. That sounds like a win-win in my book!
If you want to see the Amazon ads used, but don’t have an adblocker, you can always check them out here. As always, I welcome feedback.
Posted in Internet & Technology, Work Life | Tags: Adblocker, Sarahsoft
Leave a Reply