Re: CampaignStats removed clicks and cost after a while
Thank you, this exactly info I'm looking for. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups AdWords API Forum group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
CampaignStats removed clicks and cost after a while
Hello all! I know about 3 hours delay, and since I'm pessimist, I query CampaignStats after at least 6 hours from previous day. However, sometimes I found that previously reported data changed, e.g. clicks/costs removed. For example, I got 67 clicks for period 2011-11-01;2011-11-20, and I queried it 2011-11-21 11:05:08.709. Currently for that company I get 66 clicks, and of course less money. It's very rare happens though, but annoying, since past-time values slightly differs from Reporting/and currently queried CampaignStats. I looked at my logs, and seems I didn't logged that answers from API, so probably can't help much to investigate this. I can provide specialist with campaign id if needed. If this is a known bug/feature, then I need to know how many hours/days I need to wait, to be sure that no clicks will be erased. Thank you. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups AdWords API Forum group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
v13 Geographical Report differs from other reports
Hello! I'm using v13 cross-client reporting, and we have problem with geo report. It shows more clicks and more money than other types of reports, and interface quick stats. We double, even triple-checked all, error persists. Here's job ids of reports, which returns different data; 2003507704 - summary report, return same clicks count as in interface; 2003413864 - geo report, return more clicks and more spents. Also, we noticed earlier that geo reports sometimes returns different conv count too. So, what info do you need more from me? -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups AdWords API Forum group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
Re: Planned Jobs Problems
No, it seems all is fine from about this morning - all reports creating, all reports downloads ok. Thanks. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups AdWords API Forum group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
Planned Jobs Problems
Hello! We using Java v13 API to make cross-client reports. Logic to plan report is such: 1. Check if there is room for report (15 queue limit) 2. If ok - validate it 3. If ok - plan it, store Job ID. 4. For each not downloaded reports, check their statuses; if status OK - download it. It works fine for hundreds of accounts (partially there is cross-client reports, while partially not). But sometimes, Report Service just don't believe our credential information. Example: ns1:code5/ns1:code ns1:messageEither this object does not exist, or this user does not have permission to access it./ns1:message ns1:triggerJob ID: 1856723944/ns1:trigger It happens not rarely, and it's have global effect, if we have such problems, then it happened not with one account, but with many. If we plan, plan, plan new feports, eventually some report is done and we can download it. Do you need any additional info? -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups AdWords API Forum group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
