[QuotaCheckError.INCOMPLETE_SIGNUP @ ; trigger:'<null>']

69 views
Skip to first unread message

Vladyslav

unread,
Sep 9, 2014, 6:27:42 AM9/9/14
to adwor...@googlegroups.com
I've read all the threads about this error without success. I think I've done all I could do myself.

I went through the Common Errors guide:
Did you enter your billing information?
Yes. I can see billing information in my Production MCC account. I've seen AdWords API T&C and accepted it.
Are you having trouble entering your billing information?
No. I've added credit card successfully. It was charged for a few cents (like when you link a card to Google Play) from Google Inc. So I'm sure the card was added successfully.
Are you using an unapproved developer token against a production AdWords account?
No. I'm using developer token from Production MCC against  the test client account under Test MCC.
Still receiving INCOMPLETE_SIGNUP error after completing the above steps?
Yes! I've submitted  a form to AdWords API Compliance and received an answer with same steps. So the tals way was to use the developer forum.


My Production MCC: 182-716-2353
My Test MCC662-907-7712
My Client under Test MCC861-475-5602

In the Developers Console I've created a "web application" logged in with the email of my Test MCC.

When a logged in as Test MCC owner account I go to my own web application and go through OAuth2 flow, grant access to my application.

Then I setup the client library in my web-server application with:
Developer Token: Developer token from my Production MCC.
Client Customer ID: Client under Test MCC (861-475-5602).
OAuth2 Client ID — From the app in Developers Console as described above.
OAuth2 Client Secret  Secret of the app.
OAuth2 Token: The one from auth flow with Test MCC owner.

In debug mode I see Authorization header with the right token and SOAP body contains clientCustomerId. So configs are fine.

After all I receive INCOMPLETE_SIGNUP with any api request.

Danial Klimkin

unread,
Sep 9, 2014, 7:02:19 AM9/9/14
to adwor...@googlegroups.com
Hello Vladyslav,


I see the production MCC account is missing T&T (terms and conditions not signed). Normally, it's available as the last step of the billing setup process.

Please check with the tokens review team to sign T&C manually.


-Danial, AdWords API Team.
Reply all
Reply to author
Forward
0 new messages