Profile_bird

Hey there! AdWordsHelper is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What's happening? Join today to start receiving AdWordsHelper's tweets.

Already using Twitter
from your phone? Click here.

AdWordsHelper

  1. New post. "Using The Ads Diagnostic Tool: Your campaign has reached and exceeded its budget for this month." http://bit.ly/4lwgz6
  2. I've posted an update in the AdWords Forum about an issue where AdWords Editor users get 'Error 211': http://bit.ly/XXozu
  3. @JohnWEllis Are you using a new feature or ad type that you just started with recently?
  4. @JohnWEllis We have a few other cases. It seems to happen when posting changes that aren't supported by the AdWords API.
  5. @JohnWEllis Sorry, I sent this over to a friend on the Editor team, but forgot to reply. Let me check in with them.
  6. @JohnWEllis That's odd. Any chance you could send me a screenshot?
  7. @vkore91 Thanks. I just wrote that list on my whiteboard.
  8. @AccuraCast Yes, that's right. There has to be at least the line of code that calls the Google ad servers for conv. tracking to work.
  9. @SFLTVBossMan In my experience, stats tend to update more slowly the further you drill in. They should match for 'Yesterday' though.
  10. @kalena Hmmmm... I don't believe I've seen that before, but I might have missed it. Let me check.
  11. @Beer_Baron We hope you get good use out of it.
  12. @AccuraCast in other words, you can insert only the server request line from the code snippet, without the Javascript.
  13. @AccuraCast Not entirely, though it's possible to track using only part of the code snippet.
  14. Something new. Weekly posts on AdWords features. This week, part one in a series on the Ads Diagnostic Tool: http://bit.ly/4bKV3O
  15. @sallymander As someone whose job it is to explain issues like this, I completely understand the desire for feature/tracking parity.
  16. @sallymander It wouldn't necessarily be useful, but I like it as a sanity check. Also, as always, rants are noted and appreciated.
  17. @sallymander Hypothetically. You could run an invalid clicks report for the date range to see if a large number of clicks were filtered.
  18. @sallymander Just a guess, but it's possible it's a spoofed user agent, and the clicks/impr were filtered as invalid.
  19. Heads up. There's a problem right now with saving custom targets in AdWords. We're working on resolving it ASAP.
  20. @michaelq If you want to DM me the CID of the MCC account, I'll see if everything looks normal.