Forum Moderators: martinibuster
As mentioned last week, I'll start to collect your feature requests on a weekly basis, and communicate them to the relevant teams.
I look forward to hearing your ideas,
ASA
Fear of being unjustly booted without any recourse is one which I suspect a lot of publishers share
not till you've mentioned it :-)
prompt and meaningful communication.
A good place to start would be during events like the current issue/problem with advanced reports in the AdSense stats that seems to be affecting at least some publishers [webmasterworld.com].
Maybe I just missed it.....
prompt and meaningful communication.
I'll second that.
Maybe it would be constructive to start with "meaningful communication" within this thread here and now. If the ideas we are suggesting are going to be rejected, please communicate and elaborate as much as you can.
For example: Our suggestion to extend the competitive ad filter (so that we may tackle the MFA problem) was rejected without any real or meaningful dialogue. It would save us much time if the reasons for your rejection for a bigger filter were clearer. Is it because Google doesn't want publishers to block sites perceived as spam, low paying, or MFA? So do we forget about wasting our time and your time suggesting 101 alternatives to tackle MFA, because Google doesn't acknowledge an MFA problem?
On the other hand, if your response was along the lines that Google is not prepared to extend the competitive ad filter... BUT it was willing to hear other suggestions on the issue of garbage ads and MFA, then I'm sure many of us here would be more than happy to continue to submit further suggestions on this particular issue.
CONSISTENCY - Other than inconsistency!
Without a doubt Google is my most unreliable business supplier ever, thank heavens I do not have to rely upon them for anything to do with my real-life, bricks and mortar businesses.
They would have been sacked/disposed of years ago!
That's all that I want............
I understand that you are keen to receive updates on the status of your requests. All will be presented to the relevant teams for review. While I cannot comment on which requests we are already working on, or which will be prioritized, please know that we appreciate and take on board all of your valuable feedback.
Would you take note of this thread [webmasterworld.com...] when presenting information to the relevant teams for review?
Thanks,
FarmBoy
While I cannot comment on which requests we are already working on, or which will be prioritized, please know that we appreciate and take on board all of your valuable feedback.
Why not ASA ?
I fail to see why. What would be the big secret say, if you were increasing channels ?
It would be good for you in terms of PR and openness.
It would give us more confidence, hope and reassurance that things are not going on deaf ears.
Learn to work with not against the beast, the bigger it is the slower it moves and the less mistakes it can afford.
- Your next question would be when is it coming out.
I doubt it, esp if some kind of rules were applied.
But, what are we getting now ? ... people month in, month out asking for the same thing. Just leads to frustration.
- They do it and in testing discover a quirk or a reason they're better off without it.
Most of these requests are simple things to do.
- While developing the feature something else comes up and gets higher priority.
But ASA could inform us of such things. People *are* understanding when told of problems. People hate being given the mushroom treatment. [kept in the dark and fed BS]
All the above would mean even more disgruntled cranky publishers.
Not at all. People don't mind waiting IF they know it is coming. Less frustation to start with, and more respect is earned.
Learn to work with not against the beast, the bigger it is the slower it moves and the less mistakes it can afford.
Looking at some of google's bugs, it looks like they were one of he beasts that were small and fast ;)
