Hi Orly,
Thank you for the example, I see what you mean now. It turns out that
in the case of 206 this is a trademarked term in some countries, but
since my campaign was targeting the US I couldn't generate the error.
It will never be possible to completely avoid these types of policy
errors, but
Hi Eric, many thanks for your reply.
An instance of the problem could be reproduced by the following
request id: "867c6a6b4d06f8fbbf39f2972ed738db"
Your suggestion of using the validateOnly was very helpful. We
overlooked it as a possiblity and it will come in handy on identifying
the rejected ad
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
