Uploading audience via API to multiple Ad accounts

[Google dev]

Is it possible to have one app / developer token created (and approved by Google) that we can use to upload to various Ad accounts as long as that account Ad account gives the consent to access their account via API? Or is one app/token limited to one Ad manager (and Ad accounts below it)?

Is it possible to do this? Hope I am explaining this right. 

Would Ad Manager api (and service accounts) work? The uploading custom audience is there in Ads api only afaik.

Thanks.

[Google dev]

To add more details - we currently use the desktop app OAuth credentials and can upload from that project/token to the ad account that allows access. But we want the app/project to be created and maintained by us (the developers) and be able to access / upload audiences to Ad accounts that give permissions. 

Would this work in a Web app app type better? Or a service account. 

This part is not clear in all the docs I had reviewed. 

[Google Ads API Forum Advisor]

Hi,

Thank you for reaching out to us.

Moving forward to this, "Is it possible to have one app / developer token created (and approved by Google) that we can use to upload to various Ad accounts as long as that account Ad account gives the consent to access their account via API?" -Yes, you can use only one OAuth app. However, If you meant for the developer token, then note that the developer token is like a license key; it is tied to an MCC account for approval purposes, but once approved, you can use it to make calls against any Google Ads account. The MCC hierarchy for making API calls doesn't matter.

For this one "is one app/token limited to one Ad manager (and Ad accounts below it)?"
-You can create more than one OAuth app for your API console project. You may check this documentation for more information.

And for this one, "Would this work in a Web app type better? Or a service account."
-Kindly note that we strongly recommend using OAuth2 desktop app or web app flow instead of service accounts unless you need a domain-specific feature (for example, impersonation).

OAuth2 desktop app and web app flows do require an initial user interaction for granting access to the account, but are much simpler to set up.

You may check this documentation for service accounts and this documentation for OAuth2 desktop app or web app flow .

Best regards,

Heidi Google Ads API Team

ref:_00D1U1174p._5004Q2gfs7u:ref

[Google dev]

Hi - thank you for your reply!

(I posted a response but it's not showing here)

To summarize : 

In my Ads Manager account (under https://ads.google.com/aw/apicenter), I have created a Developer Token and applied for Basic Access

In the same Ads Manager account (under https://console.cloud.google.com/apis/credentials?project=xxxxxxxxx), I have created a Client ID / Secret for both Desktop and Web applications.

Once the dev token is approved for Basic Access, can I use the above to connect to any Ad account. 

Like in this statement : "MCC hierarchy for API calls doesn't matter" - does this mean, once I get the Developer token basic access approved, I can use that to access (assuming they give approval) any Ad account (like Bank A, Bank B, Bank C ad accounts - under different Ad managers / customers)?

Pl help clarify this.

Thanks!

[Google Ads API Forum Advisor]

Hi,

Thank you for getting back to our team. 

With regards to, "does this mean, once I get the Developer token basic access approved, I can use that to access (assuming they give approval) any Ad account (like Bank A, Bank B, Bank C ad accounts - under different Ad managers / customers)?", if these accounts are in the single entity then you can use it. I said this because please note that there is one developer token approved to use for a single entity only. Also, please make sure that the account that you use to send a request and the user email has access to the MCC account where the developer token is associated.

Regards,

Carmela Google Ads API Team

ref:_00D1U1174p._5004Q2gfs7u:ref

[Google dev]

Can you pl explain what the 'single entity' means? 

And your last comment means all the ad accounts I want to connect to and upload audiences have to be under the MCC (same as Ad Manager I am assuming) account? 

I am looking for a solution where one token/credentials will allow accessing (with consent) and posting audience data to ANY ad account out there. 

Sri

[Google Ads API Forum Advisor]

Hi Sri,

Thank you for the reply.

Can you pl explain what the 'single entity' means?

• You may check this API structure documentation as it has guide that introduces the primary components that make up the Google Ads API and this documentation for more information in entity diagrams.

And your last comment means all the ad accounts I want to connect to and upload audiences have to be under the MCC (same as Ad Manager I am assuming) account?

• If the topmost manager account holds a developer token, then all sub-accounts should still be able to use it. This is because one entity can't have basic access to more than one developer token. To get a better clarity on your concern related to developer token eligibility, you may also reach out to the API Compliance Team via this form .
• In addition, Developer token is tied to an MCC account for approval purposes, but once approved, you can use it to make calls against any Google Ads account. The MCC hierarchy for making API calls doesn't matter

I am looking for a solution where one token/credentials will allow accessing (with consent) and posting audience data to ANY ad account out there.

• For you to share your token, you need to give them access. You may check this article as it explains the levels of access you can assign and the corresponding features available for each access level. You can also learn here how to grant or remove access to your Google Ads Account.

Best regards,

Heidi Google Ads API Team

 

ref:_00D1U1174p._5004Q2gfs7u:ref