Hi,
we're currently updating our frameworks from v201802 to v201809 and noticed something peculiar about the new version, namely that it allows us to upload ads containing policy violations where we were denied previously. We check the correct handling of certain policy violations in our test suite, and were surprised to see these tests fail because no policy violation error was returned.
As an example, any ads containing the word "cigar" in the ad copy caused a AdPolicyError.POLICY_ERROR to be returned in v201802, whereas in v201809 that same ad can be created just fine. I suppose it would later still be disapproved after review, but this is still a quite significant change in how policy violations are handled.
Interestingly enough, in the old Google Ads web interface it's also not possible to save an ad containing the word "cigar", while in the new interface no error is thrown and the text ad is created.
Is this expected behavior? If so, are there any recommendations how to test the correct handling of policy violations going forward?
Thanks and best regards,
Dorian