Supporting an on-prem open source application

[Sherif Nada]

Hi, 

I'm following up on this issue: https://groups.google.com/g/adwords-api/c/qMxsf1a2uZs/m/EPa1XT8uBQAJ. I contacted the Compliance Team as directed in the original issue. However, the Compliance Team are saying that Airbyte requiring users to obtain their own API token is in violation of the API policies and directed me to ask you for help. 

My question is the following: how can Airbyte not require users to apply for their own dev token, without allowing Airbyte any access to user data? (Airbyte is self-hosted by the clients. Having access to user data is not an option)

Thanks

Shrif Nada

Founding Member, Airbyte

[Google Ads API Forum Advisor Prod]

Hi Sherif,

Thank you for reaching out. The workaround here is that you apply for the developer token and share it with the clients. The clients’ MCC accounts are not linked to your MCC account so you do not have access to their accounts and data.

Thanks and regards,
Xiaoming, Google Ads API Team
 

Xiaoming Google Ads API Team

ref:_00D1U1174p._5004Q2DuADg:ref

[Sherif Nada]

Hi Xiaoming, 

Thanks for the prompt reply! Wouldn't this be a violation of the "Allowing automated use" section in the policy violation section: https://support.google.com/adspolicy/answer/6169371?hl=en#pp? 

From the docs:

"Any automatic or programmatic use of Google Ads by agencies or end-advertiser clients requires them to use their own Google Ads API (AdWords API) token; you cannot provide indirect access to your API token via APIs that you provide. End users of your tool will need to manually sign in to use your tool, rather than having automatic access, to make manual or programmatic changes to their accounts."

BEST,

Shrif Nada

Founding Member @ Airbyte