Hi, we are currently migrating from Adwords API v201710 to v201806 and we are observing an issue regarding policy violations / excemption requests.
Part of our test suite is the creation of an (expanded) text ad triggering a PolicyViolationError. Everything is fine with v201710 - we are expecting this error (and creating an excemption request later). [INFO] com.google.api.ads.adwords.lib.client.AdWordsServiceClient.soapXmlLogger SOAP response: <?xml version="1.0" encoding="UTF-8"?> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> ... <soap:Body> <soap:Fault> ... <detail> <ApiExceptionFault xmlns="https://adwords.google.com/api/adwords/cm/v201710"> ... <errors xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="PolicyViolationError"> ... <errorString>PolicyViolationError.POLICY_ERROR</errorString> <ApiError.Type>PolicyViolationError</ApiError.Type> <key> <policyName>weapons</policyName> <violatingText>Rifle</violatingText> </key> <externalPolicyName>Google AdWords</externalPolicyName> <externalPolicyUrl/> <externalPolicyDescription>This ad or keyword requires review before it can run.</externalPolicyDescription> <isExemptable>true</isExemptable> ... </errors> </ApiExceptionFault> </detail> </soap:Fault> </soap:Body> </soap:Envelope> However, the error is not triggered when using v201806. The expected error is not triggered: [DEBUG] com.google.api.ads.adwords.lib.client.AdWordsServiceClient.soapXmlLogger SOAP response: <?xml version="1.0" encoding="UTF-8"?> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> ... <soap:Body> <mutateResponse xmlns="https://adwords.google.com/api/adwords/cm/v201806"> <rval> <ListReturnValue.Type>AdGroupAdReturnValue</ListReturnValue.Type> <value> ... <ad xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="ExpandedTextAd"> ... </ad> <status>PAUSED</status> <policySummary> <reviewState>REVIEW_IN_PROGRESS</reviewState> <combinedApprovalStatus>UNDER_REVIEW</combinedApprovalStatus> </policySummary> </value> </rval> </mutateResponse> </soap:Body> </soap:Envelope> We are aware that there are some changes concerning policy violations as mentioned in https://developers.google.com/adwords/api/docs/reference/release-notes/v201806#policy and https://developers.google.com/adwords/api/docs/guides/exemption-requests. However, we wouldn't have expected that no error is triggered at all. Are we missing something? Why isn't the policy error triggered when using v201806? Thanks for your help, Peter -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads 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 and Google Ads 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 https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/01304439-fdd4-4b0a-8d64-88c49452b52c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.