Agreed. At the current rate, it would take a mighty long time to earn even one gold, let alone enough to cover any monthly obligations. Hope this is only a temporary phenomenon and not an omen of things to come.
Seems like regional differences. I've made 10 gold already this month with little effort with snickers, citibank, ebates, land rover and some other ads. Some dry spells but the ads return after a short break.
Of course we'd all like more consistency and higher paying ads.
Lots of big holidays coming up which usually bring more ads... Thanksgiving, Black Friday, Halloween, Christmas etc.
Hopefully things turn around for those struggling. It is not good for everyone if people are unhappy.
I had time to swipe a little last night for the first time in several days-- and expected to see the dearth of ads that has been mentioned during that time. I saw plenty of ads, ranging from 2-15 silver. No annoying problems other than the surveys my phone won't load, and everything credited. I'm in the midwest. (But I only swiped for a short time......)
@mmfacemm, thanks for your reply. I'm pleased to report that the "ad drought" was indeed a short-lived phenomenon and I have been getting a good number of 15-pointers again. So, problem solved and thanks again.
My current gripe isn't the decaying value of a swipe, but the decaying value of a second......
A lot of the long video ads have a countdown timer. Some even identify 'seconds', and nearly all seem to count down seconds even if not notated as such.
But... a Empires & Puzzles video game ad (by Ad Choices) seems to use devalued seconds in the timer. I'm not sure what 20 'units' they're using to indicate countdown timing, but it regularly takes 60 seconds for those 20 'units' to count down. The ad does pay, but nowhere near what a 60 second ad should pay.
I noticed the same thing with Empires and Puzzles, and the only workaround I figured out was to play the game (not download it, just swipe or select the right game pieces, if I recall correctly), which started that countdown clock again each time. That shortened the "20" seconds to under 30, anyway.