|Technical issue affecting a limited number of accounts|
Google AdWords defined ppc campaign broadcast region unable to 'save'
| 5:30 pm on Oct 29, 2009 (gmt 0)|
When creating or deleting broadcast regions for my ppc ad campaigns I am not able to save any changes. My Google AdWords account manager has verified this and says that the technical team is working on it, and that it is affecting a limited number of accounts - hopefully not yours.
| 6:38 pm on Oct 29, 2009 (gmt 0)|
Yep, I can confirm that, C7Mike.
Assuming that I am in the office at the time it occurs, I'll post again once I've heard this is resolved.
To set reasonable expectations I typically wait at least four hours after I have heard from engineering that an issue is resolved before I am willing to say it's fixed in front of thousands of folks. ;) So, quite often, someone in this forum will notice that an issue has been resolved before I ever post to say so.
| 3:33 pm on Nov 9, 2009 (gmt 0)|
AWA, do you have any updates?
From what I'm seeing on my end, I believe the issue to be partially corrected. I can define an area to advertise in, but when I save I get the error. I then refresh, like it says for me to do, and then it seems to act like the changes made it through.
Based on the numbers I'm seeing, something is still wrong, even though it shows that we're advertising in the defined area. The numbers act as if the changes to the broadcast area haven't been enacted even though the account shows the broadcast area as being enabled.
| 11:56 pm on Nov 12, 2009 (gmt 0)|
Hi C7Mike - first off my apology for having missed your follow-up question until now. And, even worse, for not having returned to this thread when the issue was resolved as I said I would in my previous post!
In any case, I have understood this issue to be fully resolved. If, after rebooting and going to AdWords from a fresh login page (as opposed to getting there from a bookmark) you still experience this, I would probably suggest contacting AdWords support with the details and ask them to take a look.
As an aside (and'data point') this issue caused a fuss in another forum on which I post - and I've heard of no further problems there since the 'fix'.