Hi Greg, Thanks for taking the time to provide feedback on why this change was problematic for you. I'll pass this along to the reporting team so they keep this in mind for any future changes.
Best regards, Josh, AdWords API Team On Tuesday, July 21, 2015 at 10:57:56 AM UTC-4, GregT wrote: > > Hi, Josh. > > We were also hit by this, as we use reports like this to download > structure, and it unfortunately has caused us a lot of trouble due to our > system thinking that all of the negative keywords in all our clients' > campaigns were gone. I just want to point out for the future that changing > something to behave as intended without announcing it in advance is > probably a fine thing if it's only been released a couple days and no one's > using it yet. In this case, it's literally been years that this report has > behaved this way, so changing its behavior to what was intended when first > released years ago without advance notice really causes problems -- whether > documented or not, actual behavior becomes expected behavior for a public > API when it behaves in a certain way for a long time. In this case, what > would have been a couple minutes to fix the code had we known in advance > has caused us additional hours of cleanup. > > Thanks, > Greg > > On Monday, July 20, 2015 at 2:47:00 PM UTC-5, Josh Radcliff (AdWords API > Team) wrote: >> >> Hi Giles, >> >> That change went into effect around July 10th. There wasn't an >> announcement because we were making the reports behave as intended -- that >> is, they were supposed to exclude negative keywords unless explicitly >> requested. >> >> Cheers, >> Josh, AdWords API Team >> >> On Monday, July 20, 2015 at 11:56:10 AM UTC-4, Giles Bodger wrote: >>> >>> Thanks Anthony, >>> >>> can you tell me from what date that happened? (we will need to re sync >>> some data fro that date), and also was there any notification anywhere that >>> we missed ? >>> >>> cheers >>> >>> On Monday, July 20, 2015 at 3:23:41 PM UTC+1, Anthony Madrigal wrote: >>>> >>>> Hi Giles, >>>> >>>> The recent change to the Keywords Performance Report was made so that >>>> the report would be more consistent with the user interface. Like you >>>> said, >>>> you can use the predicate *isNegative IN [true, false] *to include >>>> negative keywords in your report. >>>> >>>> Regards, >>>> Anthony >>>> AdWords API Team >>>> >>> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/4c87e855-264e-4647-9070-7d3275a571cf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
