Hi Orly, I haven't seen any cases where numbers generate policy errors, do you have the requestId of a request that demonstrates this?
As for how to handle these errors, our recommendation is that you use the validateOnly header to check your ads before committing them. This allows you to detect policy violations and either correct them or request an exemption. An example of how to do this was recently included in the PHP client library: http://code.google.com/p/google-api-adwords-php/source/browse/trunk/examples/v200909/HandlePolicyViolationError.php Best, - Eric Koleda, AdWords API Team On Apr 28, 11:54 am, Orly Junior <orly.jun...@periscopix.com> wrote: > Hello, sometimes we receive policy error when there is no obvious > reason for such. > > Upon further analysis we identify the reason as being the usage of > certain numbers on the ad text. > > This effectively means that you will not be able to use a price (e.g. > £206.50) which part of it is the model number of a known Peugeot car > or God knows what else, except if you go through the entire process of > requesting an exemption. > > Perhaps at some point, so many numbers will be trademarked that > advertisers will not be able to use the price on their product ads at > all. > > The real problem lies on the fact that our software updates several > ads at once, as it is more efficient on Google resources and also > ensures the operations completes faster. > > However, since the incorrect identification of one ad as a policy > violation will compromise the execution of the entire batch (and we > are charged for it), our developer will be forced to go revert to old > technique of performing one update at a time, which is sadly an > inneficient approach. > > Specifying an exemption request will not solve the problem of not > being able to confidently submit a creative update batch. > > Will Google at some point be able to distinguish prices from actual > trademark violations? > > -- > =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ > Have you migrated to v200909 yet? > The v13 sunset is on April 22, 2010. > > Also find us on our blog and discussion > group:http://adwordsapi.blogspot.comhttp://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 > athttp://groups.google.com/group/adwords-api?hl=en -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
