Recently, maybe 2 weeks ago, I started being bombarded by the..lets see if I can find it..o wait it just happens to be displaying on aw right now: "Your latest changes were not processed.
Please note that you may not click your browser's 'Back' button to edit settings you've already saved through the wizard. If you'd still like to revise your campaign or Ad Group, you may continue from this page."
After 2 weeks of frustrations, loss of productivity, and attempts to resolve the issue with AW reps I am going to post here and ask if anyone else has seen an *insanely* high level of these messages WHEN doing absolutely nothing wrong in terms of browser navigation.
AW makes good $en$e in terms of ROI so I would use it regardless of errors and additional problems. However, I think it does something to your thoughts of AW when frustration levels reach high. I cannot express the level of dissatisfaction I have when I cannot develope at my own rate or be thrown through tangent problems in the middle of my work.
AWA, can I try to put this in perspective? Please do your best to really put yourself in my scenario:
-Let's say 20% of the time you come to WW and you create posts, you loose data. You cannot fix the problem and the mods can't/don't really help you. You begin making your posts in MS Word and feel that helps in some ways. Keep in mind, you are loosing *some* productivity here..
-Let's say now when you go and create your weekly advertisers feedback report, the program you use to compile your report haults and outputs errors stating you *did* something that you in fact did not. You followed the rules perfectly and even humored the help files recommendations of bogus actions. Still, many many times your reports are completly lost. You start doing things differently to counter the massive losses of data.
Now, sure you have countered the issues as best you could by using alternative methods of preperation and execution. The key thing here is you have lost a significant amount of time across the board as a result. IE: You now have less time to spend focusing on your mission/goals/objectives because you have to do so much busy body work to compensate for the problems.
I will put this into perspective by stating when another (similar paying) position opens at G that allows you to do the things you like without the frustration that busy body tasks bring, it *might* have more appeal. Now, as an advertiser, can you see how our thoughts and actions might parallel to some degree?
AWA. Just curious, do these types of errors build logs that engineers look at? Maybe they already know about this issue, but if not, I think error logs would possibly show the increase in errors I am talking about?
If I created a program that compiled basic log stats of my paths through aw and the number of times I receive this error as a percentage compared to the total number of times I do not, would you be interested in seeing my results?
Perhaps this is an error due to creating so much, so quickly? I build these campaigns, adgroups, and kw/kp's like they are on fire. Could this be why I get the error SO frequently? Does the system think I am a bot?
Back to ErrorWords...
I hear from lots of people here in Germany who have the same problem, but not so frequent.
- Jan
When I receive the error messages (very infrequently on most days, if I get one, then I'll usually get a lot in a single day), about half the time I can hit the back button and then submit or whatnot again and it goes through just fine.
Complaining with the help desk didn't help so far, the standard answer is: empty cache, start new browser, reboot. As if we have nothing else running at the same time.
Honestly, though, I have to say that I haven't noticed an up-tick in emails regarding this sort of thing - and I'm in the practice of scanning several hundred advertiser emails daily, from advertisers at all levels of experience, specifically to spot such trends.
Complaining with the help desk didn't help so far, the standard answer is: empty cache, start new browser, reboot. As if we have nothing else running at the same time.
The reason this is the standard answer is that it usually solves the problem, which almost invariably turns out to be a matter of the interaction between the advertiser's machine, and the AdWords UI. I certainly understand the frustration, though, and will pass your comments on.
AWA
"Sorry you have to reboot your system before you can order this item. Your last additions to your card have been discarded. Oh, and if you decide to retry, don't even think to look back or have second thougts about what you've just seen, and don't answer the phone while you are ordering." How does that sound? That is basically how AdWords work.
Sorry for ranting, but this happens about 20-30 times a day. It is also the first complaint I hear from new people assisting me.
Anyway, I've just re-read your first post, and want to assure you that I've understood your point, and can absolutely understand your frustration.
You too, HitProf.
I've just pasted comments from this thread into the report, and will also personally bring up the topic at an upcoming meeting.
AWA