OK, thanks, will do.

On Tuesday, September 23, 2014 12:06:23 PM UTC-7, Josh Radcliff (AdWords 
API Team) wrote:
>
> 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 
> <https://developers.google.com/adwords/api/docs/common-errors#QuotaCheckError>
>  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
>
> On Monday, September 22, 2014 5:47:21 PM UTC-4, Steve Renaker wrote:
>>
>> 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
>> Test: 513-692-2134
>>
>> 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
>>
>>
>>
>> On Monday, September 22, 2014 8:47:42 AM UTC-7, Josh Radcliff (AdWords 
>> API Team) wrote:
>>>
>>> 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
>>>
>>> On Friday, September 19, 2014 11:17:50 AM UTC-4, [email protected] 
>>> wrote:
>>>>
>>>> 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
>>>>
>>>> On Thursday, September 18, 2014 8:08:47 PM UTC+3, Josh Radcliff 
>>>> (AdWords API Team) wrote:
>>>>>
>>>>> 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
>>>>>
>>>>> On Thursday, September 18, 2014 12:46:53 PM UTC-4, 
>>>>> [email protected] wrote:
>>>>>>
>>>>>> 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.
>>>>>>
>>>>>> On Tuesday, September 2, 2014 4:48:23 PM UTC+3, Josh Radcliff 
>>>>>> (AdWords API Team) wrote:
>>>>>>>
>>>>>>> Hi Eli,
>>>>>>>
>>>>>>> Have you tried setting the clientCustomerId 
>>>>>>> <https://developers.google.com/adwords/api/docs/guides/soap#clientCustomerId>
>>>>>>>  header 
>>>>>>> to the customer ID of one of the *child* AdWords accounts of your 
>>>>>>> test MCC?
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Josh, AdWords API Team
>>>>>>>
>>>>>>> On Sunday, August 31, 2014 8:22:01 AM UTC-4, [email protected] 
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> 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
>>>>>>>>
>>>>>>>> On Friday, August 29, 2014 4:15:11 PM UTC+3, Josh Radcliff (AdWords 
>>>>>>>> API Team) wrote:
>>>>>>>>>
>>>>>>>>> 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 
>>>>>>>>> <https://developers.google.com/adwords/api/docs/common-errors#QuotaCheckError>.
>>>>>>>>>  
>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>> On Thursday, August 28, 2014 10:20:19 AM UTC-4, 
>>>>>>>>> [email protected] wrote:
>>>>>>>>>>
>>>>>>>>>> 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
>>>>>>>>>>
>>>>>>>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
Visit this group at http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/b7753118-0cbf-4bf7-873b-f2ccae0a72c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to