Buyer Creative ID

[msi...@ezakus.com]

Hi guys,

When we get some disapproved creatives, we get an email containing the buyer creativeid and the snippet ID. 

Example

Buyer Creative ID	62002539277
Snippet ID	70959149353934883

Problem is that those values are not related to any field of the Creatives API entity.

The buyerCreativeId in API is a unique value set by us and not the google value.

The snippetId is, as far as I have checked, not provided in the API. 

So how can we match which creative was disapproved ? 

We can go the adex UI but still ... would be great to have those values in the API.

Or to have our own buyerCreativeId in the email so we can check directly which campaign is impacted.

Thanks

Manuel

[Mark Saniscalchi]

Hello Manuel,

That disapproval email is actually referencing a Placeholder Ad that was generated when you created a PretargetingConfig. If you happen to make use of the SOAP API, you could find this along with the related Placeholder Campaign / AdGroup with it. You wouldn't ordinarily ever need to directly create/update this, so the REST API doesn't expose it. I'm not certain why you received the email, given that the Placeholder Ad appears to have been approved on our end. I'll bring this up with the engineering team internally to see if we can prevent emails from being sent out for Placeholder Ads.

Regards,

Mark Saniscalchi

[Manuel]

Thanks Mark,

I have another question about creatives disapproved.

It would be great to have any insights from you guys cause it looks like my creatives are fine.

Note that we did some tests with our bidder and the python requester and the redirection is ok.

snippet id : 8985960146000680657

error : Bad Destination Url: Site Not Crawlable

Obviously the destination website is crawlable though...

Note that we use openbidder.

We also noticed that sometimes the creative is approved, we use it in our production bidder for several days then it's disapproved ...

Weird behaviour.

Thanks !

Manuel

[Mark Saniscalchi]

Hello Manuel,

Looking at the provided snippetId, I'm seeing that the disapproval appears to make sense—the click url resulted in a 400 Bad Request. This group focuses on API support, so you might want to instead talk to your TAM for a more in-depth analysis of the creative disapproval reason.

Regards,

Mark Saniscalchi