RE: DEVELOPER_TOKEN_NOT_APPROVED - Google Ads

[Google Ads API Forum Advisor]

Hello,

Thank you for reaching out to us.

You've mentioned that you're using Google Ads TEST account for making API calls. If you're initiating the request on an actual production account, then this is the reason why you've encountered the DEVELOPER_TOKEN_NOT_APPROVED error. If you wish to use the developer token and make API requests on production accounts, you should apply for either Basic or Standard API access. You can check on the procedures mentioned on this guide for more details.

As an aside, I will be removing your original post as it contains a screenshot of your response log. Moving forward, please refrain from sharing logs in the Forum thread. Below is a copy of your post.

Hi team,
We are using a Google Ads TEST account for making API calls. When sending API request to create shared campaigns as shown in the official docs of Google Ads API (https://developers.google.com/google-ads/api/rest/examples#creates) we get the following error:
The developer token is not approved. Non-approved developer tokens can only be used with test accounts.


We are using Test account ID for making call. We even tried resetting the dev token, but we are still getting the same error.
Please help with this issues!
Thanks.

Regards,

Mark Kevin Albios Google Ads API Team

ref:_00D1U1174p._5004Q2PHGmC:ref

[Wayne]

Hi Mark

Thanks for the reply. Can you please review our account if we provide our account ID?

Thanks!

[Google Ads API Forum Advisor]

Hi Wayne,

I work with Mark and will assist you. You can share privately by "Reply to Author". Test accounts all have are square stating "Test Account" on the top right hand corner in the UI, both MCC and regular test accounts. All account Id's can only refer to accounts that have the red square when your developer token is not approved.

Regards,

Aryeh Baker Google Ads API Team

ref:_00D1U1174p._5004Q2PHGmC:ref

[Google Ads API Forum Advisor]

Hi Wayne,

Thank you for sending us your Id's privately. I checked and you have a developer token that can only access a test account that has the red square on the top right showing when looking at it in the UI. Your "test accounts" may be accounts you test on but they are still considered production accounts and not test accounts for the purpose of API usage.

Test accounts don't require an approved developer token, so you can start experimenting with the API immediately, even before your application is reviewed or approved. The developer token you have can go through an application for basic access to become a token that can be used with production accounts.

To play with real test accounts before your developer token is approved, you can create another new gmail account, and from that new gmail account follow the instructions in Test accounts. 

[Martin Levi]

Hi Aryeh,

I also need some assistance getting set up for Google Ads API.  I'm completely confused as to what the difference is between a "Test Account" and a "real test account" in your reply to Wayne.

I need the API only to upload offline click conversions, and it's not clear to me how I can test this on a test account with no clicks.

Please can you help me get set up?

Thanks,

Martin

[Google Ads API Forum Advisor]

Hi Martin,

Test accounts don't serve ads, so you won't have GCLID's and therefore you won't be able to upload click conversions without the API returning an error. You can still experiment with Create Conversion Actions and uploading of fake conversions to get a feel for the process. Of course an error will be returned for the fake conversion.

Regarding test accounts, all test mcc accounts and test regular accounts show in the UI with a red square in the top right with the words "test account" in them. If the red square isn't present it's not a test account, it doesn't matter if you internally call it a test account and only test on it without serving ads.

To create a test account, you must have a Google account that is not already linked to your production manager account. Create a new Google account.

Feel free to get back to us.

[Martin Levi]

Hi Aryeh,

Thanks for your response.  In my specific case I don't see any value in running the upload click conversions in a test environment.  At the moment I am uploading my conversions manually via the Google UI, and if I test an upload via the API and it doesn't work the worst case is that I have to upload some more conversions manually via the API while I make any corrections to the code.  Am I required to practice in a test environment before getting my production Developer Token?

Also, if I create a Master account, am I correct in thinking that I can get a Developer Token for that Master account which will then allow me to upload click conversions for any regular account that is linked to the Master account?

Regards,

Martin

[Google Ads API Forum Advisor]

Hi Martin,

There may be a value in running fake GCLID's in a test account, if the only problem is that they are fake then all other error messages won't come. Another benefit is in test accounts any mistake you make has no real world effects so you can learn by trial and error.

An MCC account with an active developer token affords access to the API to all sub-linked accounts in the hierarchy. Moreover, you can set up Cross-account conversion tracking - the benefits are described here.

[Martin Levi]

Hi Aryeh,

Thanks once again for your response.  In my specific case I still don't see any value in running conversion uploads in a test environment.  The conversion data is already recorded successfully in a database on my webserver so I am 100% confident of passing the correct data to Google, so the worst case scenario is that I run the upload and nothing happens.  So please let me know how I can go straight to a production Developer Token?

Thanks also for the links to cross-account conversion tracking, but it appears that it is pixel based.  In 2021 optimizing ad campaigns by means of  a third party pixel is close to completely ineffective, and will only continue to get worse long before Google finally and officially declares the pixel dead.  This is the major reason I am uploading my conversion data.

Regards,

Martin

[Google Ads API Forum Advisor]

Hi Martin,

This is Yasar and I work with Aryeh. Let me assist you with this.

Kindly note that you may not be able to test the conversions using test accounts as they do not serve ads. You need to have a production account for this functionality. Please refer to this guide for uploading conversions via API.

Note that you would need a production access level for your developer token in order to call conversion upload service API requests against the production account. That said, you can complete this form to have a basic access level for your developer token and make sure you have followed these steps below:

• Ensure that you already have a developer token with test account access level.
• Ensure that the API Contact Email in the API center is up-to-date. You will not be able to complete the application process without a valid, regularly checked Developer Contact Email. Ensure you have linked all of your active Google Ads accounts to the manager account with the API token.

Let us know if you have any further questions.

Regards,

Yasar Google Ads API Team

ref:_00D1U1174p._5004Q2PHGmC:ref

[Martin Levi]

Hi Yasar,

Thanks for your reply.  I will now go ahead and apply for my production Developer Token.  I do already have a test account Developer Token in my Master Account.

Is it OK that both my active Google Ad account and the Master account are set up on the same gmail account?

When it asks "Does your company currently possess any APPROVED Google Ads API Tokens?" is it referring only to production tokens?

Also, if for any reason my request for a Developer Token is rejected, will I have the opportunity to correct any errors and resubmit my application?  I am actually much more wary about getting my account access and structure correct than I am about integrating the API call!

Regards,

Martin

[Google Ads API Forum Advisor]

Hi Martin,

Thank you for your follow up questions. You may refer below for my responses :

Is it OK that both my active Google Ad account and the Master account are set up on the same gmail account?

This should be okay. However, if you would like to inquire further on account access details, you may reach out to the Google Ads Product Support team instead, via this link.

When it asks "Does your company currently possess any APPROVED Google Ads API Tokens?" is it referring only to production tokens?

The "APPROVED" developer token is referring to those tokens that have already been approved for either basic or standard access

Also, if for any reason my request for a Developer Token is rejected, will I have the opportunity to correct any errors and resubmit my application? I am actually much more wary about getting my account access and structure correct than I am about integrating the API call!

You should be able to re-submit a request. That said, for any developer token review and approval concerns, the Compliance Team should be able to provide more insights. You can reach their team via this contact form for any developer token related concerns.

Best regards,

Peter Laurence Napa Oliquino Google Ads API Team

ref:_00D1U1174p._5004Q2PHGmC:ref

[Martin Levi]

Thanks for all your help.  I now have my Developer Token approved for basic access.

Regards,

Martin