INCOMPLETE_SIGNUP error returned by Adwords API

176 views
Skip to first unread message

eli....@aimeesoft.com

unread,
Aug 28, 2014, 10:20:19 AM8/28/14
to adwor...@googlegroups.com
Hi,
When making requests with a  production key to test a MCC i get an INCOMPLETE_SIGNUP error.
I followed the instructions in other posts and made sure the billing info is updated and the terms contract has been approved.
Can you please help?

Test customer id: 879-695-1428
Production customer id: 471-076-9636

Thanks,
Eli

Josh Radcliff (AdWords API Team)

unread,
Aug 29, 2014, 9:15:11 AM8/29/14
to adwor...@googlegroups.com
Hi Eli,

Billing info needs to be setup and terms and conditions must be accepted on the production MCC (the one with the developer token). I can see that terms & conditions have not been accepted yet on your production MCC. Please follow the instructions in our Common Errors Guide. That guide also contains contact information you can use if you have trouble with the billing or terms & conditions setup.

Cheers,
Josh, AdWords API Team

eli....@aimeesoft.com

unread,
Aug 31, 2014, 8:22:01 AM8/31/14
to adwor...@googlegroups.com
Thanks Josh.
I checked again and we did accept the terms and did enter the billing information as required.
In any case I used the contact form in the guide you refereed me to and reported the problem.

Thanks again,
Eli

Josh Radcliff (AdWords API Team)

unread,
Sep 2, 2014, 9:48:23 AM9/2/14
to adwor...@googlegroups.com
Hi Eli,

Have you tried setting the clientCustomerId header to the customer ID of one of the child AdWords accounts of your test MCC?

Cheers,
Josh, AdWords API Team

eli....@aimeesoft.com

unread,
Sep 18, 2014, 12:46:53 PM9/18/14
to adwor...@googlegroups.com
Hi Josh,
I did use the correct customer id but while checking it i noticed it was not connected to a test MCC. I created a MCC account and connected it properly to the child account but the i still keep getting the incomplete singup error.
I also opened a ticket in the support form you reffered me to but i got no reply so far.

Josh Radcliff (AdWords API Team)

unread,
Sep 18, 2014, 1:08:47 PM9/18/14
to adwor...@googlegroups.com
Hi Eli,

I still see that Terms & Conditions are not signed on the production MCC. I also saw that you contacted the API Compliance team to resolve this ~30 minutes ago. You should hear back from them within the next day. Once they've resolved the Terms & Conditions issue, please let me know if you still encounter this error.

Thanks,
Josh, AdWords API Team

eli....@aimeesoft.com

unread,
Sep 19, 2014, 11:17:50 AM9/19/14
to adwor...@googlegroups.com
Hi Josh,
The API compliance team just got back to me - they they that the terms are not signed in the production MCC account and recommend to consult in this forum...
How do you suggest to proceed? the thing is that i see in my mcc console that terms are signed and billing preferences are set as well.
Moreover, if i understand correctly, i could not have setup the billing preferences without accepting the terms, right? so how come your records show billing preferences are ok but terms are not signed?
If you have no other suggestion i thought of opening a new MCC production account, sign terms and billing preferences and get a new developer token. If i understand correctly, when using the adwords API against test accounts the only thing the "links" to the production mcc account is the developer token, right?
Thanks,
Eli

Josh Radcliff (AdWords API Team)

unread,
Sep 22, 2014, 11:47:42 AM9/22/14
to adwor...@googlegroups.com
Hi Eli,

I see that there was further correspondence from the Compliance team about 10 hours ago, indicating that they are looking into the issue for you. Since they are the ones who can actually fix the missing Terms & Conditions issue, I'll defer to them on that.

You are correct in that signing terms is part of the billing setup process, but we sometimes see issues with the terms acceptance not being recorded properly. That's where the Compliance team will step in and help users sign the terms manually. Rather than creating another production MCC, I recommend letting the Compliance team help you fix the one you already have. I wouldn't want you to go through the trouble of creating a new account just to find yourself in the same situation with that account as well.

Thanks,
Josh, AdWords API Team

eli....@aimeesoft.com

unread,
Sep 22, 2014, 12:22:00 PM9/22/14
to adwor...@googlegroups.com
Ok, i will keep handling this issue with the compliance team.
Many thanks for your help!

Eli

Steve Renaker

unread,
Sep 22, 2014, 5:47:21 PM9/22/14
to adwor...@googlegroups.com
Hi Josh -- I hope you don't mind if I jump into this thread, since I'm having a similar issue which I hope you can help with. I've followed the instructions to set up an AdWords API test account, with the Python client. I'm trying to send requests to the production MCC account, but I can't get past the INCOMPLETE_SIGNUP error. Here are the customer IDs:

Production: 587-024-9783

Here's the request code:

from googleads.adwords import AdWordsClient
import googleads.common

client = AdWordsClient.LoadFromStorage()
campaign_service = client.GetService('CampaignService')
request = campaign_service.mutate()

I know that request wouldn't do anything even if it worked, but it's the minimum necessary code to generate the error. The production account billing information is filled in, so I assume somebody must have agreed to the terms and conditions. I'm pretty sure my googleads.yaml file is set up correctly, with the developer token from the production account and the client_customer_id set to the test account CID, and the other necessary values filled in, but still the INCOMPLETE_SIGNUP error persists. Any guidance?

Thanks very much,

- Steve

Josh Radcliff (AdWords API Team)

unread,
Sep 23, 2014, 3:06:23 PM9/23/14
to adwor...@googlegroups.com
Hi Steve,

I confirmed that your prod MCC does not show Terms & Conditions as accepted. Please go through the steps outlined in the Common Errors Guide for trying to accept Terms & Conditions and if you still get that error (or are unable to accept Terms & Conditions), contact the API Compliance team via the link in the guide.

Thanks,
Josh, AdWords API Team

Steve Renaker

unread,
Sep 23, 2014, 3:27:27 PM9/23/14
to adwor...@googlegroups.com
OK, thanks, will do.

Steve Renaker

unread,
Sep 26, 2014, 1:06:17 PM9/26/14
to adwor...@googlegroups.com
Hi Josh,

I got hold of the compliance group and got the T&C issue sorted out, but now I've got another error I can't get past. When I try to add a new campaign through my test account I get this error:

suds.WebFault: Server raised fault: '[OperationAccessDenied.ADD_OPERATION_NOT_PERMITTED @ class campaignmgmt.campaign.MutateAction (ADD) requires CREATE_CAMPAIGN]'

If I should start a new thread for this, just let me know. I see the question has been asked before, but not recently, and I wasn't able to get any useful help from the answers. I'm using the developer token from my production MCC account (listed below) and the CID from my test account (also listed below). 

Thanks,

- Steve

Josh Radcliff (AdWords API Team)

unread,
Sep 26, 2014, 3:21:18 PM9/26/14
to adwor...@googlegroups.com
Hi Steve,

That error is due to the same issue mentioned in this post. Your test CID is for an MCC, but you cannot create campaigns in an MCC. You'll want to create a child test AdWords (non-MCC) account under your test MCC, and then specify the child's CID in the header.

Cheers,
Josh, AdWords API Team

P.S. As you guessed, it generally is better to post a new topic when you have a new, unrelated question. This makes it easier for people to find relevant topics when they search the forum. No need to split this one off at this point, though -- I mention this just for future reference. :)
Reply all
Reply to author
Forward
0 new messages