Hello Zweitze, Indeed, nothing has changed. Trying to filter on UNKNOWN is an intentional error case. I have asked them to change the HTTP code to something more meaningful, but they have not implemented such a change yet.
No useful results will be in the UNKNOWN status. The "incompatibility with your WSDL version" does not mean from an older version of the API, but rather something that doesn't fit into the API framework at all. These are not meaningful to users. It is there as a precaution only, just in case something goes wrong. We double-checked the existence of any such items when you brought up this issue. You needn't worry yourself with the UNKNOWN status. I haven't ever seen results being left out because you *didn't* use a filter. You can still filter on all statuses other than UNKNOWN, but in practice, filtering on all values should have the same practical effect as not having a filter at all. If you are able to reliably produce results that act otherwise, I will gladly forward your findings to the team so they can investigate and fix the cause of the discrepancy. Regards, Mike, AdWords API Team On Wednesday, February 4, 2015 at 10:41:45 AM UTC-5, Zweitze wrote: > > Michael, > > First, the 500-error still appears when you include UNKNOWN in the > predicate. It appears that nothing is changed. > > Second, according to the docs > <https://developers.google.com/adwords/api/docs/reference/v201409/CampaignService.CampaignStatus>, > > when the software is using an "old" version of the API, the API may return > UNKNOWN. So, in my understanding UNKNOWN is used for all campaigns that are > not supported by the API. So I would think that in the future the API will > report campaigns not supported by this version, but only with status > UNKNOWN. If that is not the case, how should I interprete the statement in > the docs? > > Third, you suggest not to set a filter to get all statuses. However, > multiple times we've seen issues where *not* including a status on all > values results in inclompete reports - usually deleted items were left out. > Even AdWords API Team members suggest to always include a predicate > filtering on all possible status values. > Well, that was the past and now you suggest a completely different > approach. Is this a recent change? Do you know an article on the Developer > blog confirming this new behaviour? > > Thanks in advance! > > > On Monday, January 12, 2015 at 2:34:35 PM UTC+1, Michael Cloonan (AdWords > API Team) wrote: >> >> Hello Zweitze, >> >> Those campaigns will not return at all, even if you were able to return >> campaigns with an UNKNOWN status. Currently, the Adwords API does not >> support video campaigns, which means that those results are also excluded >> from reporting. If you don't filter on Status at all, then you will get all >> results from all statuses. >> >> I'll follow up on the bug I filed to try to get a more useful error >> message for this case, but you should be able to just remove that predicate >> and things will work fine. >> >> Regards, >> Mike, AdWords API Team >> >> On Monday, January 12, 2015 at 7:11:09 AM UTC-5, Zweitze wrote: >>> >>> Well, I'm curious about those campaigns too. Note that current >>> implementation prevents me from getting them, so, I cannot get those >>> campaigns. >>> >>> Anyway, take 279-999-6021. It has a video campaign. Now, leaving out the >>> predicate on status UNKNOWN means that all campaigns except the video >>> campaign is returned. So I assume that with UNKNOWN I will get those >>> campaigns. >>> >>> Further you suggest to leave out that particular status in the >>> predicate. Indeed we do that now, but we like to make sure we get >>> everything. >>> >>> >>> Thanks! >>> >>> >>> On Thursday, January 8, 2015 at 10:09:30 PM UTC+1, Michael Cloonan >>> (AdWords API Team) wrote: >>>> >>>> Hello Zweitze, >>>> >>>> If you know of any campaigns or ad groups that have the 'UNKNOWN' >>>> status in your account, can you please provide me their IDs so that the >>>> engineering team can take a closer look? If you aren't aware of any >>>> specific items, then you should be safe leaving out the predicate on >>>> 'UNKNOWN' values, which would hopefully solve the issue. >>>> >>>> Regards, >>>> Mike, AdWords API Team >>>> >>>> On Tuesday, December 30, 2014 at 6:18:53 AM UTC-5, Zweitze wrote: >>>>> >>>>> Any progress? >>>>> >>>>> On Tuesday, December 9, 2014 3:15:28 PM UTC+1, Michael Cloonan >>>>> (AdWords API Team) wrote: >>>>>> >>>>>> Hello Zweitze, >>>>>> >>>>>> I was also able to reproduce this. I will file a bug with the team >>>>>> and let you know when I hear more. >>>>>> >>>>>> Regards, >>>>>> Mike, AdWords API Team >>>>>> >>>>>> On Tuesday, December 9, 2014 4:26:30 AM UTC-5, Zweitze wrote: >>>>>>> >>>>>>> Yes, >>>>>>> >>>>>>> This is happens all the time - reproduction should be no issue. I >>>>>>> also found out that groups now have a status "UNKNOWN" as well, and the >>>>>>> same problems arise - including the HTTP 500. >>>>>>> >>>>>>> Zweitze. >>>>>>> >>>>>>> >>>>>>> On Monday, December 8, 2014 9:16:59 PM UTC+1, Michael Cloonan >>>>>>> (AdWords API Team) wrote: >>>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> Are you consistently getting 500 errors when using UNKNOWN in the >>>>>>>> predicate? If so, I will file a bug with the team, as even if this is >>>>>>>> an >>>>>>>> error case, an HTTP 500 error is not the right way to indicate that. >>>>>>>> >>>>>>>> Regards, >>>>>>>> Mike, AdWords API Team >>>>>>>> >>>>>>>> On Monday, December 8, 2014 3:04:30 PM UTC-5, Zweitze wrote: >>>>>>>>> >>>>>>>>> I found it. Apparently you cannot use value "UNKNOWN" for a >>>>>>>>> predicate on Status. >>>>>>>>> >>>>>>>>> But I need those campaigns too. As I recall, when you leave out a >>>>>>>>> predicate on Status, your results may get filtered on certain status >>>>>>>>> values. This happened in the past (remember the 'automatic' filters >>>>>>>>> on >>>>>>>>> creatives etc.) and I never got word that the issue with auto-filters >>>>>>>>> was >>>>>>>>> resolved. So I need to include this predicate. >>>>>>>>> Mind you, if I add a filter with all predicate values *except* >>>>>>>>> "UNKNOWN", I would assume that campaigns with status "unknown" will >>>>>>>>> be left >>>>>>>>> out from the result. I don't want that. >>>>>>>>> >>>>>>>>> According to the documentation, "UNKNOWN" is a valid predicate >>>>>>>>> value, and "unknown" is a valid display value. So the documentation >>>>>>>>> is >>>>>>>>> wrong and/or the implementation is wrong. >>>>>>>>> How do I go on from here? How can I get campaigns with status >>>>>>>>> "unknown"? >>>>>>>>> >>>>>>>>> Thanks in advance! >>>>>>>>> >>>>>>>>> >>>>>>>>> On Monday, December 8, 2014 6:37:17 PM UTC+1, Zweitze wrote: >>>>>>>>>> >>>>>>>>>> Hello, >>>>>>>>>> >>>>>>>>>> At development of the v201409 migration I noticed this error on a >>>>>>>>>> report of type CAMPAIGN_PERFORMANCE_REPORT. The error happened four >>>>>>>>>> times >>>>>>>>>> in a row (30 seconds interval), and never happened four times in a >>>>>>>>>> row on >>>>>>>>>> earlier versions. >>>>>>>>>> >>>>>>>>>> This is the report: >>>>>>>>>> <?xml version="1.0"?> >>>>>>>>>> <reportDefinition> >>>>>>>>>> <selector xmlns=" >>>>>>>>>> https://adwords.google.com/api/adwords/cm/v201409";> >>>>>>>>>> <fields>AccountDescriptiveName</fields> >>>>>>>>>> <fields>AccountCurrencyCode</fields> >>>>>>>>>> <fields>AccountTimeZoneId</fields> >>>>>>>>>> <fields>CampaignId</fields> >>>>>>>>>> <fields>CampaignName</fields> >>>>>>>>>> <fields>CampaignStatus</fields> >>>>>>>>>> <fields>Amount</fields> >>>>>>>>>> <fields>AdvertisingChannelType</fields> >>>>>>>>>> <predicates> >>>>>>>>>> <field>Status</field> >>>>>>>>>> <operator>IN</operator> >>>>>>>>>> <values>UNKNOWN</values> >>>>>>>>>> <values>ENABLED</values> >>>>>>>>>> <values>PAUSED</values> >>>>>>>>>> <values>REMOVED</values> >>>>>>>>>> </predicates> >>>>>>>>>> </selector> >>>>>>>>>> <reportName xmlns=" >>>>>>>>>> https://adwords.google.com/api/adwords/cm/v201409";>CampaignInfo_All_Time</reportName> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> <reportType xmlns=" >>>>>>>>>> https://adwords.google.com/api/adwords/cm/v201409";>CAMPAIGN_PERFORMANCE_REPORT</reportType> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> <dateRangeType xmlns=" >>>>>>>>>> https://adwords.google.com/api/adwords/cm/v201409";>ALL_TIME</dateRangeType> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> <downloadFormat xmlns=" >>>>>>>>>> https://adwords.google.com/api/adwords/cm/v201409";>GZIPPED_XML</downloadFormat> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> <includeZeroImpressions xmlns=" >>>>>>>>>> https://adwords.google.com/api/adwords/cm/v201409";>true</includeZeroImpressions> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> </reportDefinition> >>>>>>>>>> >>>>>>>>>> Our request headers: >>>>>>>>>> Content-Type >>>>>>>>>> application/x-www-form-urlencoded >>>>>>>>>> Authorization >>>>>>>>>> Bearer ya29.1...3Leq25 >>>>>>>>>> clientCustomerId >>>>>>>>>> 8928384200 >>>>>>>>>> developerToken >>>>>>>>>> kNkfox...m9qg_g >>>>>>>>>> skipReportHeader >>>>>>>>>> True >>>>>>>>>> skipReportSummary >>>>>>>>>> True >>>>>>>>>> User-Agent >>>>>>>>>> Adwords API by Maxlead >>>>>>>>>> Host >>>>>>>>>> adwords.google.com >>>>>>>>>> Content-Length >>>>>>>>>> 1445 >>>>>>>>>> Expect >>>>>>>>>> 100-continue >>>>>>>>>> Accept-Encoding >>>>>>>>>> gzip, deflate >>>>>>>>>> >>>>>>>>>> AdWords API Response headers: >>>>>>>>>> X-Content-Type-Options >>>>>>>>>> nosniff >>>>>>>>>> X-Frame-Options >>>>>>>>>> SAMEORIGIN >>>>>>>>>> X-XSS-Protection >>>>>>>>>> 1; mode=block >>>>>>>>>> Transfer-Encoding >>>>>>>>>> chunked >>>>>>>>>> Cache-Control >>>>>>>>>> private, max-age=0 >>>>>>>>>> Content-Type >>>>>>>>>> text/xml >>>>>>>>>> Date >>>>>>>>>> Mon, 08 Dec 2014 16:38:32 GMT >>>>>>>>>> Expires >>>>>>>>>> Mon, 08 Dec 2014 16:38:32 GMT >>>>>>>>>> Server >>>>>>>>>> GSE >>>>>>>>>> >>>>>>>>>> As stated before, this is an exact copy of the report we >>>>>>>>>> requested in earlier versions. But there is one small difference, we >>>>>>>>>> use >>>>>>>>>> flags skipHeaderReport and skipHeaderSummary in this version. >>>>>>>>>> >>>>>>>>>> Is v201409 not stable yet? >>>>>>>>>> >>>>>>>>>> Thank in advance, >>>>>>>>>> Zweitze de Vries >>>>>>>>>> >>>>>>>>> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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/54f9b606-8866-4e1a-a043-83cdfcedb647%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
