Is anyone experiencing this issue with Google Rejecting Banner Ads created with Lottie.
The client has been communicating with google about why the ads are being rejected and the response is:
''It shows on an internal tool that the reason behind being no eligible creative, or creative is being disallowed on publisher inventory is due to the wrapper provider being detected as one of the unidentified ad technology provider
If you'd find that the wrapper provider is one of the certified ad technology provider, it could be that the domain that provided in the wrapper is not certified, means that it will still be detected as unidentified vendor
You can have your creatives team to check and see the wrapper provider if they are indicated in the lists of certified ATP, and if they are certified, check with the wrapper provider if the domain that they have on the wrapper is also certified as most of the time, this is the main reason.''
HTML:
`<!DOCTYPE html>
Mercer Vale - 3 & 4 Bedroom Homes
`
Previously we would have provided a path to the json hosted on Lottie but we also tried it locally and that was being rejected too.
Is it anything o do with Lottie not accepting Googles GDPR policy?
Any feedback is welcome, thanks!
Is anyone experiencing this issue with Google Rejecting Banner Ads created with Lottie.
The client has been communicating with google about why the ads are being rejected and the response is:
''It shows on an internal tool that the reason behind being no eligible creative, or creative is being disallowed on publisher inventory is due to the wrapper provider being detected as one of the unidentified ad technology provider If you'd find that the wrapper provider is one of the certified ad technology provider, it could be that the domain that provided in the wrapper is not certified, means that it will still be detected as unidentified vendor You can have your creatives team to check and see the wrapper provider if they are indicated in the lists of certified ATP, and if they are certified, check with the wrapper provider if the domain that they have on the wrapper is also certified as most of the time, this is the main reason.''
HTML: `<!DOCTYPE html>