I don't mean to hijack this thread, but the whole point of my question 
stems from the "Test Accounts" section of the API docs:
https://developers.google.com/adwords/api/docs/test-accounts

Under "Getting Started" it states that you need to use a *production* mcc 
account Developer Token when making service calls (even to test accounts in 
test mcc).
However, when I try to use a production token from a different account to 
call a test account in a SOAP call, I get 
AuthorizationError:USER_PERMISSION_DENIED.

Why? Is there something I need to do to associate the test account with the 
production account? Since I am using OAuth credentials associated with the 
user from the test account and the production developer key, I assume there 
is something I need to do to associate them. I am able to authenticate via 
OAuth2 fine, but any API service calls I make return the user perm denied 
error.

Thanks
Mike

On Tuesday, October 15, 2013 7:07:27 AM UTC-4, Takeshi Hagikura (AdWords 
API Team) wrote:
>
> Hi Nate,
>
> If you need to access both campaigns with the same credential (MAIN 
> PRODUCTION MCC ACCOUNT in that case), the structure looks right to me. 
>
> As for the test accounts, now you can create a test MCC on your own 
> (please see the 
> blog<http://googleadsdeveloper.blogspot.jp/2013/08/streamlining-adwords-test-accounts.html>
> ).
> I recommend to create a separate MCC from the production MCC account. 
> It's easier to manage. 
>
> Best,
> - Takeshi, AdWords API Team
>
> On Thursday, October 10, 2013 8:53:08 PM UTC+9, deve...@aardvarkads.comwrote:
>>
>> I have tried to use the Production developer token in my Test calls 
>> (Oauth2 token refresh is successful), as Google instructs in grey block 
>> under "Getting Started": 
>> https://developers.google.com/adwords/api/docs/test-accounts?hl=e<https://developers.google.com/adwords/api/docs/test-accounts?hl=es>
>> n.
>>
>> When a ManagedCustomerService call failed with 
>> AuthorizationError.USER_PERMISSION_DENIED, 
>> I figured I needed to link the Test account to the production MCC. 
>> However, when I try to link any Test account to my production in MCC, I 
>> get an error message. This post outlines the same problem: 
>> https://groups.google.com/forum/#!topic/adwords-api/psNwhXb0cK8
>>
>> I attached the log files for the request.
>>
>> Please help.
>> Mike
>>
>> On Wednesday, October 9, 2013 3:56:56 PM UTC-4, Nate Fischer wrote:
>>>
>>> Hi All, 
>>>
>>> I've been trying to sort this out for 2 days now and haven't come to the 
>>> correct solution, any help would be greatly appreciated! 
>>>
>>> My situation:  I have 2 companies in a similar space (the component 
>>> industry, but separate entities entirely).  Both of these companies have 
>>> large databases of inventory connected to their respective web application 
>>> that I would like to link up to the AdWords API to programatically add  
>>> keywords/campaigns.  From what I have gathered so far talking AdWords 
>>> support my account structure needs to look like this: 
>>>
>>>                                                                             
>>>                                      
>>> MAIN PRODUCTION MCC ACCOUNT
>>>                                                                         
>>>                                                /                   
>>> \                        \
>>>                                                      
>>>                                                                  /         
>>>             \                        \ 
>>>                                                                             
>>>                                          
>>> /                       \                        \ 
>>>                                                                             
>>>                                         
>>> /                    Entity #1               Entity #2
>>>                                                                             
>>>                                        
>>> /                     campaign               campaign
>>>                                                                             
>>>                                
>>> TEST MCC 
>>>                                                                         
>>>                                    /               \ 
>>>                                                                         
>>>                                   /                 \ 
>>>                                                                         
>>>                                  /                   \
>>>                                                                             
>>>                          
>>> Test 1            Test 2
>>>                                                                             
>>>                      
>>> campaign           campaign
>>>
>>>
>>> Is this the correct structure that I should be trying to get set up or 
>>> am I going about this incorrectly?  I assume I need the test account/keys 
>>> to develop in a 'sandbox' and then once everything is working switch the 
>>> credentials to my production account but so far I have been completely 
>>> unable to get a Test MCC linked underneath my production MCC.
>>>
>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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.

Reply via email to