OfflineDataUploadService WhiteList Error

[Nitin Gupta]

Hello, 

We develop an enterprise application used by some of the largest advertisers in the world. We require access to the OfflineDataUPloadService AP for functionality in our next release. 

How can we get access to this? I attempted to work with our account manager for our internal advertising team even though this is not intended for internal use but for our customers. 

The Google AM tried to involve others to help. However, they have been unable to figure a path forward and suggested using a different API that does not provide the equivalent functionality. 

It's been over a month now and this is impacting our development timelines. 

Please advise how we can get access to this API for our product develoment team.

Thanks,

Nitin

[Google Ads API Forum Advisor Prod]

Hi Nitin,

Thank you for reaching out to us. I can assist you with the whitelisting process, but I'll need your Google Account Manager to contact us. Could you please ask your Google Account Manager to send us an email? We can assist them with the set up right away.

Thank you,
Bryan, Google Ads API Team

ref:_00D1U1174p._5001UXX5Jy:ref

[Nitin Gupta]

I've requested Pega's Google account manager, Miguel, reach out to you. 

Miguel is Pega's account manager for our own ad spend on Google. He has indicated we do not meet the thresholds required for access to this API as an advertiser.

However, we are not building products for internal usage but for our clients - leading retail banks, insurance companies, telcos, etc. He is not aware of the process to request access as product development organizations building tools for external advertisers. 

After the Google offline conversion capability is included in Pega CDH a client would request access to the API independently and use it in conjunction with their single-tenant and on-premise implementation of our product.

Please help us figure out the path forward to gain access to this API for external product development vs. internal usage.  

Thanks,

Nitin