Hi, If you are receiving incomplete sign up errors, please send me (by responding to author): 1. your MCC CID 2. the complete response error that you received
Thanks, On Thursday, February 27, 2014 1:18:13 PM UTC-5, Mike Sullivan wrote: > > I had a similar problem -- incomplete signup. > > *There is no Terms & Conditions acceptance *at the end of the Billings > setup. I did it three times. There is only a Save Changes button or > Cancel. > > > > > > On Friday, February 21, 2014 5:25:02 AM UTC-5, Josh Radcliff (AdWords API > Team) wrote: >> >> Hi, >> >> I checked your accounts and you have not accepted Terms & Conditions on >> your *prod* MCC. When you entered your billing information did you >> click *Continue* all the way through and accept the Terms & Conditions? >> >> Thanks, >> Josh, AdWords API Team >> >> On Thursday, February 20, 2014 8:51:47 AM UTC+1, GigiCom wrote: >>> >>> Hi, i have the same Issue 'Incoplete Signup' and I don't find anything. >>> >>> Thanks >>> >>> Am Freitag, 7. Februar 2014 20:25:23 UTC+1 schrieb Josh Radcliff >>> (AdWords API Team): >>> >>>> Hi, >>>> >>>> It looks like you did not accept Terms & Conditions on your production >>>> MCC. Could you go back into *Billing --> Billing Preferences* and >>>> re-enter your billing information, and make sure that you click >>>> *Continue* all the way through, including past the Terms & Conditions >>>> screen? >>>> >>>> Thanks, >>>> Josh, AdWords API Team >>>> >>>> On Thursday, February 6, 2014 2:03:15 AM UTC-5, deve...@jo.de wrote: >>>>> >>>>> Hi Josh, >>>>> yes i have set it up in both, the prouction MCC (827-869-5334) from >>>>> which i use the pending token and the test MCC (614-512-7851). >>>>> >>>>> Am Mittwoch, 5. Februar 2014 18:31:05 UTC+1 schrieb Josh Radcliff >>>>> (AdWords API Team): >>>>>> >>>>>> Hi Am, >>>>>> >>>>>> Have you entered billing information and accepted terms and >>>>>> conditions on your production MCC (the one with the pending developer >>>>>> token)? >>>>>> >>>>>> Thanks, >>>>>> Josh, AdWords API Team >>>>>> >>>>>> On Tuesday, February 4, 2014 2:13:24 AM UTC-5, deve...@jo.de wrote: >>>>>>> >>>>>>> Hi, >>>>>>> the clientCustomerId I use is 345-112-6902 from an Account i created >>>>>>> under the Test MCC. >>>>>>> >>>>>>> Am Montag, 3. Februar 2014 19:57:02 UTC+1 schrieb Josh Radcliff >>>>>>> (AdWords API Team): >>>>>>>> >>>>>>>> Hi Am, >>>>>>>> >>>>>>>> Welcome to the AdWords API community! Regarding the >>>>>>>> INCOMPLETE_SIGNUP error, could you let me know which >>>>>>>> *clientCustomerId* you put in *auth.ini* when running the >>>>>>>> *GetCampaigns.php* example? >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Josh, AdWords API Team >>>>>>>> >>>>>>>> On Friday, January 31, 2014 3:50:06 AM UTC-5, deve...@jo.de wrote: >>>>>>>>> >>>>>>>>> Hi Josh, >>>>>>>>> i'm completely new to the AdWords API and i've setup my auth.ini >>>>>>>>> in the php library exactly the way you described but im still getting >>>>>>>>> the QuotaCheckError.INCOMPLETE_SIGNUP. >>>>>>>>> Im using a test account since our Developer Token is not yet >>>>>>>>> approved. >>>>>>>>> 1. api.adwords.clientId i got from code.google.com/apis/consoleafter >>>>>>>>> logging in with the Test Account, creating a project and creating a >>>>>>>>> new client id for a native application. >>>>>>>>> 2. see 1. >>>>>>>>> 3. Optional as you said, ive put in the name of my Application. >>>>>>>>> 4. Developer Token from the Production Account in which the TOS >>>>>>>>> are accepted and the billig is set up. >>>>>>>>> >>>>>>>>> With that i am able to use the Getrefreshtoken.php and receive a >>>>>>>>> refreshtoken that ive also put in the auth.ini. >>>>>>>>> When i now try to use the example GetCampaigns.php i still receive >>>>>>>>> the error QuotaCheckError.INCOMPLETE_SIGNUP. >>>>>>>>> I have no idea what i am missing to get the test account working. >>>>>>>>> >>>>>>>>> Am Montag, 13. Januar 2014 19:57:24 UTC+1 schrieb Josh Radcliff >>>>>>>>> (AdWords API Team): >>>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> Thanks for putting together such a comprehensive list! The only >>>>>>>>>> modifications I would make are: >>>>>>>>>> >>>>>>>>>> 1. api.adwords.clientId - This can come from either the >>>>>>>>>> NON-test or the test account. Since you will ultimately need an >>>>>>>>>> api >>>>>>>>>> project for the non-test account, I would recommend using that >>>>>>>>>> here. >>>>>>>>>> 2. api.adwords.clientSecret - This can come from either the >>>>>>>>>> NON-test or the test account, same as #1. >>>>>>>>>> 3. api.adwords.userAgent - This is optional, but it is >>>>>>>>>> extremely helpful for us if you have questions about specific >>>>>>>>>> requests. >>>>>>>>>> You can set this to any string that might be useful for that >>>>>>>>>> purpose. >>>>>>>>>> 4. api.adwords.developerToken - As you stated, this should >>>>>>>>>> come from the NON-test account and does not have to be approved >>>>>>>>>> in order to >>>>>>>>>> use it in API calls on a test account. Note that we recently >>>>>>>>>> changed the >>>>>>>>>> AdWords UI so that you cannot create a developerToken from a test >>>>>>>>>> account, >>>>>>>>>> which should help avoid confusion on this going forward. >>>>>>>>>> 5. QuotaCheckError.INCOMPLETE_SIGNUP - You need to enter >>>>>>>>>> billing information and accept the Terms & Conditions on the >>>>>>>>>> NON-test >>>>>>>>>> account. You should not have to do this for the test account. >>>>>>>>>> >>>>>>>>>> Thanks again, >>>>>>>>>> Josh, AdWords API Team >>>>>>>>>> >>>>>>>>>> On Tuesday, January 7, 2014 1:30:27 PM UTC-5, Alex Medearis wrote: >>>>>>>>>>> >>>>>>>>>>> I finally got my test account working. The setup should be as >>>>>>>>>>> follows: >>>>>>>>>>> >>>>>>>>>>> api.adwords.refreshToken >>>>>>>>>>> This should be from the test account, after doing the two-step >>>>>>>>>>> oAuth handshake. >>>>>>>>>>> >>>>>>>>>>> api.adwords.clientId >>>>>>>>>>> This should be from the test account. Create an api project at >>>>>>>>>>> https://cloud.google.com/console, then set up a client id under >>>>>>>>>>> "APIs and Auth" -> Credentials -> Create new ClientID. >>>>>>>>>>> >>>>>>>>>>> api.adwords.clientSecret >>>>>>>>>>> Same as above. >>>>>>>>>>> >>>>>>>>>>> api.adwords.clientCustomerId >>>>>>>>>>> This is the customer id of an account under the test MCC, not >>>>>>>>>>> the id of the test MCC itself. You will need to create an account >>>>>>>>>>> under >>>>>>>>>>> the test MCC in adwords. Accounts -> Create account. >>>>>>>>>>> >>>>>>>>>>> api.adwords.userAgent >>>>>>>>>>> I don't believe this is necessary, but I'm using the email >>>>>>>>>>> address of the MCC account. >>>>>>>>>>> >>>>>>>>>>> api.adwords.developerToken >>>>>>>>>>> This is the developer token from a NON-test MCC account. Does >>>>>>>>>>> not need to be approved. >>>>>>>>>>> >>>>>>>>>>> So, in short, make sure everything is from the test account, >>>>>>>>>>> except the developer token. In order to help out everyone else, >>>>>>>>>>> here are >>>>>>>>>>> some potential pitfalls I ran into that I ran into: >>>>>>>>>>> >>>>>>>>>>> Attempting to link Test MCC with Production MCC, "The following >>>>>>>>>>> customer IDs had errors", "An error occurred. Please try again >>>>>>>>>>> later"... >>>>>>>>>>> It is not necessary to link your accounts -- the Test MCC should >>>>>>>>>>> remain unlinked from the MCC you are getting the developer token >>>>>>>>>>> from. >>>>>>>>>>> >>>>>>>>>>> 400 Bad Request / "error" : "invalid_grant": >>>>>>>>>>> Make sure that you are using a valid developer token. This >>>>>>>>>>> should be the token in your Production account under "My Account" >>>>>>>>>>> -> >>>>>>>>>>> Adwords API center >>>>>>>>>>> QuotaCheckError.INVALID_TOKEN_HEADER: >>>>>>>>>>> Make sure that you are using the actual refresh token, which is >>>>>>>>>>> the final step of the oAuth handshake, NOT the intermediate token >>>>>>>>>>> that you >>>>>>>>>>> receive in the browser callback. Copy the intermediate token back >>>>>>>>>>> into the >>>>>>>>>>> application ("Type the code you received here: ") to receive the >>>>>>>>>>> refresh >>>>>>>>>>> token. >>>>>>>>>>> >>>>>>>>>>> QuotaCheckError.INCOMPLETE_SIGNUP: >>>>>>>>>>> Make sure that you've accepted the terms and conditions and set >>>>>>>>>>> up billing on your account(s). I'm not sure if its necessary for >>>>>>>>>>> the test >>>>>>>>>>> MCC, but I just set it up for both and this problem went away. >>>>>>>>>>> >>>>>>>>>> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com 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 adwords-api+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
